LCP
Largest Contentful Paint
3.0s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize mm.js.37236.mentimeter.dev
Remove Unused JavaScript Code
High Impact+6 points estimated
Why It Matters
356KB of unused JavaScript is bloating your bundle size and slowing down page load without providing value.
How to Fix
Use Next.js bundle analyzer (@next/bundle-analyzer) to identify unused code in your chunks. Implement dynamic imports for GSAP ScrollTrigger and other animation libraries that aren't needed immediately. Remove or lazy-load the Google Tag Manager script and Maze analytics if not critical for initial page load. Configure your build to tree-shake unused polyfills and transforms.
0Needs Improvement
What This Score Means
A score of 87 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
172ms
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/React site has good performance with a score of 87/100, but has one critical issue holding it back. The biggest problem is render-blocking CSS files that are delaying the initial page load by nearly 1 second, preventing users from seeing content quickly. The site also suffers from a slow Time to Interactive at 10.2 seconds due to excessive unused JavaScript (356 KiB that could be removed) and inefficient main-thread processing. Optimizing the CSS delivery, removing unused JavaScript code, and implementing better code splitting could significantly improve the user experience and push this site into the excellent performance range.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+8 points estimatedWhy It Matters:
CSS files are blocking initial page render and delaying FCP by 1 second, directly impacting user experience.
How to Fix:
Implement critical CSS inlining for above-the-fold content in your Next.js app. Move non-critical CSS to load asynchronously using next/dynamic with ssr: false for components below the fold. Consider splitting your large CSS bundle (57KB) into route-specific chunks using Next.js automatic CSS code splitting.
Optimize Cache Strategy
Medium Impact+3 points estimatedWhy It Matters:
Poor caching configuration forces users to re-download resources on repeat visits, missing opportunities for faster load times.
How to Fix:
Configure longer cache headers for static assets in your Next.js deployment (Vercel/CDN settings). Set cache-control headers to at least 31536000 seconds (1 year) for JS/CSS bundles with hashed filenames. For third-party scripts like Maze loader, implement service worker caching or move to self-hosted version with proper cache headers.
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
Optimize Cache Strategy
Poor caching configuration forces users to re-download resources on repeat visits, missing opportunities for faster load times.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial page render and delaying FCP by 1 second, directly impacting user experience.
Optimize CSS Delivery Strategy
Render-blocking CSS delays First Contentful Paint by 900ms, preventing users from seeing content quickly.
Eliminate Page Redirects Chain
Redirects add 780ms delay and directly impact LCP by 800ms, creating unnecessary network round trips.