Google's phone test finds one script, a page-builder compatibility file loaded from api-dispatcher.bily.ai, using 2.9 s of processing time on the homepage, twice what Cozy Earth's own page code needs. In total the page spends 7.9 s running scripts. Real shoppers feel it: across the site, taps take 496 ms to respond against Google's 200 ms limit, the homepage's main content takes 3.84 s on phones, and loading has got 23% slower in a year. The site fails Core Web Vitals on both counts.
First action
List the templates that use the page builder and test the homepage without its script.
How to measure it
Site-wide INP (phones)
- Now
- –
- Target
- under 200 ms
- By
- 60 days
Steps
Audit
Which templates and sections depend on the page builder.
Web Development Lead 2 days
Test without it
Homepage and one collection on a staging theme.
Web Development Lead 2 days
Load only where needed
Or rebuild those sections natively.
Web Development Lead 1 week
Delay tags
Consent, Google Ads and Facebook after first interaction.
Web Development Lead 2 days
Check tracking
Purchases still recorded in ads platforms.
Performance Marketing Manager 2 days
Fix slow taps
Menu, Quick Add and cart drawer handlers.
Web Development Lead 1 week
Watch field data
Chrome UX Report and PageSpeed monthly.
Director of E-commerce monthly
Why it works
Find which pages still need the page builder and load its script only there (or rebuild those sections in the theme). Then delay the consent, Google Ads and Facebook scripts until after the first tap or scroll, and recheck the add-to-cart and menu taps, which are the interactions behind the slow INP.
Shoppers deciding on a $258 sheet set mostly browse on phones; faster taps and pages convert better, and Google uses these same measures in ranking. Removing one script is the cheapest speed gain available.
Ready to use
ChecklistScript diet
[ ] Page-builder script only on templates that need it [ ] Consent script loaded after first paint [ ] Google Ads and Facebook delayed until interaction [ ] Server-side purchase events checked [ ] Quick Add and menu tap handlers profiled [ ] PageSpeed phone test re-run [ ] Chrome UX Report checked after 28 days
Risks and how to handle them
Builder sections break
Rebuild the few that matter before removing the script everywhere.
Lost ad attribution
Use server-side events and compare purchase counts before and after.
Evidence
- PageSpeed testGoogle PageSpeed test of the homepage on a phone (October 20, 2026): performance 37/100; main content at 6.1 s in the lab, 2,030 ms of blocking time, 7.9 s of script execution and 11.6 s of main-thread work; 7.1 MB. The single most expensive script is a page-builder compatibility script loaded from api-dispatcher.bily.ai, at 2.9 s of processing, twice the cost of the page's own code (1.4 s); the TrueVault consent script (0.43 s), the Google Ads tag (0.31 s) and the Facebook pixel (0.28 s) follow. Real Chrome visitors on phones: the homepage's main content takes 3.84 s (target 2.5 s) and first content 3.17 s; across the whole site, taps take 496 ms to respond (INP, limit 200 ms) and main content 3.14 s, so the site fails Core Web Vitals on loading and responsiveness.Source
- Chrome UX ReportReal-visitor loading time for cozyearth.com (75th percentile, main content) is 3.18 s and has got 23% slower over the past year.Source
- Your websiteHomepage: banner "Free Domestic Shipping on orders $100+" and "Bundle and save – 10% off when you buy 3+ items"; "Shop HSA/FSA Eligible Products"; an Oprah's Favorite Things collection in the menu. Full-price product tiles read "Price is up to 0% off, is normally $258. Can be $258." (Bamboo Sheet Set) and the same for other products. One homepage link points to /open%20, which returns a 404; 8 images have no alt text.Source