LCP
Largest Contentful Paint
7.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize knallens.fs.se
Remove Unused JavaScript Code
Medium Impact+10 points estimated
Why It Matters
24 KiB of unused JavaScript is wasting 150ms of load time and impacting FCP/LCP.
How to Fix
Analyze your Next.js bundle using @next/bundle-analyzer to identify unused code in chunk 4383-60735002eb169288.js. Implement code splitting with dynamic imports for components not needed on initial load. Remove unnecessary polyfills for modern JavaScript features (Array.at, Object.hasOwn) by updating your Next.js target browsers configuration.
0Needs Improvement
What This Score Means
A score of 71 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
78ms
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 site has concerning performance issues with a score of 71/100, falling short of good user experience standards. The biggest problem is extremely slow Largest Contentful Paint at 7.8 seconds, primarily caused by unoptimized images that could save 487 KiB through modern formats like WebP/AVIF and proper sizing. The site is also slowed down by render-blocking CSS files and unused JavaScript code totaling 24 KiB that could be eliminated. Addressing the image optimization alone could improve loading speed by 1.5 seconds and significantly boost the overall performance score.
Other Optimization Recommendations
Optimize Images for Modern Formats
High Impact+25 points estimatedWhy It Matters:
Images are causing a 1.5 second LCP delay and wasting 487 KiB of bandwidth with outdated formats.
How to Fix:
Convert JPEG images to WebP/AVIF formats using Next.js Image component with format optimization. Implement proper responsive image sizing by adjusting your image CDN to serve correctly sized images (665x798 instead of 900x758). Enable automatic format selection in your media.knallens-fs.se CDN configuration.
Eliminate Render Blocking CSS
High Impact+15 points estimatedWhy It Matters:
Three CSS files are blocking initial page render and delaying LCP by 150ms.
How to Fix:
Inline critical CSS for above-the-fold content in your Next.js pages using styled-jsx or CSS-in-JS. Move non-critical CSS (15e87215aa996daa.css, d20172e3fcd0b9a3.css) to load asynchronously using next/dynamic or media='print' with onload trick. Use Next.js built-in CSS optimization by ensuring proper CSS splitting.
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
Eliminate Render Blocking CSS
Two CSS files are blocking initial render, adding 150ms delay to First Contentful Paint.
Remove Unused JavaScript Code
116KB of unused JavaScript from Google Tag Manager scripts delays LCP by 350ms and FCP by 300ms.
Optimize Largest Contentful Paint Image
The LCP image has 1.9 seconds of render delay and poor compression, directly impacting the 7.9s LCP score.
Eliminate Render Blocking CSS
Three CSS files are blocking initial page render and delaying LCP by 150ms.