The new VP of Growth Marketing is hired to "own the marketing website as a core growth asset, including performance". Today the homepage fails Core Web Vitals for real Chrome users: Interaction to Next Paint is 452 ms and layout shift 0.12, both "needs improvement" (loading is fine at 2.4 s). On Google's mobile test it scores 27, with a 17-second Largest Contentful Paint and 2.4 seconds of blocking script. The shifts come from the hero block and the cookie banner, and much of the unused code is tag manager, two separate Google Ads tags, analytics and a 2023 cookie banner script. For a company that sells the detection of "frustration, rage clicks, and failure points", its own front door is slow to respond.
First action
Defer the tag manager and pixels on the homepage and re-run PageSpeed.
How to measure it
INP at the 75th percentile
- Now
- –
- Target
- Under 200 ms
- By
- 60 days
Steps
Baseline
Field and lab numbers for home, pricing and demo pages.
Web team lead 1 day
Static hero
Server-render the headline; animate after paint if at all.
Web team lead 3 days
Cookie banner
Overlay instead of shifting content; update the script.
Web team lead 2 days
Tags
Load ads, social and analytics tags on idle; merge the Google Ads tags.
Marketing analytics lead 1 week
Trim
Remove unused JavaScript and duplicate font files.
Web team lead 1 week
Budget
Performance budget in CI for the top 20 pages.
Web team lead 1 week
Measure
Demo-form conversion before and after.
Marketing analytics lead 4 weeks
Why it works
Render the hero headline as static text (no word-by-word animation on first paint) and reserve its space; fix the cookie banner so it overlays instead of pushing content; load tag manager, ad and social pixels after the first interaction or on idle; merge the two Google Ads tags; and trim the 3.5 MB page. Set a budget (INP under 200 ms, CLS under 0.1, mobile LCP under 2.5 s in the lab) and check it on every release of the demo and pricing pages too.
Slow responses to taps and jumping layouts cut demo-form completion, especially from paid mobile traffic, and Google uses Core Web Vitals as a ranking signal. Fixing them is the cheapest conversion gain available to the growth team.
Ready to use
ChecklistHomepage performance fixes
[ ] Hero headline server-rendered as plain text [ ] Hero height reserved (no shift) [ ] Cookie banner as overlay, current script version [ ] Tag manager, ads and social pixels on idle or first interaction [ ] One Google Ads tag instead of two [ ] Unused JavaScript removed [ ] Budget: INP < 200 ms, CLS < 0.1, lab LCP < 2.5 s [ ] Same checks on /pricing/ and the demo page
Risks and how to handle them
Losing tracking data
Deferring tags keeps every event; check attribution after the change.
Design team wants the animation
Keep it, but start it after the first paint.
Evidence
- Google PageSpeedHomepage, mobile test run October 21, 2026: performance 27, Largest Contentful Paint 17.0 s, Total Blocking Time 2,430 ms, First Contentful Paint 8.3 s, 3.5 MB transferred, about 533 KB of unused JavaScript (largely tag manager, two Google Ads tags, analytics and a 2023 cookie banner script). Real Chrome users on the homepage (Chrome UX Report, 75th percentile): LCP 2.4 s is good, but Interaction to Next Paint is 452 ms and Cumulative Layout Shift 0.12, both "needs improvement", so the page does not pass Core Web Vitals. The two layout shifts come from the hero block and the cookie banner.Source
- HiringVP, Growth Marketing (posted September 30, 2026): leads "Pendo's full growth engine from top-of-funnel awareness through qualified pipeline creation" across "paid search, paid social, SEO/GEO, content-driven acquisition". Will "Own the marketing website as a core growth asset, including performance, conversion rate optimization, experimentation, lead routing, and continuous improvement of the buyer journey and demo experience", build "clear attribution models", "a rigorous testing culture across acquisition, the website, onboarding, and lifecycle", and drive product-led and lifecycle growth. Nice to have: "scaling growth in hybrid self-serve and enterprise environments".Source
- Your websiteHomepage: title "Pendo | Product Context for Your Apps and AI Agents"; H1 "Shipping product got easy. Knowing if it worked didn't."; "Join 14,000+ teams", "40 Trillion Events / 1 Billion+ Users / 18K+ Agents and apps"; "Headless Pendo" brings product context into "Claude, ChatGPT, Fin, your IDE, and any MCP client"; Session Replay and analytics "Surface frustration, rage clicks, and failure points fast". Proof points include "3x faster outreach to at-risk customers" and "71% faster roadmap decisions".Source
- Your websitePricing page: Free (500 monthly active users), then Base, Core and Ultimate, each "Request pricing" with "Custom MAU volume"; Novus "Free (no credit card required)" in open beta; Predict and Agent Analytics as add-ons; "Our pricing philosophy": "No bait and switch". The Free plan's "Start now" goes to app.pendo.io/register; Novus registers separately at novus.pendo.io.Source