LCP
Largest Contentful Paint
16.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Critical Resource Loading
How to optimize redlinesociety.com
Optimize Critical Resource Loading
High Impact+20 points estimated
Why It Matters
16.1 second LCP is primarily caused by render-blocking CSS and delayed resource loading.
How to Fix
Inline critical above-the-fold CSS directly in theme.liquid. Use Shopify's preload_tag for hero images and fonts. Remove unused CSS rules (69KB savings identified). Defer non-critical stylesheets using media='print' onload technique.
0Poor
What This Score Means
A score of 28 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
522ms
Poor
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
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 28/100. The biggest problem is excessive JavaScript blocking the main thread for over 17 seconds, causing extremely slow loading times - your Largest Contentful Paint takes 16.1 seconds and users can't interact with the page for nearly a minute. The site is loading massive amounts of unused JavaScript (over 2MB) from Google Analytics, marketing tools, and third-party scripts that are completely blocking page rendering. Immediately removing or deferring non-essential JavaScript, especially the duplicate Google Tag Manager scripts and unused marketing pixels, could improve your score by 40+ points and transform your user experience from unusable to acceptable.
Other Optimization Recommendations
Reduce Unused JavaScript Drastically
High Impact+25 points estimatedWhy It Matters:
2.1MB of unused JavaScript is blocking page load and creating 3.3 seconds of total blocking time.
How to Fix:
Remove duplicate Google Tag Manager scripts and consolidate to single implementation. Defer non-critical third-party scripts like OptimOnk, Klaviyo using Shopify's Script Tag API. Use dynamic imports for heavy components loaded only when needed.
Fix JavaScript Execution Performance
High Impact+15 points estimatedWhy It Matters:
17.3 seconds of main thread work and forced reflows are preventing user interactions.
How to Fix:
Break up long JavaScript tasks using setTimeout or requestIdleCallback. Remove legacy JavaScript polyfills for modern browsers (71KB savings). Optimize third-party scripts by loading them after page interactive using Shopify's defer attribute.
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 Critical Resource Chain
Resource load delay of 835ms and network dependency chains up to 10 seconds are preventing fast page rendering.
Eliminate Unused JavaScript Execution
2MB of unused JavaScript is causing 8.5 seconds of execution time and blocking the main thread for nearly 3 seconds.
Fix Critical LCP Element Rendering
Element render delay of 2.1 seconds is causing your LCP to reach 19 seconds, severely impacting user experience.
Fix Cumulative Layout Shifts
Layout shifts score 0.499 (poor) due to unsized images and web font loading causing content to jump during page load.