LCP
Largest Contentful Paint
6.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Execution Time
How to optimize web.dev.floristerias.co
Reduce JavaScript Execution Time
High Impact+25 points estimated
Why It Matters
JavaScript execution takes 2.3 seconds and blocks the main thread for 1.3 seconds, severely impacting Total Blocking Time and user interactivity.
How to Fix
Split your Next.js bundles using dynamic imports for non-critical components. Remove unused Google Tag Manager code (104KB wasted). Implement code splitting with Next.js dynamic() for heavy components that aren't immediately visible. Consider lazy loading analytics scripts after user interaction.
0Poor
What This Score Means
A score of 48 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
802ms
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 Next.js site has poor performance with a score of 48/100, indicating significant issues that need immediate attention. The biggest problem is excessive JavaScript execution time (2.3 seconds) and main-thread blocking (3.1 seconds), which causes your page to become interactive extremely slowly at 14.4 seconds and delays content visibility to 6.2 seconds. Your site is loading 462 KB of unused JavaScript, particularly from Google Tag Manager and analytics scripts, and using outdated JavaScript polyfills that add unnecessary 13 KB of code for modern browsers. Quick wins include removing unused JavaScript code, updating your build process to target modern browsers, implementing better caching strategies for your product images, and optimizing the logo image format from PNG to WebP, which could collectively improve your score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Optimize LCP Image Loading
High Impact+15 points estimatedWhy It Matters:
Your LCP image has a 1.7-second resource load delay and 979ms render delay, contributing to a poor 6.2-second LCP score.
How to Fix:
Add priority={true} to your LCP image component in Next.js to enable fetchpriority='high'. Preload the LCP image using next/head with <link rel='preload' as='image'>. Optimize your CDN cache settings to reduce the 1.7s load delay. Consider using next/image with fill={false} and explicit dimensions for better performance.
Modernize JavaScript Build Target
Medium Impact+8 points estimatedWhy It Matters:
Your bundle includes 13KB of unnecessary polyfills for modern browser features, adding extra parsing and execution overhead.
How to Fix:
Update your Next.js target in next.config.js to 'es2020' or 'esnext' to remove polyfills for Array.prototype.at, Object.hasOwn, and other modern features. Configure your browserslist to exclude legacy browsers if not needed. This will reduce bundle size and improve parsing performance.
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 Next.js Speed Tests
Next.js Performance Resources
Modernize JavaScript Build Target
Your bundle includes 13KB of unnecessary polyfills for modern browser features, adding extra parsing and execution overhead.
Optimize LCP Image Loading
Your LCP image has a 1.7-second resource load delay and 979ms render delay, contributing to a poor 6.2-second LCP score.
Optimize CSS Delivery Strategy
Render-blocking CSS files are creating a 1.2-second delay before content can be painted.
Update JavaScript Build Target
36 KiB of legacy polyfills are unnecessarily delaying LCP by 150ms for modern browsers.