LCP
Largest Contentful Paint
8.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render Blocking Resources
How to optimize flotajoyeria.com.ar
Eliminate Render Blocking Resources
Medium Impact+8 points estimated
Why It Matters
Google Fonts CSS is blocking first contentful paint by 900ms, delaying initial page render.
How to Fix
Preload the Google Fonts CSS file using <link rel='preload' href='fonts-url' as='style'>. Use font-display: swap in your CSS to show fallback fonts immediately. Consider self-hosting fonts to eliminate external requests and improve cache control.
0Needs Improvement
What This Score Means
A score of 66 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
122ms
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 jewelry website has poor performance with a score of 66/100, indicating significant user experience issues. The biggest problem is the extremely slow Largest Contentful Paint of 8.6 seconds, primarily caused by oversized product images that are 1024x1024 pixels but displayed at only 380x380 pixels, wasting 550 KiB of unnecessary downloads. The site is also loading 141 KiB of unused JavaScript from Google Analytics, Facebook tracking, and store scripts that could be deferred or removed. Additionally, the main product image has lazy loading enabled when it should load immediately with high priority since it's the largest visual element users see first.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
141 KiB of unused JavaScript is delaying LCP by 750ms and blocking initial render.
How to Fix:
Audit and remove unnecessary tracking scripts like Google Analytics and Facebook Pixel if not essential. Enable tree-shaking in your build process to eliminate dead code. Consider loading analytics scripts asynchronously after page load using defer or async attributes.
Optimize LCP Image Loading
High Impact+18 points estimatedWhy It Matters:
The main product image is lazy-loaded and oversized, significantly delaying LCP by 1.35 seconds.
How to Fix:
Remove loading='lazy' from the main product image and add fetchpriority='high' attribute. Serve appropriately sized images (380x380) instead of 1024x1024 for the display size. Use responsive image srcset to serve optimal sizes for different viewports.
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 Generic Speed Tests
Generic Performance Resources
Improve Image Delivery Efficiency
Images waste 82 KiB due to oversized dimensions and poor compression, slowing down page rendering.
Optimize LCP Image Loading
The main product image uses lazy loading and lacks priority hints, delaying the largest contentful paint.
Remove Render-Blocking Font Requests
Google Fonts CSS is blocking initial render and delaying FCP by 750ms.
Optimize LCP Image Performance
The LCP image takes 9.6 seconds to load and could be optimized for 550KB savings and 2.95s improvement.