Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize hipposplit.com
Short cache durations force unnecessary re-downloads on repeat visits, slowing performance.
Configure your CDN/server to cache static assets for 1 year instead of 4 hours. Set cache-control headers for the PostHog scripts to 'public, max-age=31536000'. Add versioning to asset filenames to enable safe long-term caching.
A score of 100 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 achieves a perfect performance score of 100/100, indicating excellent overall performance. However, there are still opportunities for optimization, with the biggest issue being oversized images that could improve your Largest Contentful Paint by 300 milliseconds and save 70 KB of data transfer. The site is also loading 67 KB of unused JavaScript code that isn't being executed, which represents wasted bandwidth for your users. To further optimize, consider implementing responsive images that match the actual display dimensions and removing or deferring unnecessary JavaScript to make the site even more efficient for visitors.
Why It Matters:
Oversized images delay LCP by 300ms and waste 70KB of bandwidth on mobile devices.
How to Fix:
Use Astro's Picture component with multiple breakpoints for the hero images. Generate 385x794 versions for mobile display instead of serving 660x1361 images. Convert the logo to WebP format and create a 56x56 version to match display size.
Why It Matters:
67KB of unused JavaScript increases bundle size and slows initial page load.
How to Fix:
Use Astro's tree-shaking by importing only needed functions from modules. Split the large module.SteQYeQS.js (40KB unused) into smaller chunks. Defer loading of non-critical JavaScript like PostHog until after page interaction.
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
67KB of unused JavaScript increases bundle size and slows initial page load.
Oversized images delay LCP by 300ms and waste 70KB of bandwidth on mobile devices.
Render-blocking CSS is delaying initial paint by 160ms and preventing faster content rendering.
The LCP element lacks fetchpriority=high attribute, which could improve resource loading prioritization and reduce the 5.0s LCP time.