Eliminate Unused JavaScript Bundles

How to optimize quietmirror.me

Next.js SiteScore: 93/100Analyzed April 2026Re-analyze this site

Eliminate Unused JavaScript Bundles

High Impact+4 points estimated

Why It Matters

95KB of unused JavaScript is blocking page performance and delaying user interactions.

How to Fix

Use Next.js dynamic imports to code-split large chunks. Implement React.lazy() for components not needed on initial render. Configure webpack-bundle-analyzer to identify and remove dead code from your Next.js build process.

0Good

What This Score Means

A score of 93 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

LCP

Largest Contentful Paint

2.9s
Needs Improvement

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

197ms
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 performs well with an excellent score of 93/100, but there are several optimization opportunities to achieve perfect performance. The biggest issue is excessive unused JavaScript, with 93 KB of unnecessary code being loaded (over 80% waste in key bundles), which contributes to a slower-than-ideal Speed Index of 3.6 seconds. Additional quick wins include optimizing a single oversized icon image that's being displayed at 24x24 pixels but loading at 192x192 (wasting 10KB), and addressing render-blocking CSS that's delaying initial page rendering. Implementing code splitting to reduce JavaScript bundle sizes and properly sizing images would likely push this site into the perfect performance range.

Other Optimization Recommendations

Fix Render Blocking CSS

High Impact+3 points estimated

Why It Matters:

CSS file is blocking initial page render for 151ms and preventing faster visual content display.

How to Fix:

Move critical CSS inline using Next.js styled-jsx or CSS-in-JS solutions. Use Next.js dynamic imports for non-critical stylesheets. Configure next.config.js to split CSS bundles and defer non-essential styles.

Optimize Icon Image Delivery

Medium Impact+2 points estimated

Why It Matters:

Your header icon is 10KB larger than needed and uses inefficient PNG format.

How to Fix:

Replace the 192x192 PNG icon with a properly sized 24x24 WebP version using Next.js Image component. Configure next.config.js to enable WebP format conversion. Use responsive image sizing with the Image component's sizes prop.

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

More Next.js Speed Tests

Next.js Performance Resources

Frequently Asked Questions