Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize apogeewatcher.com
Oversized images waste 12KB of bandwidth and can cause layout shifts affecting user experience.
Resize the RankInPublic badge from 310x100px to 124x40px to match its display size. Resize the launch badge from 300x81px to 148x40px. Add explicit width='124' attribute to the RankInPublic badge image to prevent layout shifts. Use responsive image techniques or server-side resizing for optimal delivery.
A score of 98 falls in the "Good" 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 website has excellent performance with a score of 98/100, indicating very fast loading speeds for users. The biggest improvement opportunity is removing unused JavaScript code, which could save 20 KiB and improve your First Contentful Paint by 150 milliseconds. Additionally, optimizing image delivery by properly sizing badge images and implementing better caching policies could save another 51 KiB in total bandwidth. While these optimizations would provide marginal gains given the already high performance score, addressing the unused JavaScript would be the most impactful change for further speed improvements.
Why It Matters:
Unused JavaScript blocks rendering and delays First Contentful Paint by 150ms while wasting 20KB of bandwidth.
How to Fix:
Analyze your main JavaScript bundle (app-BFLsgXNZ.js) to identify unused code accounting for 65% of the file. Use tree-shaking with your bundler to eliminate dead code. Consider code splitting to load only necessary JavaScript for each page. Defer non-critical JavaScript execution until after page load.
Why It Matters:
Poor caching wastes 39KB on repeat visits and slows down returning user experience.
How to Fix:
Set long-term caching headers (1 year) for your Matomo analytics script instead of no-cache. Increase Microsoft Clarity script cache lifetime beyond 1 day to at least 1 week. Implement versioning strategy for third-party scripts to enable aggressive caching while maintaining update capability.
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
Poor caching wastes 39KB on repeat visits and slows down returning user experience.
Unused JavaScript blocks rendering and delays First Contentful Paint by 150ms while wasting 20KB of bandwidth.
3 CSS files block page rendering for 2.2 seconds, delaying First Contentful Paint.
Unsized images cause a 0.401 CLS score as content jumps when images load.