Real shoppers on iconoflash.com fail Google's loading test (2.7s against a 2.5s limit), and in Google's phone test the main content takes 18.9s. The image Google waits for is a product photo set to lazy-load, so the browser deliberately delays the most important picture. The page also runs two session-recording tools (Hotjar and Lucky Orange) plus a 485 KB tag manager, which block the page for most of a second.
First action
Remove the lazy-load class from the first four product images on the homepage.
How to measure it
LCP at the 75th percentile
- Now
- –
- Target
- Under 2.5s
- By
- 2 months
Steps
Find the LCP image
Confirm in PageSpeed which element is largest.
Shopify developer 1 hour
Load it eagerly
First banner and first product row with fetchpriority high.
Shopify developer 2 hours
Pick one recorder
Keep Hotjar or Lucky Orange, not both.
Ecommerce Manager 1 day
Trim apps and tags
Remove scripts from uninstalled apps; delay tags.
Shopify developer 2 days
Cache theme files
Long cache lifetimes.
Shopify developer 2 hours
Retest
Lab now, field data after 28 days.
Shopify developer weekly
Why it works
Load the first row of product images and the first banner eagerly with a high fetch priority; keep lazy-loading for everything below the fold. Keep one session recorder (or none outside test periods), move tags to load after the page, remove unused apps whose scripts still load, and set long cache lifetimes for theme files. Retest on PageSpeed and watch Search Console's field data for 28 days.
Fashion shoppers browse on phones and leave pages that keep them waiting. Two of the fixes are settings, not redesign, and getting under 2.5s helps conversion and Google rankings at once.
Ready to use
ChecklistPhone speed fixes
[ ] First banner: no lazy-load, fetchpriority="high" [ ] First product row: eager images with width and height set [ ] One session recorder only [ ] Remove scripts from apps no longer used [ ] Delay marketing tags until after load [ ] Long cache lifetimes for theme assets [ ] Allow pinch-zoom in the viewport tag [ ] Recheck Search Console Core Web Vitals in 28 days
Risks and how to handle them
Losing recordings
Keep one recorder and sample sessions.
Theme update overwrites changes
Document the edits.
Evidence
- Google PageSpeedHomepage: real shoppers fail Google's Core Web Vitals on loading (LCP 2.7s at the 75th percentile; the limit is 2.5s), while responsiveness (144 ms) and layout (0.03) pass. In the lab: mobile score 39 (desktop 53); the main content takes 18.9s to appear on a phone, and the element Google waits for is a product image set to lazy-load ("img.lazyload-fade"). The page downloads 3 MB, 1,662 KB of it from 12 third-party services, including Google Tag Manager (485 KB, 472 ms blocking), identixweb (396 KB), Hotjar (276 ms blocking) and Lucky Orange, two session-recording tools. Top fixes: unused JavaScript (about 3.4s), cache lifetimes (about 2.1s), render-blocking requests (about 2s).Source