LCP
Largest Contentful Paint
18.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Video Element
How to optimize quickbooks.intuit.com
Optimize LCP Video Element
High Impact+20 points estimated
Why It Matters
The hero video has 2+ second render delay and lacks fetchpriority optimization, severely impacting LCP of 18.2 seconds.
How to Fix
Add fetchpriority='high' to the hero video element. Implement video poster image with proper dimensions to prevent layout shift. Consider replacing autoplay video with optimized static image for mobile using Next.js responsive images.
0Poor
What This Score Means
A score of 26 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
650ms
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/React site has severe performance issues with a critically low score of 26/100. The biggest problem is excessive JavaScript execution time (12.2 seconds) combined with massive amounts of unused code - nearly 3MB of unnecessary JavaScript and CSS that's slowing everything down. Your pages take an extremely long 18.2 seconds to show meaningful content and nearly a full minute to become interactive, primarily due to bloated third-party scripts and inefficient code splitting. Removing unused JavaScript, optimizing your build process to reduce bundle sizes, and deferring non-critical scripts could dramatically improve your score by 40+ points and provide a much better user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
2.8MB of unused JavaScript is blocking the main thread for 12.2 seconds and delaying LCP by 3.6 seconds.
How to Fix:
Use Next.js dynamic imports with React.lazy() to code-split large components. Remove or defer third-party scripts like LivePerson chat (763KB unused). Configure webpack-bundle-analyzer to identify and eliminate dead code from your Next.js build.
Remove Unused CSS Rules
Medium Impact+12 points estimatedWhy It Matters:
291KB of unused CSS is blocking first paint and adding 750ms delay to FCP.
How to Fix:
Use PurgeCSS with Next.js to remove unused styles from component stylesheets. Implement critical CSS inlining for above-the-fold content. Split CSS by route using Next.js automatic CSS code splitting to load only necessary styles per page.
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 CSS Rules
291KB of unused CSS is blocking first paint and adding 750ms delay to FCP.
Eliminate Unused JavaScript Code
2.8MB of unused JavaScript is blocking the main thread for 12.2 seconds and delaying LCP by 3.6 seconds.
Implement Efficient Resource Caching
Poor cache lifetimes are costing 1,718 KiB in repeat downloads and adding 300ms to both LCP and FCP.
Optimize JavaScript Execution Performance
16.4 seconds of JavaScript execution time is causing 6,660ms of total blocking time, severely impacting user interactions.