India is a harder lab than the blog posts assume
CrUX for Indian origins often shows poorer LCP than the same stack in Frankfurt. That is devices, networks, and hosting regions — not karma. Host close to users or use a CDN that actually has Indian POPs.
Do not compare your lab Lighthouse on a MacBook to a competitor’s marketing screenshot. Compare GSC field data, same country, same device class.
Office fibre is not a persona
Throttle to 4G and a mid-range phone when you accept a build. If the intern only tests on Wi-Fi, you will ship a lie.
CLS: sticky bars, fonts, and late ads
Reserve space for images, embeds, and announcement bars. Load fonts with fallback metrics. Never inject a 72px coupon bar after paint. Ad slots need min-height.
WhatsApp floating buttons that load late and push content are a Chennai special. Put them in a reserved corner from first paint or use a static CSS button.
Hosting, PHP, and the TTFB nobody named
Shared ₹99 hosting with 40 plugins will miss LCP before the image even starts. Object cache, PHP version, and a host that has heard of India are prerequisites for WordPress CWV.
Next.js on a serious runtime with static generation for marketing URLs removes a lot of PHP lottery. It does not remove bad images.
Migration week is when TTFB explodes
DNS, origin in US-East, and no CDN is a common “new Next.js site feels slow in Tambaram” story. Check TTFB from an Indian probe, not only from Vercel’s US view.
WordPress plugin tax in practice
Each “all-in-one SEO + security + animation + slider + backup + chat” stack fights INP. We ship WordPress with a short plugin list and a performance budget in the handover.
Do not stack three image optimisers. They often re-compress and break. One pipeline, owned.
Page builders can pass CWV — until someone “makes it pop”
The tenth animation is where INP dies. Editorial training is part of technical SEO. Without it, monthly reports become archaeology.
Next.js advantages and the ways teams still fail
App Router, image component, and static pages are a head start. Client-only dashboards wrapped as marketing sites, unbounded client components, and four analytics SDKs throw it away.
Choose Next.js when you want ownership and speed, not because a reel said React ranks. The crawler wants HTML. SSR or static is the SEO path.
Hydration error theatre
Mismatched server/client markup delays interactivity. INP and UX both suffer. Treat hydration warnings as SEO bugs, not console noise.
How Google uses CWV versus how customers use the phone
Ranking: decent vitals help when competitors are close. Business: slow pages drop form fills even when you rank. For local pack, a tappable number on a light page beats a cinematic clinic film that never plays.
AI Overviews will not quote your LCP. They might skip a page that is hard to fetch. Speed is hygiene for technical SEO, not the whole AEO strategy.
Passing CWV on desktop only
India is phone-first. Desktop green / mobile red means you are not done. GSC splits them. Believe mobile.
The fix order that moves both rankings and rupees
1) Hosting and TTFB. 2) LCP image. 3) Kill or defer third-party JS. 4) Fonts and CLS slots. 5) Builder/JS diet. 6) Then micro-optimise. Reverse that order and you polish a 4 MB hero.
Report field metrics monthly inside SEO. If the theme cannot hit the budget, quote a rebuild: ₹28,000 business or ₹50,000 + ₹15,000/mo dynamic + SEO.
Do not buy a “speed plugin” instead of a diagnosis
Caching plugins help WordPress TTFB and sometimes LCP. They cannot reserve CLS or write smaller JS. Diagnosis first — consult.
What we include in a build versus a retainer
Builds include a budget, compressed media, and a plugin/script policy. Retainers include GSC monitoring and bounded fixes. Rescues of abandoned Elementor museums are projects.
Ads accounts should point at fast landings. A ₹20,000/mo media retainer on a 9-second LCP is lighting money on OMR traffic. Fix the URL or pause the campaign.
GBP cannot save a lead who bounced
Maps gets the tap; the site must finish the job. GBP vs website is both, not either.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.