LCP
Largest Contentful Paint
7.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery and Sizing
How to optimize truck.liftutbildning.se
Optimize Image Delivery and Sizing
High Impact+20 points estimated
Why It Matters
Oversized images waste 1,074KB and delay LCP by 300ms, especially the hero image taking 1.98 seconds to render.
How to Fix
Replace the 1024x1044 PNG logo with properly sized WebP versions using Next.js Image component with responsive breakpoints. Implement proper srcSet for the hero image at media.truck-liftutbildning.se. Use next/image with priority={true} for above-the-fold images and optimize image compression settings.
0Needs Improvement
What This Score Means
A score of 68 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
158ms
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 Next.js website has poor performance with a score of 68/100, primarily due to extremely slow loading times that take nearly 8 seconds before users can fully interact with the page. The biggest issue is inefficient resource loading - the site is loading 116 KiB of unused JavaScript (mostly from Google Analytics), 18 KiB of unused CSS (particularly Font Awesome icons), and oversized images that are much larger than needed for display. The site would benefit most from removing unused code, optimizing image sizes to match their display dimensions, and implementing better caching strategies, which could collectively improve the performance score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Remove Unused CSS and JavaScript
High Impact+25 points estimatedWhy It Matters:
Eliminating 18KB of unused CSS and 116KB of unused JavaScript can improve LCP by 650ms and reduce TTI by 7.9 seconds.
How to Fix:
Remove the entire Font Awesome CSS file since 99.5% is unused - use only needed icons as SVGs instead. Optimize Google Analytics by switching to gtag with minimal tracking events. In Next.js, use dynamic imports for non-critical components and enable tree shaking in webpack config.
Fix Render Blocking Resources
Medium Impact+12 points estimatedWhy It Matters:
CSS files are blocking initial page render by 320ms, directly impacting First Contentful Paint and user experience.
How to Fix:
Move critical CSS inline using Next.js styled-jsx or CSS-in-JS solutions for above-the-fold content. Defer Font Awesome loading using next/dynamic with ssr: false. Implement CSS code splitting by route using Next.js automatic code splitting features to load only necessary styles per page.
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
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Next.js Speed Tests
Next.js Performance Resources
Fix Render Blocking Resources
CSS files are blocking initial page render by 320ms, directly impacting First Contentful Paint and user experience.
Remove Unused CSS and JavaScript
Eliminating 18KB of unused CSS and 116KB of unused JavaScript can improve LCP by 650ms and reduce TTI by 7.9 seconds.
Fix Element Render Delay
LCP element has 6 second render delay causing extremely poor perceived performance.
Reduce JavaScript Main Thread Work
Excessive main thread blocking time of 8.2 seconds prevents user interactions and severely impacts responsiveness.