Google's field data from real Chrome visitors shows Beechtree's main content appears fast (LCP 1.9 s, passing) and nothing jumps (layout shift 0). The one failure is responsiveness: Interaction to Next Paint is 295 ms against Google's 200 ms limit, so the site fails Core Web Vitals on that metric alone. Every tap on a size, a colour swatch, a filter or Add to Cart waits on a busy main thread. The biggest single cause on the homepage is Google Tag Manager: 355 KB and 441 ms of main-thread blocking, more than all other third parties combined, alongside 12 other services (Clarity, Snapchat, Google Ads, Bing Ads, Tapad and more). Total blocking time is 263 ms on mobile and 398 ms on desktop.
First action
Export the GTM container and list every tag with its trigger, owner and last time its data was used.
How to measure it
Field INP, mobile
- Now
- –
- Target
- Under 200 ms (pass Core Web Vitals)
- By
- 60 days
Steps
Inventory tags
Every GTM tag with trigger, owner, purpose and whether its data is used today.
E-commerce Manager 2 days
Remove and merge
Pause tags nobody owns; keep one tool per job and remove duplicates.
Performance Marketing Manager 2 days
Delay the rest
Fire ad pixels after interaction or on key events rather than on every page view.
Shopify Developer 3 days
Fix the theme
Defer render-blocking scripts, drop unused JavaScript and compress hero images.
Shopify Developer 1 week
Test key taps
Measure swatch, size, filter and Add to Cart responsiveness on a mid-range Android phone.
Shopify Developer 1 day
Check conversions still track
Compare ad-platform purchase counts with Shopify orders for a week.
Performance Marketing Manager 1 week
Watch the field data
Re-run PageSpeed weekly; real-visitor data updates over a 28-day window.
E-commerce Manager 4 weeks
Why it works
Run a tag audit inside Google Tag Manager: list every tag, its owner and whether anyone still uses its data. Remove tags nobody owns, keep one tool per job (for example one session-recording tool and one source of truth for conversions), and move the remaining marketing pixels to fire after the page is interactive or on consent and purchase events instead of on every page load. Then fix what PageSpeed flags on the theme itself: render-blocking requests (about 1.15 s), 148 KB of unused JavaScript and 433 KB of image savings. Check INP again on the homepage, a collection page and a product page, which are where shoppers tap most.
Field LCP already passes, so the gain is in how quickly the store reacts once a shopper starts browsing on a phone. Faster taps on swatches, filters and Add to Cart reduce abandoned sessions, and passing Core Web Vitals removes a ranking disadvantage on Google for every product and collection page at once. It is also verifiable by anyone: the public PageSpeed report shows the number moving.
Ready to use
ChecklistTag and responsiveness audit
[ ] Export GTM container; list tags, triggers, owners [ ] Mark tags whose data nobody used in 90 days [ ] One session-recording tool, one analytics source of truth [ ] Ad pixels fire on interaction or key events, not page load [ ] Defer render-blocking theme scripts [ ] Remove unused JavaScript (148 KB flagged) [ ] Compress hero and slider images (433 KB flagged) [ ] Enlarge small touch targets [ ] Test swatch, size, filter, Add to Cart on a mid-range Android [ ] Re-check PageSpeed field INP weekly until under 200 ms
Risks and how to handle them
Ad platforms lose conversion data
Keep purchase events firing immediately and compare counts against Shopify orders before and after.
Teams object to losing a tool
Pause rather than delete for 30 days and restore anything someone shows they use.
Evidence
- Google PageSpeedReal Chrome visitors to the homepage (field data, November 3, 2026): Interaction to Next Paint 295 ms, above Google's 200 ms "good" limit, so the site fails Core Web Vitals on INP alone; Largest Contentful Paint 1.9 s and layout shift 0 both pass; server response 568 ms; LCP trend steady.Source
- Google PageSpeedThird-party code on the homepage: 13 services, 576 KB. Google Tag Manager is the largest at 355 KB and 441 ms of main-thread blocking; Microsoft Clarity 109 ms; Snapchat 74 ms over 9 requests; plus Google Analytics, Google Ads, Bing Ads, Tapad, dengage, BaadMay, Ahrefs and Shop. Total blocking time 263 ms on mobile and 398 ms on desktop. Accessibility 97/100, with one issue: touch targets too small or too close together.Source
- Google PageSpeedLab test of the homepage (November 3, 2026): mobile performance 69/100, desktop 64/100; mobile LCP 12.7 s, and the element Google measures as the main content is the notice "Dear Customer, For International orders, please switch to our global site."; the page weighs 2.9 MB in 218 requests, with 689 KB of JavaScript and 1,287 KB of images; estimated savings: render-blocking requests 1.15 s, unused JavaScript 148 KB, images 433 KB.Source