LCP
Largest Contentful Paint
15.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking CSS
How to optimize cinesync.web.feature.5.layoutindex.dev
Eliminate Render Blocking CSS
Medium Impact+12 points estimated
Why It Matters
107 KiB of unused CSS and render-blocking stylesheets delay First Contentful Paint by 1.4 seconds.
How to Fix
Use Next.js CSS optimization by splitting critical CSS inline in the document head. Remove unused CSS rules from the main stylesheet (986c55cf0cc05833.css) which has 86% unused styles. Defer non-critical CSS loading using next/dynamic for component-specific styles that aren't above-the-fold.
0Poor
What This Score Means
A score of 37 falls in the "Poor" 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
479ms
Needs Improvement
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 site has severe performance issues with a critically low score of 37/100. The biggest problem is excessive JavaScript execution time (3.2 seconds), primarily from Google reCAPTCHA and other scripts that are blocking the main thread and causing a painfully slow 15.2-second Largest Contentful Paint. The site is also loading nearly 770KB of unused JavaScript and 107KB of unused CSS, while render-blocking stylesheets are delaying initial page rendering by 1.4 seconds. Immediate wins would come from deferring non-essential JavaScript, optimizing or removing the heavy reCAPTCHA implementation, and eliminating unused code - these changes alone could improve the performance score by 30+ points and dramatically reduce load times.
Other Optimization Recommendations
Reduce Unused JavaScript Loading
High Impact+25 points estimatedWhy It Matters:
768 KiB of unused JavaScript is blocking page rendering and delaying LCP by 3.8 seconds.
How to Fix:
Configure Next.js code splitting to defer non-critical components using dynamic imports with { ssr: false }. Remove or lazy-load reCAPTCHA until user interaction is needed. Implement tree shaking by reviewing imports and removing unused third-party libraries like Facebook Pixel from initial bundle.
Fix Critical Image Loading Issues
High Impact+20 points estimatedWhy It Matters:
LCP image has lazy loading enabled and takes 2.4 seconds to discover, severely delaying page rendering.
How to Fix:
Remove loading='lazy' from the LCP image (Freakier Friday movie poster) and add priority={true} to Next.js Image component. Add preload link in next/head for the LCP image resource. Optimize image compression - current images can be reduced by 105 KiB through better compression settings.
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
Fix Critical Image Loading Issues
LCP image has lazy loading enabled and takes 2.4 seconds to discover, severely delaying page rendering.
Reduce Unused JavaScript Loading
768 KiB of unused JavaScript is blocking page rendering and delaying LCP by 3.8 seconds.
Reduce Unused JavaScript Bundle Size
616 KiB of unused JavaScript wastes network bandwidth and delays page interactivity.
Remove Legacy JavaScript Polyfills
75 KiB of unnecessary polyfills for modern browsers slow LCP by 400ms.