Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize dailymathquest.com
285 KiB of unused JavaScript and 18 KiB of unused CSS are delaying LCP by 1.45 seconds and blocking page rendering.
Remove unused Font Awesome CSS (98% unused) and replace with icons you actually need. Split Firebase bundles and only load required modules (Firestore shows 65% unused code). Use tree-shaking and dynamic imports for D3.js which is 77% unused.
A score of 59 falls in the "Needs Improvement" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Daily Math Quest site has poor performance with a score of 59/100, taking 8.8 seconds for the Largest Contentful Paint - well above Google's recommended 2.5 seconds. The biggest problem is render-blocking CSS files that delay the page's initial display by 310 milliseconds, combined with excessive unused JavaScript (285 KB) from Firebase and D3.js libraries that aren't fully utilized. The site is also loading 99% unused Font Awesome CSS (18 KB) and has inefficient caching that could save 215 KB on repeat visits. Fixing these issues by deferring non-critical CSS, removing unused code, and implementing proper caching could improve the performance score by 30+ points and dramatically speed up the user experience.
Why It Matters:
Render-blocking CSS files are delaying First Contentful Paint by 310ms and creating long dependency chains.
How to Fix:
Inline critical CSS for above-the-fold content directly in HTML head. Defer non-critical stylesheets (themes.css, graph.css, treemap.css) using media='print' onload technique. Add preconnect hints for Firebase, Google APIs, and Firestore domains to establish early connections.
Why It Matters:
Oversized images waste 38 KiB and the LCP image lacks fetchpriority optimization, delaying render completion.
How to Fix:
Resize ghost images from 300x300 to actual display size of 96x140 pixels. Add fetchpriority='high' to the LCP image element. Remove lazy loading from above-the-fold images and compress existing WebP files further using tools like Squoosh.
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Current Cloudflare challenge setup suggests security concerns that could be optimized to maintain protection while reducing overhead.
With a 99 performance score, proactive monitoring prevents future regressions and maintains excellent user experience.
Cloudflare challenge resources have zero cache lifetime, causing unnecessary re-downloads and impacting repeat visit performance.
Layout shifts score of 0.108 creates poor user experience as content jumps during loading.