LCP
Largest Contentful Paint
10.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix Forced Reflow Issues
How to optimize forte.forte.com
Next.js SiteScore: 36/100Analyzed February 2026
Fix Forced Reflow Issues
Medium Impact+10 points estimated
Why It Matters
JavaScript queries geometric properties after DOM changes, causing 113ms of forced reflows that block rendering.
How to Fix
Batch DOM reads and writes to avoid layout thrashing in React components. Use useLayoutEffect sparingly and prefer useEffect. Consider CSS transforms over position changes for animations.
0Poor
What This Score Means
A score of 36 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
778ms
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 36/100. The biggest problem is excessive JavaScript execution taking 3.4 seconds, which is blocking user interactions and causing an extremely slow Time to Interactive of 11 seconds. The site is loading 105KB of unused JavaScript and oversized images that could be compressed by 861KB, while the Largest Contentful Paint is delayed to 10.8 seconds due to render blocking and poor resource optimization. Reducing JavaScript bundle sizes, optimizing images, and implementing proper caching could dramatically improve the score by 30+ points and provide a much better user experience.
Other Optimization Recommendations
Reduce JavaScript Bundle Size
High Impact+25 points estimatedWhy It Matters:
JavaScript execution takes 3.4 seconds and blocks main thread for 1,116ms, severely impacting LCP (10.8s) and TTI (11.0s).
How to Fix:
Use Next.js bundle analyzer to identify unused code in _app.js (107KB wasted). Enable tree shaking and code splitting with dynamic imports. Remove legacy polyfills and update build target to modern browsers to save 25KB.
Optimize LCP Image Loading
High Impact+20 points estimatedWhy It Matters:
LCP image has 3.9 second render delay and wastes 350KB due to oversized dimensions and poor compression.
How to Fix:
Add fetchpriority='high' to the LCP image element. Implement Next.js Image component with proper responsive sizes. Compress images further and serve correctly sized variants (current 750px for 412px display).
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
Eliminate Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
Frequently Asked Questions
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