Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize mayacollection.se
Product images are 4x larger than needed, wasting 2.4MB and delaying LCP by 5.8 seconds.
Configure Shopify's responsive image settings to serve appropriately sized images. Update Next.js Image components to use srcSet with multiple breakpoints (274w, 548w, 822w). Enable automatic WebP conversion in your CDN settings. Add priority loading to above-the-fold product images.
A score of 65 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 Next.js/Shopify site has poor performance with a score of 65/100, particularly struggling with slow loading times. The biggest problem is excessive JavaScript execution taking 3.5 seconds of main thread work, which is blocking user interactions and causing the page to become fully interactive only after 8.2 seconds. The site is also serving oversized product images that are 4x larger than needed, wasting over 2MB of bandwidth, and these images lack proper dimensions causing layout shifts. Optimizing JavaScript payloads, properly sizing images with responsive formats, and adding explicit width/height attributes to images could dramatically improve loading speed and user experience.
Why It Matters:
JavaScript execution blocks the main thread for 3.5 seconds, preventing user interactions and increasing TBT to 450ms.
How to Fix:
Update your Next.js build configuration to target modern browsers and remove legacy polyfills (saves 14KB). Split large JavaScript chunks using dynamic imports for non-critical features. Move third-party scripts like Clarity analytics to web workers or defer until after page interactive.
Why It Matters:
Critical CSS files delay first paint by 160ms and prevent users from seeing content immediately.
How to Fix:
Inline critical CSS directly in your Next.js pages using styled-jsx or CSS-in-JS. Move non-critical stylesheets to load asynchronously using Next.js dynamic imports. Configure your build process to automatically extract and inline above-the-fold CSS.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Images are oversized and poorly compressed, wasting 613KB of bandwidth and slowing page load.
156KB of unused JavaScript is blocking page load and delaying LCP by 1.2 seconds.
LCP is critically slow at 8.7 seconds, severely impacting user experience and Core Web Vitals score.
Missing preconnect hints to staging-api.tailzaar.com waste 300ms on connection setup.