Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize metavgc.com
Images are oversized and poorly compressed, wasting 289 KiB of bandwidth with no impact on visual quality.
Use Next.js Image component with proper sizing - images are served at 475x475 but displayed at 168x168. Implement responsive images with srcSet for different screen sizes. Increase compression settings for WebP images to reduce file sizes by 30-50% without quality loss.
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.
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/React site has fair performance with a score of 71/100, but faces significant JavaScript execution issues. The biggest problem is excessive JavaScript processing taking 3.7 seconds, which creates a poor user experience with 1.3 seconds of blocking time that prevents users from interacting with the page. The site is loading 367 KiB of unused JavaScript from ad networks and analytics, plus 43 KiB of unnecessary legacy code that modern browsers don't need. Optimizing JavaScript delivery, removing unused code, and implementing better caching (currently missing for key images) could improve the score by 15-20 points and dramatically reduce the 14-second time to interactive.
Why It Matters:
JavaScript execution takes 3.7 seconds and blocks the main thread, causing 1,330ms Total Blocking Time which severely impacts user interactions.
How to Fix:
Split large chunks using Next.js dynamic imports with React.lazy() for non-critical components. Remove or defer third-party scripts like Criteo and ad networks until after page load. Use Next.js Script component with strategy='lazyOnload' for analytics and tracking scripts.
Why It Matters:
The main CSS file blocks initial render and delays both FCP and LCP by 150ms each.
How to Fix:
Extract critical above-the-fold CSS and inline it in the HTML head. Use Next.js built-in CSS optimization by splitting the large CSS chunk into smaller, page-specific bundles. Remove unused CSS rules (75% of current CSS is unused) using PurgeCSS or similar tools.
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
LCP element has 3.2 second render delay causing the poor 7-second LCP score.
Heavy JavaScript parsing takes 900ms and creates 990ms of blocking time, preventing user interactions.
Google Fonts are blocking first paint for 1.65 seconds, severely delaying LCP and FCP.
The main CSS file blocks initial render and delays both FCP and LCP by 150ms each.