Google's data from real Chrome users shows ridge.com fails Core Web Vitals on one measure only: responsiveness. Interaction to Next Paint is 437 ms against a 200 ms target, while loading and layout pass. That is the delay after a shopper taps a finish swatch, opens the menu or presses Add to Cart. In Google's phone test the main thread is busy for 8.6 seconds, Google Tag Manager alone loads 1.5 MB and blocks about 2 seconds, and 1.2 MB of JavaScript goes unused. The homepage loads 46 third-party services, including two heatmap tools (heatmap.com and Hotjar), two experiment tools (Intelligems and GrowthBook) and seven ad pixels.
First action
Export the Tag Manager container and list every tag with an owner.
How to measure it
INP at the 75th percentile
- Now
- –
- Target
- under 200 ms
- By
- 60 days
Steps
Inventory tags
Every script, owner, purpose, last used.
eCommerce Manager 2 days
Remove orphans
Pause tags with no owner.
eCommerce Manager 1 day
One tool per job
One heatmap and one experiment tool per page.
eCommerce Manager 1 week
Delay pixels
Load ad pixels after interaction or server-side.
Performance Creative Manager 1 week
Defer widgets
Chat, reviews and affiliate scripts on idle.
Front-end Developer 1 week
Fix long tasks
Swatch, menu and cart handlers.
Front-end Developer 2 weeks
Monitor
Real-user INP weekly.
eCommerce Manager weekly
Govern
Owner and end date for every new tag.
eCommerce Manager ongoing
Why it works
Run a tag audit: list every script with its owner, purpose and last-used date, and remove or pause anything without a current owner. Keep one heatmap tool and one experiment tool on any given page. Move ad pixels and non-essential widgets (chat, reviews below the fold, affiliate and quiz scripts) to load after the first interaction or when idle, and move pixels to server-side events where the ad platforms support it. Break up long tasks in the theme's swatch, cart and menu code. Track INP from real users weekly (Chrome UX Report or a real-user monitoring script) and set a rule that every new tag needs an owner and a removal date.
Faster taps mean fewer abandoned swatch changes and add-to-carts on mobile, where most DTC traffic is, and a lighter page also lowers ad costs through better landing-page experience. Ridge already passes on loading, so responsiveness is the one fix between it and a full Core Web Vitals pass.
Ready to use
ChecklistTag audit sheet columns
Tag | Vendor | Owner | Purpose | Pages | Load timing (now / proposed) | Last used | Keep, defer, server-side or remove | Removal date
Risks and how to handle them
Attribution gaps when pixels move
Run server-side events alongside for two weeks before switching.
Teams lose a tool they rely on
Agree which tool stays per job with each owner.
Evidence
- Google PageSpeedridge.com homepage (tested October 20, 2026): real Chrome users fail Core Web Vitals on responsiveness, with Interaction to Next Paint at 437 ms (target 200 ms), while loading (LCP 1.9 s) and layout stability (CLS 0.01) pass. Mobile lab score 44/100: 1.9 s of total blocking time, 8.6 s of main-thread work, 7.2 MB over 514 requests, 4.1 MB of JavaScript of which about 1.2 MB is unused; Google Tag Manager alone loads 1.5 MB and blocks about 2 s; the main hero image has no alt text.Source
- Google PageSpeedThe homepage loads 46 third-party services, including two heatmap or session tools (heatmap.com and Hotjar), two experiment tools (Intelligems and GrowthBook), an attribution tool (Northbeam), ad pixels for Facebook, Google, Snapchat, Reddit, LinkedIn, Taboola and Outbrain, plus Klaviyo, Postscript, Okendo, Richpanel, Superfiliate, Fondue and an IP lookup service.Source