Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize antoniomadrigal.mx
419KB of unused JavaScript wastes bandwidth and slows down FCP by 150ms.
Implement lazy loading for reCAPTCHA by only loading it when contact forms are visible using Intersection Observer API. Remove or defer Swiper bundle (42KB wasted) until carousel interaction is needed. Use tree shaking to eliminate dead code from bundled scripts.
A score of 84 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 website has good performance with a score of 84/100, but there's significant room for improvement in loading speed. The biggest issue is render-blocking JavaScript files that are preventing the page from displaying content quickly, causing a slow Time to Interactive of 8.8 seconds and delaying the Largest Contentful Paint to 3.5 seconds. The site is loading 419 KiB of unused JavaScript (primarily from reCAPTCHA) and has several scripts blocking the initial render that could save nearly a full second if deferred. Optimizing JavaScript delivery, removing unused code, and implementing proper caching could dramatically improve the user experience and push this site into the excellent performance range.
Why It Matters:
Critical JavaScript blocks initial page render for 910ms, directly delaying both FCP and LCP by 900ms.
How to Fix:
Add 'defer' attribute to welcome.js and welcome-head.js script tags. Move reCAPTCHA script to load asynchronously after page load using window.onload event. Consider inlining small critical scripts directly in HTML to avoid network requests.
Why It Matters:
Poor cache headers for 38KB of resources force unnecessary re-downloads and delay LCP by 150ms on repeat visits.
How to Fix:
Set cache-control headers for static assets to 'max-age=31536000' (1 year) in your server configuration. Add versioning to filenames like app-BXS-Op9n.js for cache busting. Configure CDN cache lifetime to at least 1 month for external libraries like SweetAlert2.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Poor cache headers for 38KB of resources force unnecessary re-downloads and delay LCP by 150ms on repeat visits.
Critical JavaScript blocks initial page render for 910ms, directly delaying both FCP and LCP by 900ms.
Poor cache policies waste 38 KB on repeat visits and slow down returning users.
Render-blocking requests delay LCP and FCP by 1.7 seconds, preventing content from appearing quickly.
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.