Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize craft.kit.dev
JavaScript is causing 92ms of forced reflows that block the main thread and hurt INP.
Batch DOM reads and writes to avoid layout thrashing in app-B75yEAbr.js. Use requestAnimationFrame for DOM measurements. Cache geometric property values instead of repeatedly querying offsetWidth/offsetHeight.
A score of 97 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 an excellent performance score of 97/100, indicating very fast loading times for users. However, the biggest opportunity for improvement is reducing unused JavaScript code, which could save an estimated 69KB and improve loading times by up to 300ms - this includes removing unnecessary code from both the main app bundle and analytics tracking scripts. The site also has a render-blocking CSS file that delays initial page rendering by about 150ms, and some JavaScript functions are causing forced reflows that impact smoothness. While these issues are relatively minor given the high overall score, addressing the unused JavaScript would provide the most meaningful performance boost for users.
Why It Matters:
70KB of unused JavaScript is delaying LCP by 300ms and wasting bandwidth.
How to Fix:
Analyze Matomo tracking script and remove unused features (56% unused). Use tree-shaking in your build process to eliminate dead code from app-B75yEAbr.js (62% unused). Consider loading analytics scripts asynchronously after page load.
Why It Matters:
CSS file is blocking initial render and delaying LCP/FCP by 150ms.
How to Fix:
Inline critical CSS directly in the HTML head for above-the-fold content. Load non-critical CSS asynchronously using media='print' onload="this.media='all'" technique. Consider splitting CSS into critical and non-critical bundles in your build process.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Poor cache policies waste 14KB on repeat visits and slow down returning user experience.
DNS lookup to Sentry is adding 70ms delay to LCP and creating network dependency bottleneck.
102 KiB of unused JavaScript is delaying LCP by 400ms and blocking critical page rendering.
The 601KB hero image lacks priority hints and proper optimization, contributing to the 14-second LCP.
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.