LCP
Largest Contentful Paint
2.7s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking CSS
How to optimize craft.kit.dev
Generic SiteScore: 94/100Analyzed January 2026
Eliminate Render-Blocking CSS
High Impact+3 points estimated
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.
0Good
What This Score Means
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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
35ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
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.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+2 points estimatedWhy It Matters:
69KB of unused JavaScript wastes 300ms of processing time and delays LCP by 300ms.
How to Fix:
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.
Fix Forced Layout Reflows
Medium Impact+1 point estimatedWhy 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.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Implement Long-term Asset Caching
Poor cache policies waste 14KB on repeat visits and slow down returning user experience.
Add Preconnect to Sentry Domain
DNS lookup to Sentry is adding 70ms delay to LCP and creating network dependency bottleneck.
Remove Unused JavaScript Code
102 KiB of unused JavaScript is delaying LCP by 400ms and blocking critical page rendering.
Optimize LCP Image Loading
The 601KB hero image lacks priority hints and proper optimization, contributing to the 14-second LCP.
Frequently Asked Questions
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites