Core Web Vitals for busy marketing teams (India edition)

Your Google Search Console says your LCP is "Poor" and your developer is on a 3-week sprint. What can a marketing team actually do to improve Core Web Vitals without writing a line of code? More than you think. Here is the India-specific playbook.

What the three metrics mean in plain terms

• LCP (Largest Contentful Paint): How long until the biggest visible element (usually your hero image or H1) is loaded. Google wants this under 2.5 seconds. Most Indian WordPress sites on shared hosting land at 4–8 seconds on mobile.
• INP (Interaction to Next Paint): How fast your page responds when a user clicks something. Heavy tag manager setups and chat widgets are the main offenders. Target under 200ms.
• CLS (Cumulative Layout Shift): How much the page jumps around while loading. Ads, late-loading fonts, and images without defined dimensions cause this. Target under 0.1.

Marketing-team fixes for LCP (no developer needed)

1. Compress your hero image — Use ShortPixel (free up to 100 images/mo) or TinyPNG. A 2MB JPEG hero image becoming a 180KB WebP is often the single biggest LCP win.
2. Add a CDN — Cloudflare free plan puts your images closer to users. Indian users in Mumbai, Bengaluru, Chennai, and Delhi all get served from nearby edge nodes.
3. Enable WordPress lazy loading for images — WP Admin → Media → tick "lazy load images." This is native since WordPress 5.5 and costs nothing.
4. Remove unused above-fold fonts — If your hero section loads 4 Google Fonts variants but only uses two, remove the unused ones from your theme settings.

Marketing-team fixes for INP

INP problems are almost always caused by third-party scripts. Common culprits on Indian marketing sites:

• Tag Manager with 15+ tags including Facebook Pixel, Google Analytics 4, Hotjar, and chat widgets loaded on every page
• Tawk.to and Intercom chat widgets loaded on landing pages where users rarely chat
• Heavy slider plugins (Revolution Slider, Layer Slider) loading on pages that only show one image

Fix: In Google Tag Manager, trigger your chat widget and Hotjar only on high-intent pages (contact, pricing, demo), not on every blog post. This alone can drop INP from 800ms to under 200ms.

Marketing-team fixes for CLS

• Add explicit width and height to all images in your WordPress media library (done by default in WP 5.5+)
• If you run display ads (Google AdSense, DAN), reserve ad slot height in CSS so the layout doesn't shift when the ad loads
• Fix late-loading cookie consent banners by loading them synchronously, not after page render

Check real Indian user data — not lab scores

PageSpeed Insights lab scores use a simulated throttled connection from a US data centre. They do not reflect what Jio users in Tier 2 cities actually experience. For real data:

1. Open Google Search Console → Core Web Vitals report
2. Check both Mobile and Desktop tabs separately — Indian mobile users often have 3x worse scores than desktop
3. Click "Open Report" to see which specific page templates are failing

Fix the template with the most failing URLs first — usually your home page, product listing, or landing page templates.

When hosting is the bottleneck

If you have done the above and LCP is still above 3 seconds, the problem is likely server response time (TTFB). Signs: PageSpeed shows "Reduce initial server response time" as a top opportunity. Fix: upgrade from shared hosting to a cloud hosting plan with LiteSpeed or Nginx, or move to a Mumbai VPS where you can configure server-level caching.

Frequently asked questions