Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize tamer.web.vercel.app
1.7 seconds of JavaScript execution time is blocking the main thread and delaying Time to Interactive to 8.6 seconds.
Break up long-running JavaScript tasks using React.memo() and useMemo() hooks to prevent unnecessary re-renders. Implement lazy loading with React.lazy() and Suspense for heavy components. Use web workers for CPU-intensive calculations to keep the main thread responsive.
A score of 73 falls in the "Needs Improvement" 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Next.js site has poor performance with a score of 73/100, primarily due to excessive JavaScript blocking the main thread for 2.9 seconds. The biggest issue is render-blocking CSS files that delay both First Contentful Paint and Largest Contentful Paint by 750ms, while 207 KiB of unused JavaScript further slows the site. The Largest Contentful Paint takes a concerning 4.8 seconds, mainly caused by a 2.8-second element render delay. Deferring CSS loading, removing unused JavaScript code, and optimizing the build process could improve performance by several seconds and significantly boost user experience.
Why It Matters:
CSS files are blocking initial render and delaying LCP by 750ms, preventing users from seeing content quickly.
How to Fix:
Inline critical CSS for above-the-fold content in your Next.js pages. Use next/dynamic with ssr: false for non-critical components. Configure next.config.js to extract and defer non-critical CSS chunks using the experimental.css option.
Why It Matters:
207 KiB of unused JavaScript is delaying LCP by 300ms and wasting bandwidth on unnecessary code execution.
How to Fix:
Use Next.js dynamic imports to code-split large components and libraries. Analyze your bundle with @next/bundle-analyzer to identify unused dependencies. Implement tree-shaking by using named imports instead of default imports from large libraries.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
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.