Thanks Point
Discordサーバー向けミッション・ポイント管理システム。メンバーの活動を可視化し、ポイント報酬でコミュニティを活性化。メッセージ送信、ボイスチャット、リアクションなど多彩なミッションを設定可能。.
Report generated on April 5, 2026
A note on how to read this
This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.
Key Insights for Thanks Point
CSP blocks regional Google Analytics endpoints, killing login funnel visibility
Your Discord authentication flow is invisible to analytics. You cannot track whether users are successfully logging in, where they drop off, or identify friction points in your Discord-integrated onboarding—critical data for a service that depends entirely on Discord authentication.
Login page loads 54% slower than industry standard, risking Discord user abandonment
At 1231ms, your authentication page is competing for attention against Discord's native login experience. Users expecting instant authentication will bounce before entering your service, directly impacting conversion rates for your Discord-authenticated userbase.
Content Security Policy misconfiguration blocks both analytics collection and monitoring of real user behavior
Your CSP restricts analytics to the legacy domain while your implementation targets regional endpoints. This creates a security blind spot where you cannot monitor login anomalies, bot activity, or unusual authentication patterns that Discord-integrated services are particularly vulnerable to.
What ProdPoke understands about Thanks Point
Thanks Point appears to be a web application that uses Discord for authentication, as evidenced by the login page displaying 'Discordでログイン' (Discord Login in Japanese). The page is built with Tailwind CSS and presents a login interface. Without being able to see the authenticated portions of the site, I can only confirm that this is a Discord-integrated service, but cannot determine its specific business purpose or functionality beyond the authentication mechanism visible on this entry page.
Based on exploring 1 page across the site
First Impression — How clear is your site?
This is 'Thanks Point,' a Discord server management tool. The site describes it as a "ミッション達成でポイント獲得" (mission completion and point acquisition) system that allows community managers to set various missions like "メッセージ送信、VC参加、リアクションなど" (message sending, voice chat participation, reactions). Members earn points through these missions, which can be exchanged for rewards or used in lotteries to "メンバーのエンゲージメントを最大化する" (maximize member engagement).
This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.
Overall Score
Strong foundation.
Performance
92/100High Time to First Byte: 1231ms
Your Thanks Point login page takes 1231ms to load, which is significantly slower than the 800ms target. Discord users expecting a quick authentication experience will experience delayed page load, potentially increasing login abandonment rates and reducing conversion to your authenticated service.
Found: 1231ms
SEO
100/100Accessibility
100/100Functional
100/100Technical Health
Connecting to 'https://region1.google-analytics.com/g/collect?v=2&tid=G-XFTET...
Your Thanks Point login page is attempting to send analytics data to Google Analytics regional endpoints, but your Content Security Policy only allows connections to the main google-analytics.com domain. This is blocking user interaction tracking and analytics collection for your Discord-authenticated service, preventing you from monitoring login behavior and user engagement.
Fetch API cannot load https://region1.google-analytics.com/g/collect?v=2&tid=...
The Fetch API request to Google Analytics is being blocked by your Content Security Policy configuration. Analytics data from your Discord login page cannot be transmitted, which means you're losing visibility into how users are accessing your service and whether the authentication flow is working properly across different user segments.
Compliance
100/100Key Metrics
Crawlability
Standards
Improvement Plan
Your Thanks Point login experience is currently hamstrung by a CSP configuration that predates your current analytics implementation. The regional Google Analytics endpoints (region1.google-analytics.com) are being blocked while your code actively tries to reach them, creating a silent failure where login telemetry simply disappears. This is your highest priority because without analytics data, you're flying blind on your most critical user flow—Discord authentication is your only entry point, and you have zero visibility into how it's performing.
Second, address the 1231ms Time to First Byte. For a login-focused application, every 100ms of latency directly correlates to abandonment. Discord users are accustomed to instant authentication experiences; your page should load in under 800ms. Investigate whether your server is processing Discord requests synchronously, or if there's DNS resolution lag on the regional analytics endpoints that's cascading into page load delays.
Your immediate action plan: (1) Update your Content Security Policy to explicitly allow https://region1.google-analytics.com/g/collect in your connect-src directive, alongside the existing google-analytics.com allowlist. Test that analytics payloads are now transmitting successfully by checking your Google Analytics real-time dashboard immediately after login. (2) Profile your server response time separately from asset delivery—identify whether the 1231ms is server latency or frontend asset loading. (3) Once analytics flow is restored, create a dashboard specifically tracking Discord login completion rates, abandonment points, and time-to-authentication by geographic region. This data will reveal whether your performance issues are global or localized to specific Discord user segments.
Suggested priority order:
- Fetch API cannot load Google Analytics regional endpoint — CSP misconfiguration
- Connecting to regional Google Analytics blocked — CSP domain whitelist incomplete
- High Time to First Byte 1231ms — Login performance degradation
This is your site? Get the full picture.
Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.
What is ProdPoke?Automated analysis generated on April 5, 2026. Not professional advice. Contact us to modify or remove this report.