Real visitors to cleanchoiceenergy.com fail Core Web Vitals on one measure only: taps take 332 ms to respond, against a 200 ms target, while loading speed passes. The biggest cause on the page is the Genesys Cloud chat service, which downloads 1,155 KB over 31 requests and blocks the main thread for 852 ms before anyone asks a question. Tag Manager adds another 702 ms.
First action
Measure how many homepage visitors open chat; it is usually a small share.
How to measure it
Interaction to Next Paint, 75th percentile
- Now
- –
- Target
- under 200 ms
- By
- 60 days
Steps
Check chat use
Share of visitors who open chat.
Marketing Analytics Manager 1 day
Build the facade
Static chat button that loads Genesys on click.
Web Engineering Lead 2 days
Delay tags
Non-essential Tag Manager tags after first interaction.
Web Engineering Lead 2 days
Test enrollment
ZIP entry and sign-up on slow phones.
Web Engineering Lead 1 day
Retest
PageSpeed lab and real-visitor data.
Web Engineering Lead weekly
Compare
Enrollment rate before and after.
Marketing Analytics Manager 4 weeks
Why it works
Replace the chat script with a lightweight "Chat with us" button that loads Genesys only when clicked (or after the visitor has been idle for a few seconds), and move non-essential tags in Tag Manager to fire after the first interaction. Retest in PageSpeed and watch the real-visitor responsiveness number over the next 28 days.
The homepage and plan pages are where paid traffic lands and where the enrollment journey starts. Pages that react instantly to the ZIP code field and the "Sign Up" button convert better on phones, and passing Core Web Vitals also helps in search.
Ready to use
ChecklistResponsiveness fix list
[ ] Count chat opens per 1,000 homepage visits [ ] Static "Chat with us" button; load Genesys on click [ ] Fire Hotjar, Clarity and ad tags after first interaction [ ] Remove duplicate monitoring if Datadog and New Relic overlap [ ] Retest PageSpeed (lab) and watch 28-day real-visitor INP [ ] Compare enrollments per visit before and after
Risks and how to handle them
Fewer chats started
Keep the button visible and fast to open.
Lost attribution
Test each delayed tag in Tag Manager preview first.
Evidence
- PageSpeed testGoogle PageSpeed for the cleanchoiceenergy.com homepage (October 20, 2026). Real Chrome visitors fail Core Web Vitals on responsiveness: taps take 332 ms to respond (good is under 200 ms), while the main content appears in 1.6 s and layout shift is 0.03. The mobile lab test scores 53 out of 100, with the main content at 4.9 s and 1,003 ms of blocking time; the page downloads 3.5 MB, 2.9 MB of it from third parties, and about 1 MB of JavaScript goes unused.Source
- PageSpeed testThird parties on the homepage, from the same test: the Genesys Cloud chat service (mypurecloud.com) is the largest at 1,155 KB over 31 requests with 852 ms of main-thread blocking, ahead of Google Tag Manager (710 KB, 702 ms) and Facebook (251 KB, 237 ms). Also loaded: Invoca call tracking, Hotjar, Microsoft Clarity, Segment, Google Analytics, Datadog, New Relic, Trustpilot and ad tags for Google, Bing, Amazon, Yahoo and Beeswax. Images without alt text and low-contrast text are flagged.Source
- Your websiteHomepage (read through programmable.info, October 20, 2026): "Switch to Clean Electricity for Your Home": "Power your home with 100% clean energy, with no installations and no change to your utility. Every customer helps us build more solar farms in the U.S." Sign-up is at /enroll; two phone numbers are listed. cleanchoice.com redirects here.Source