LCP
Largest Contentful Paint
7.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Execution Time
How to optimize mycocos.cl
Reduce JavaScript Execution Time
High Impact+20 points estimated
Why It Matters
4.5 seconds of JavaScript execution time creates 3 seconds of Total Blocking Time, preventing user interactions.
How to Fix
Remove unused JavaScript from Google Tag Manager scripts (saving 337KB). Use Shopify's Web Workers for heavy computations. Implement code splitting for the MercadoPago security.js. Move non-critical Klaviyo and Smile.io scripts to load after user interaction using intersection observers.
0Poor
What This Score Means
A score of 39 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
547ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Shopify site has severe performance issues with a critically low score of 39/100. The biggest problem is excessive JavaScript execution taking over 4.5 seconds, which is blocking the main thread and causing a devastating 29-second delay before the page becomes fully interactive. The site is loading massive amounts of unused JavaScript (1.3MB waste) and CSS (57KB waste), while also suffering from forced reflows that repeatedly trigger expensive layout calculations. Reducing JavaScript payloads, eliminating unused code, and optimizing the numerous third-party scripts from Google Analytics, Facebook, and other services could dramatically improve the score by 30+ points and transform the user experience from unusable to acceptable.
Other Optimization Recommendations
Optimize Critical Rendering Chain
High Impact+25 points estimatedWhy It Matters:
The longest dependency chain takes 8.9 seconds, directly blocking page rendering and causing the poor LCP of 7.1s.
How to Fix:
Remove unused preconnect hints to appsolve.io and fonts.shopifycdn.com. Inline critical CSS from styles.css (1.6KB) to eliminate render-blocking. Use Shopify's Script Tag API to defer non-essential tracking scripts like Google Analytics until after page load.
Optimize Image Delivery System
Medium Impact+12 points estimatedWhy It Matters:
Images are oversized and unoptimized, wasting 246KB and delaying LCP by 300ms.
How to Fix:
Use Shopify's responsive image system with srcset for different screen sizes. Convert product images to WebP format through Shopify's image transformation API. Implement proper image dimensions (current 1080x1080 displayed as 116x116). Add loading='lazy' to below-the-fold product images in Liquid templates.
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 Shopify Speed Tests
Shopify Performance Resources
Optimize Image Delivery System
Images are oversized and unoptimized, wasting 246KB and delaying LCP by 300ms.
Optimize Critical Rendering Chain
The longest dependency chain takes 8.9 seconds, directly blocking page rendering and causing the poor LCP of 7.1s.
Fix Forced Reflow Issues
Layout thrashing from JavaScript DOM queries causes 540ms of unnecessary rendering work, degrading user experience.
Reduce JavaScript Execution Time
JavaScript blocks the main thread for 3.1 seconds and causes 1,350ms of Total Blocking Time, preventing user interactions.