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
69KB of unused JavaScript wastes 300ms of processing time and delays LCP by 300ms.
Analyze Matomo analytics script and remove unused features or switch to GA4. Use tree-shaking in your build process to eliminate dead code from app-B75yEAbr.js. Implement code splitting to load only required JavaScript per page.
A score of 94 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 94/100, but there are still some optimization opportunities. The biggest issue is render-blocking CSS that's delaying page loading by 150ms, which affects both your Largest Contentful Paint (2.7s) and First Contentful Paint times. Additionally, you have 69 KiB of unused JavaScript from analytics and your main app bundle that could be optimized or deferred to improve loading speed. Addressing the render-blocking CSS and trimming unused JavaScript could push your already strong performance score even higher and reduce your Speed Index from 4.2 seconds.
Why It Matters:
CSS file blocks initial page render for 150ms, directly delaying both LCP and FCP.
How to Fix:
Inline critical CSS for above-the-fold content in the HTML head. Move non-critical CSS to load asynchronously using media='print' onload='this.media="all"' technique. Consider splitting CSS into critical and non-critical bundles in your build process.
Why It Matters:
JavaScript queries geometric properties after DOM changes, causing 33ms of unnecessary layout work.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing in your JavaScript. Cache geometric property values instead of repeatedly querying offsetWidth/offsetHeight. Use CSS transforms instead of changing layout properties when possible.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.