LCP
Largest Contentful Paint
7.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundle Size
How to optimize grwsolar.co.uk
Reduce Unused JavaScript Bundle Size
High Impact+25 points estimated
Why It Matters
456 KiB of unused JavaScript delays LCP by 950ms and blocks user interactions for 770ms.
How to Fix
Configure Next.js code splitting by moving large dependencies to dynamic imports using next/dynamic. Analyze bundle with @next/bundle-analyzer to identify oversized chunks. Remove unused Google Analytics features and use gtag4 selective loading instead of full GTM.
0Needs Improvement
What This Score Means
A score of 53 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
412ms
Needs Improvement
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 53/100, indicating significant user experience issues. The biggest problem is excessive JavaScript that takes 1.7 seconds to execute and includes 456 KiB of unused code, which is severely delaying the Largest Contentful Paint (7.4 seconds) and making the site unresponsive for over 11 seconds. The site is also loading unnecessary CSS (28 KiB unused) and render-blocking stylesheets that could save 300ms if optimized. Reducing JavaScript bundle sizes, removing unused code, and deferring non-critical resources would dramatically improve loading speeds and user experience.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+18 points estimatedWhy It Matters:
CSS files block initial render and delay LCP by 300ms with 89% unused styles.
How to Fix:
Extract critical CSS for above-the-fold content using Next.js built-in CSS optimization. Move non-critical styles to load asynchronously with next/dynamic imports. Remove unused CSS from the 32KB stylesheet using PurgeCSS in your Next.js build process.
Optimize Hero Image Compression
Medium Impact+8 points estimatedWhy It Matters:
The main hero image wastes 47KB and could improve perceived load performance.
How to Fix:
Reduce Next.js Image component quality from 75 to 60 for non-critical images. Use next-optimized-images plugin for automatic WebP compression. Implement responsive images with proper srcSet sizes for the hero banner.
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
Optimize Image Delivery Performance
Images are oversized and poorly compressed, wasting 613KB of bandwidth and slowing page load.
Eliminate Unused JavaScript Code
156KB of unused JavaScript is blocking page load and delaying LCP by 1.2 seconds.
Fix Largest Contentful Paint Issue
LCP is critically slow at 8.7 seconds, severely impacting user experience and Core Web Vitals score.
Preconnect to Critical Third-Party Origins
Missing preconnect hints to staging-api.tailzaar.com waste 300ms on connection setup.