LCP
Largest Contentful Paint
6.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Preconnect for External Origins
How to optimize demo.comments.nonprod.dev.coeditor.link
Add Preconnect for External Origins
Medium Impact+8 points estimated
Why It Matters
Missing preconnect hints waste 300ms establishing connections to external domains.
How to Fix
Add <link rel='preconnect' href='https://unherd-wpml-test.go-vip.net'> to your Next.js _document.js Head component. Use next/head to preconnect to any other external domains used by your comments widget. Limit preconnect hints to the 3-4 most critical external origins to avoid performance degradation.
0Needs Improvement
What This Score Means
A score of 70 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
292ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.04
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js comments widget has poor performance with a score of 70/100, mainly due to a severely delayed Largest Contentful Paint of 6.5 seconds. The biggest issue is render-blocking CSS files that are preventing the page from displaying content quickly, combined with 407 KiB of unused JavaScript that's slowing down the entire loading process. The site could save nearly half a second by inlining or deferring critical CSS files, and an additional 2.1 seconds by removing unnecessary JavaScript code. Adding preconnect hints to external origins and updating the build process to avoid legacy JavaScript polyfills would provide additional performance gains.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
CSS files are blocking initial page render and delaying LCP by 460ms.
How to Fix:
Configure Next.js to inline critical CSS for above-the-fold content using next/dynamic with ssr:false for non-critical components. Move non-critical CSS (98329ce9ca87da37.css and 9e0ee02d498ed780.css) to load asynchronously using loadCSS or Next.js dynamic imports. Consider splitting CSS bundles to load only necessary styles for initial render.
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
407 KiB of unused JavaScript is delaying LCP by 2.1 seconds and blocking user interactions.
How to Fix:
Use Next.js dynamic imports with React.lazy() to code-split the 268ab96c92d3df28.js bundle. Analyze the bundle with webpack-bundle-analyzer to identify unused code. Remove or defer loading of f1e0318e19c9f7d3.js features that aren't needed on initial render. Enable tree-shaking in your Next.js build configuration.
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
Remove Unused JavaScript Code
407 KiB of unused JavaScript is delaying LCP by 2.1 seconds and blocking user interactions.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial page render and delaying LCP by 460ms.
Remove Unused JavaScript Code
371 KiB of unused JavaScript is blocking the main thread for 2.4 seconds and delaying interactivity by 18+ seconds.
Fix Lazy-Loading on LCP Image
The LCP image has lazy loading enabled, delaying critical content painting by 4.5 seconds and causing massive element render delay.