Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize beltone.frontend.stg.robustastudio.com
The redirect from root domain to /en adds 751ms delay and directly impacts LCP by 750ms.
Configure your Next.js app to serve content directly at the root domain or implement server-side redirect in next.config.js using redirects() function. Update DNS/CDN settings to point directly to /en if that's the default locale. Test with curl to verify single-hop navigation.
A score of 83 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.
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 83/100, but has room for improvement in key areas. The biggest problem is multiple page redirects that are adding 750ms of unnecessary delay to both your First Contentful Paint and Largest Contentful Paint, causing your page to take 4.4 seconds to show its main content. Additionally, your site is loading over 12MB of content primarily from large video files, and your page takes 8.3 seconds to become fully interactive. Eliminating the redirects and optimizing your video content could easily push your performance score into the 90s and significantly improve user experience.
Why It Matters:
Video files consume 10.6MB (83% of total payload) severely impacting load times and LCP.
How to Fix:
Compress the 8MB sample video using FFmpeg with H.264 codec at lower bitrate. Replace autoplay videos with poster images using Next.js Image component. Implement lazy loading for videos using Intersection Observer API. Consider moving videos to CDN with adaptive streaming.
Why It Matters:
PNG images can be reduced by 358KB using modern formats, improving perceived load speed.
How to Fix:
Update next.config.js to enable automatic WebP/AVIF conversion using Next.js built-in image optimization. Replace the large sustainability-bg-3.png with WebP version. Use next/image component for all images to enable automatic format selection and compression.
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
PNG images can be reduced by 358KB using modern formats, improving perceived load speed.
Video files consume 10.6MB (83% of total payload) severely impacting load times and LCP.
Google Fonts lack font-display optimization causing text rendering delays.
The main hero image can be compressed further to improve LCP by 150ms.