Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize pedrodegouveia.vercel.app
Images are massively oversized, with the React icon alone wasting 349KB being displayed at 96x85 from a 3840x3417 source.
Resize technology icons to their actual display dimensions (96x96px) before uploading. Convert PNG files to WebP format for better compression. Create responsive image variants using Astro's built-in image optimization with the Image component.
A score of 0 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.
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 website has severe performance issues with a failing score of 0/100. The biggest problem is oversized images that are wasting 789 KB of bandwidth - for example, a React logo image is 3840x3417 pixels but only displayed at 96x85 pixels, which is massively inefficient. The page takes 4.6 seconds to visually load content and 2.6 seconds for the first paint, both unacceptably slow for modern web standards. Additionally, render-blocking CSS and font files are delaying initial page display, and JavaScript code is causing forced reflows that hurt performance further.
Why It Matters:
CSS and font files are blocking initial page render, delaying First Contentful Paint to 2.6 seconds.
How to Fix:
Inline critical CSS directly in the HTML head for above-the-fold content. Use font-display: swap in your Google Fonts CSS to prevent render blocking. Defer non-critical CSS using media='print' onload technique or Astro's client:load directive.
Why It Matters:
JavaScript is causing 112ms of forced reflows by reading layout properties after DOM changes, blocking the main thread.
How to Fix:
Batch DOM reads before DOM writes to avoid layout thrashing. Cache geometric properties like offsetWidth instead of repeatedly querying them. Move layout-triggering JavaScript to requestAnimationFrame callbacks for smoother performance.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.