LCP
Largest Contentful Paint
9.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Main Thread Work
How to optimize beta.webcastletech.com
Reduce JavaScript Main Thread Work
High Impact+20 points estimated
Why It Matters
Excessive main thread blocking time of 8.2 seconds prevents user interactions and severely impacts responsiveness.
How to Fix
Use React.lazy() and Suspense to code-split heavy components. Move non-critical JavaScript to Web Workers using Comlink. Implement server-side rendering optimization by reducing client-side hydration work and using Next.js streaming features.
0Poor
What This Score Means
A score of 33 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
1744ms
Poor
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 website has severe performance problems with a critically low score of 33/100. The biggest issue is excessive JavaScript blocking the main thread for nearly 19 seconds, which prevents users from interacting with the page and causes an extremely slow Time to Interactive of 19.6 seconds. The site is also suffering from render-blocking CSS files that delay initial page rendering by over 2 seconds, and a slow server response time of 760ms. Optimizing JavaScript delivery, reducing unused code (78KB of unused JS identified), and implementing proper caching for the large video files could dramatically improve performance and user experience.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+25 points estimatedWhy It Matters:
Critical CSS files are blocking initial page render and delaying LCP by 2 seconds.
How to Fix:
Extract critical above-the-fold CSS and inline it in the document head. Use Next.js dynamic imports to load non-critical CSS asynchronously. Split the large 31KB CSS file into smaller, component-specific chunks using CSS modules or styled-components.
Fix Element Render Delay
High Impact+15 points estimatedWhy It Matters:
LCP element has 6 second render delay causing extremely poor perceived performance.
How to Fix:
Preload the hero image using Next.js Image component with priority={true}. Optimize the hero poster PNG to WebP format reducing size by 742KB. Use next/dynamic to defer loading of below-the-fold components that may be blocking the LCP element render.
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 Render Blocking Resources
CSS files are blocking initial page render by 320ms, directly impacting First Contentful Paint and user experience.
Optimize Image Delivery and Sizing
Oversized images waste 1,074KB and delay LCP by 300ms, especially the hero image taking 1.98 seconds to render.
Remove Unused CSS and JavaScript
Eliminating 18KB of unused CSS and 116KB of unused JavaScript can improve LCP by 650ms and reduce TTI by 7.9 seconds.
Fix Element Render Delay
LCP element has 6 second render delay causing extremely poor perceived performance.