Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize belizetravelinsider.com
46KB of unused JavaScript delays LCP by 300ms and wastes bandwidth on mobile users.
Enable tree shaking in Next.js webpack config to eliminate dead code. Use dynamic imports for heavy libraries like the 60KB chunk. Configure @next/bundle-analyzer to identify and remove unused dependencies from the 3794 chunk.
A score of 91 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.
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 good performance with a score of 91/100, but there's still room for improvement. The biggest issue is render-blocking CSS files that are delaying both page rendering and the Largest Contentful Paint (currently at 3.3 seconds), with an estimated impact of 850ms. The site is also serving oversized images that could be compressed and properly resized to save 84KB, and has unused JavaScript code wasting 46KB of bandwidth. Addressing the render-blocking CSS by inlining critical styles and optimizing image delivery would provide the most significant performance gains for users.
Why It Matters:
Blocking CSS delays LCP and FCP by 850ms, preventing users from seeing content quickly.
How to Fix:
Configure Next.js to inline critical CSS using next-critical plugin. Split large CSS files (27KB) into route-specific chunks. Use CSS-in-JS or CSS modules for component-specific styles to enable automatic code splitting.
Why It Matters:
Oversized images waste 84KB and delay LCP by 150ms with unnecessary data transfer.
How to Fix:
Update Next.js Image components with proper responsive sizes props matching actual display dimensions. Increase compression by lowering quality parameter from q=74 to q=60-65. Use next-optimized-images to automatically serve correctly sized images.
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
Oversized images waste 84KB and delay LCP by 150ms with unnecessary data transfer.
Blocking CSS delays LCP and FCP by 850ms, preventing users from seeing content quickly.
310KB of unused CSS and legacy JavaScript polyfills are unnecessarily bloating your bundles and slowing page load.
Your CLS score of 1.082 is primarily caused by unsized images in the footer causing massive layout shifts.