Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize antoniomadrigal.mx
Render-blocking requests delay LCP and FCP by 1.7 seconds, preventing content from appearing quickly.
Defer the Google reCAPTCHA script by loading it only when needed using async/defer attributes. Inline critical CSS from Google Fonts or use font-display: swap. Move welcome-head.js to load after initial render or defer its execution.
A score of 70 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 moderate performance issues with a score of 70/100, but users are experiencing frustratingly slow load times with pages taking nearly 9 seconds to become fully interactive. The biggest problem is render-blocking resources (JavaScript files, Google Fonts, and reCAPTCHA) that are preventing the page from displaying content quickly, causing an estimated 1.7-second delay in when users first see anything meaningful. Additionally, the site is loading over 400KB of unused JavaScript code, particularly from Google reCAPTCHA and Swiper components that aren't being fully utilized. Fixing these blocking resources and removing unused code could dramatically improve load times and boost the performance score by 20-30 points.
Why It Matters:
418 KB of unused JavaScript delays LCP by 1.6 seconds and blocks the main thread unnecessarily.
How to Fix:
Lazy-load reCAPTCHA only when forms are interacted with instead of on page load. Remove or defer the unused Swiper library (97% unused). Split JavaScript into critical and non-critical bundles using code splitting.
Why It Matters:
Poor cache policies waste 38 KB on repeat visits and slow down returning users.
How to Fix:
Set long-term cache headers (1 year) for static assets like app-BXS-Op9n.js and welcome.js. Add cache-busting via filename hashing for updates. Configure your server to set proper Cache-Control headers for JavaScript and CSS files.
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.
419KB of unused JavaScript wastes bandwidth and slows down FCP by 150ms.
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.