Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize truck.liftutbildning.se
Two CSS files are blocking initial render, adding 150ms delay to First Contentful Paint.
Use Next.js built-in CSS optimization by importing critical styles in _app.js. Move non-critical styles to load asynchronously using next/dynamic with ssr: false. Inline critical CSS for above-the-fold content in the document head.
A score of 63 falls in the "Needs Improvement" 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 Next.js site has poor performance with a score of 63/100, indicating significant issues that need attention. The biggest problem is extremely slow content loading, with the Largest Contentful Paint taking 7.9 seconds - far exceeding Google's recommended 2.5 seconds. The main culprits are oversized images that are much larger than their display dimensions (wasting 317 KiB), unused JavaScript from Google Analytics and tracking scripts (wasting 116 KiB), and render-blocking CSS files that delay initial page rendering. Optimizing image sizes, removing unused JavaScript code, and deferring non-critical resources could dramatically improve load times and boost the performance score by 25+ points.
Why It Matters:
The LCP image has 1.9 seconds of render delay and poor compression, directly impacting the 7.9s LCP score.
How to Fix:
Increase compression on the hero image (4210-900x600.webp) to save 54KB. Move the image to a CDN with better cache headers. Use Next.js Image component with priority prop and optimize=true for automatic optimization.
Why It Matters:
116KB of unused JavaScript from Google Tag Manager scripts delays LCP by 350ms and FCP by 300ms.
How to Fix:
Implement Google Tag Manager with Next.js gtag configuration to load only required tracking. Use next/script component with strategy='afterInteractive' for non-critical analytics. Remove unused tracking pixels and defer secondary scripts.
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 Next.js Speed Tests
116KB of unused JavaScript from Google Tag Manager scripts delays LCP by 350ms and FCP by 300ms.
The LCP image has 1.9 seconds of render delay and poor compression, directly impacting the 7.9s LCP score.
24 KiB of unused JavaScript is wasting 150ms of load time and impacting FCP/LCP.
Three CSS files are blocking initial page render and delaying LCP by 150ms.