LCP
Largest Contentful Paint
5.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused CSS and JavaScript
How to optimize quickbooks.intuit.com
Remove Unused CSS and JavaScript
High Impact+25 points estimated
Why It Matters
291 KiB of unused CSS and 2,913 KiB of unused JavaScript are blocking render and slowing down LCP by 1.05 seconds.
How to Fix
Use Next.js built-in bundle analyzer to identify unused code. Remove unused dependencies and implement code splitting with dynamic imports. Enable tree shaking in your webpack config and consider lazy loading third-party scripts like LivePerson chat and reCAPTCHA.
0Poor
What This Score Means
A score of 31 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
880ms
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 QuickBooks Next.js site has severe performance issues with a score of only 31/100. The biggest problem is extremely slow page loading, with users waiting 5.7 seconds to see the main content (Largest Contentful Paint) and an alarming 62 seconds until the page becomes fully interactive. The site is severely bloated with 12.6 MB of resources, including massive amounts of unused JavaScript (2.9 MB) and CSS (291 KB) that could be eliminated, plus render-blocking scripts that prevent the page from displaying quickly. Immediate fixes should focus on removing unused code, optimizing the 2MB video file, implementing proper caching, and deferring non-critical JavaScript to dramatically improve load times.
Other Optimization Recommendations
Optimize JavaScript Execution Performance
High Impact+20 points estimatedWhy It Matters:
16.4 seconds of JavaScript execution time is causing 6,660ms of total blocking time, severely impacting user interactions.
How to Fix:
Break up long-running tasks in your React components using React.lazy() and Suspense. Implement code splitting at the route level in Next.js. Move heavy computations to Web Workers and defer non-critical third-party scripts using Next.js Script component with strategy='afterInteractive'.
Implement Efficient Resource Caching
Medium Impact+12 points estimatedWhy It Matters:
Poor cache lifetimes are costing 1,718 KiB in repeat downloads and adding 300ms to both LCP and FCP.
How to Fix:
Configure your CDN to cache static assets for at least 1 year. Set proper Cache-Control headers in your Next.js config for JavaScript, CSS, and images. Use Next.js automatic static optimization and implement service worker caching for critical resources using next-pwa.
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.
Optimize LCP Video Element
The hero video has 2+ second render delay and lacks fetchpriority optimization, severely impacting LCP of 18.2 seconds.
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.