LCP
Largest Contentful Paint
1.3s
Good
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Preload Critical Font Resources
How to optimize potenciados.com
Preload Critical Font Resources
High Impact+1 point estimated
Why It Matters
The JetBrains Mono font (22KB) is on the critical path with 1.85s load time, potentially causing layout shifts.
How to Fix
Add a <link rel='preload' as='font'> tag in your Next.js _document.js for jetbrains-mono-600.woff2. Use font-display: swap in your CSS to prevent invisible text during font swap. Consider using next/font for automatic font optimization in Next.js 13+.
0Good
What This Score Means
A score of 98 falls in the "Good" 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
127ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js React site has excellent performance with a score of 98/100, indicating very fast loading times for users. The biggest remaining issue is render-blocking CSS that's delaying your page's initial display by 210 milliseconds, specifically a CSS file that's preventing content from appearing quickly. Additionally, the site is loading about 99 KB of unused JavaScript code that could be removed or deferred to further optimize performance. While these issues exist, they're relatively minor given the already high performance score, but addressing the render-blocking CSS could provide noticeable improvements to your Core Web Vitals.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+1 point estimatedWhy It Matters:
The main CSS file is blocking page render, delaying LCP by 200ms and FCP by 200ms.
How to Fix:
Split your CSS bundle in Next.js by creating critical CSS inline and loading non-critical styles asynchronously. Use next/dynamic with ssr: false for components with heavy CSS. Consider using CSS-in-JS libraries like styled-components to automatically split CSS by component.
Code Split Unused JavaScript
Medium Impact+0.5 points estimatedWhy It Matters:
99KB of unused JavaScript is being loaded unnecessarily, contributing to slower Time to Interactive (4.1s).
How to Fix:
Use Next.js dynamic imports with next/dynamic for components not needed on initial render. Analyze your bundle with @next/bundle-analyzer to identify large chunks. Move third-party scripts to Next.js Script component with strategy='lazyOnload' for non-critical functionality.
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
Eliminate Legacy JavaScript Polyfills
Unnecessary polyfills add 14KB and delay LCP by 150ms for modern browsers.
Optimize JavaScript Execution Performance
JavaScript execution blocks the main thread for 2.8 seconds, creating a 770ms potential input delay.
Remove Unused JavaScript Code
Unused JavaScript wastes 11MB of bandwidth and delays LCP by 55.8 seconds while blocking interactions.
Optimize JavaScript Bundle Splitting
Large JavaScript bundles are causing 1.6s execution time and 200ms blocking time, severely impacting interactivity.