Zegashop sells speed: "optimized for Google Core Web Vitals", "Web Core Vitals (93+)" on every plan and "95+" on the partner page. Yet Google's PageSpeed test gives zegashop.com 45/100 on a phone, the headline takes 9.4 s to appear, and real visitors fail Core Web Vitals. A store owner or agency who checks the claim on the homepage itself sees the opposite of the pitch.
First action
Defer the Facebook and Google Tag Manager scripts and re-run PageSpeed on a phone.
How to measure it
Homepage mobile performance
- Now
- –
- Target
- 90+ and Core Web Vitals passed
- By
- 60 days
Steps
Baseline
Record lab and real-user scores for home, pricing and partner pages.
Lead Front-End Developer 1 hour
Cut third parties
Delay Facebook, ad, session-recording and IP lookup scripts until interaction.
Lead Front-End Developer 2 days
Static hero
Server-render the H1 and hero with no blocking requests.
Lead Front-End Developer 2 days
Images and caching
Modern formats, sizes and long cache lifetimes.
Lead Front-End Developer 1 day
Split the bundle
Remove unused JavaScript and legacy polyfills.
Lead Front-End Developer 1 week
Show the score
Live PageSpeed badge with a "test it yourself" link.
Head of Marketing 1 day
Watch real users
Track the Chrome UX Report monthly.
Lead Front-End Developer monthly
Why it works
Treat the homepage as the product demo. Load Facebook, the ad tag, Smartlook and the other third parties only after interaction or consent, render the H1 and hero as plain server HTML with no blocking scripts, compress the 1.1 MB of images, and cut the 536 KB of unused JavaScript. Then put the live PageSpeed score on the homepage with a "test it yourself" link, and do the same on /pricing and the partner page.
The claim becomes proof a visitor can check in ten seconds, and every agency comparing builders by PageSpeed sees Zegashop win on its own site first.
Ready to use
ChecklistHomepage speed checklist
[ ] Facebook pixel and GTM load after first interaction [ ] IPONWEB, Smartlook, catchgrow.ai and ip-api.com removed or delayed [ ] H1 and hero are server-rendered HTML [ ] Hero image in AVIF/WebP with width and height set [ ] Unused JavaScript split out of the main bundle [ ] Cache lifetimes of a year on static files [ ] Mobile PageSpeed 90+ on home, pricing and partner pages [ ] Live score badge with a "test it yourself" link
Risks and how to handle them
Marketing tags lose data
Load them after interaction; keep server-side conversion events.
Real-user data lags
The Chrome UX Report is a 28-day average, so expect the field result a month after the fix.
Evidence
- Your websiteSpeed is the core promise. Homepage: "build a stunning website optimized for Google Core Web Vitals" and "We Provide Best Performance | Core Web Vitals". Every plan on the pricing page lists "Web Core Vitals (93+)". The partner page says "Zegashop websites achieve 95+ Google Core Web Vitals scores for better SEO and higher conversions".Source
- PageSpeed testGoogle PageSpeed Insights on www.zegashop.com (October 20, 2026): mobile performance 45/100 (desktop 64). On a phone the main content (the H1 "AI E-commerce Website Builder with Growth Strategy") takes 9.4 s to appear against a 2.5 s target; the page is ready to use at 12.3 s. Real visitors (Chrome UX Report) fail Core Web Vitals on LCP: 3.4 s, with a 1.5 s server first byte. The homepage downloads 7.1 MB in 69 requests.Source
- PageSpeed testWhat slows the homepage: 623 KB from 13 third-party services, led by Facebook (278 KB, 413 ms blocking) and Google Tag Manager (180 KB, 498 ms blocking), plus an ad service (IPONWEB), Smartlook session recording, catchgrow.ai and ip-api.com. Google's suggested fixes: remove unused JavaScript (536 KB, about 2.1 s), render-blocking requests (about 0.5 s), legacy JavaScript, 600 KB of image savings and 298 KB of better caching.Source