Core Web Vitals for Thai mobile users (3G/4G Android reality)

Core Web Vitals — Google's user-experience metrics — became a direct ranking factor in 2021 and have only grown in weight since. Most WordPress sites CWV advice online assumes the US/EU benchmark device: an iPhone 14+ on fibre or 5G. That's not the Thai market.

The device class that's actually buying from your Thai business: a 2-3 year old Android phone (Oppo, Vivo, Xiaomi, sometimes Samsung mid-range) on 4G — sometimes 4G+ in Bangkok, sometimes 3G in rural Isaan. The CPU is 30-50% slower than the iPhone benchmark and the network is 3-5x higher latency.

This matters because your CWV scores are measured against the real device mix of your users, not against a flagship phone. A Bangkok flagship-only audit looks great; the actual Thai mobile experience can be 2x slower.

Google scores three Core Web Vitals:

• LCP (Largest Contentful Paint) — when the biggest content element finishes loading. Target: under 2.5 seconds
• INP (Interaction to Next Paint) — how fast the page responds when a user taps. Target: under 200ms. Replaced FID in 2024.
• CLS (Cumulative Layout Shift) — how much content jumps around as the page loads. Target: under 0.1

For Thai mobile users specifically, LCP is the dominant problem. Mid-range Android + 4G makes large hero images and slow server response into ranking-killers.

### 1. Move off shared hosting

Shared hosting in Thailand (with 50+ neighbours on the same server) is the #1 cause of bad TTFB (Time To First Byte). When TTFB is 800ms+, LCP can't be fixed by frontend optimisation — the server response is already too slow.

The fix: managed WordPress hosting (Cloudways, Kinsta, WPEngine) or a local Thai provider with proper resource allocation. TTFB drops from 800ms+ to 100-200ms. LCP follows.

### 2. CDN for image + asset delivery

Without a CDN, every image loads from the origin server. A Bangkok user hitting a server in the US sees 200-300ms latency per asset. With Cloudflare or Bunny.net, the same asset loads from a Singapore or Bangkok edge in 20-40ms.

For Thai mobile users on 4G, this single change typically shaves 1-2 seconds off LCP.

### 3. WebP / AVIF images, lazy-loaded properly

The biggest Core Web Vitals win on most Thai sites we audit: image format and loading. Default WordPress uploads as JPEG or PNG; the conversion to WebP cuts file size by 25-40%.

AVIF cuts further (50-65%) but support on older Android phones is iffy. We recommend WebP as the practical sweet spot.

Lazy-loading also matters: every image below the fold should have `loading="lazy"`. Most Thai WordPress sites we audit either lazy-load nothing (everything blocks LCP) or lazy-load everything including the LCP element (which makes LCP worse).

### 4. Remove page-builder bloat

Elementor, Divi, and WPBakery generate 5,000+ line HTML for what should be a 200-line page. Every CSS rule, every JS event handler, every wrapper div compounds parse time on mid-range Android.

We routinely see sites where switching from Elementor to a properly-built custom theme drops LCP by 50% even without any other changes.

### 5. Defer or eliminate third-party scripts

Third-party scripts (Facebook Pixel, Google Analytics, chat widgets, FB chat, Hotjar, etc.) load synchronously by default. On 4G Android each one adds 100-300ms to render.

The fix: add `defer` to every third-party script, or load via Google Tag Manager which handles deferring properly. We've seen INP drop from 400ms to under 150ms just from this single optimisation.

Don't trust PageSpeed Insights' "Lab Data" — it's a simulation on a benchmark device. Trust the Field Data section, which is real user data from real Thai phones.

Field Data shows the actual performance distribution of your visitors. If 60% of your users are getting LCP under 2.5s, you pass for that metric. If only 40% are passing, you fail.

Google uses Field Data for ranking decisions, not Lab Data.

Achievable on properly-built WordPress:

• LCP: 1.5-2.5s (target: 2.5s passing threshold)
• INP: 120-180ms (target: 200ms passing threshold)
• CLS: 0.02-0.05 (target: 0.1 passing threshold)

Unrealistic on a 4G mid-range Android (regardless of optimisation):

• LCP under 1.5s on rural 3G — the radio latency alone eats your budget
• INP under 100ms on a 4-year-old Android — the CPU just can't paint that fast

Know what's achievable for your actual user base before chasing scores.

If you want to see where your site stands right now:

1. Open Google Search Console → Core Web Vitals report 2. Look at the Mobile tab — that's your actual user data 3. Count how many URLs are flagged as "Poor" or "Needs improvement" 4. Note the specific metric failing most (usually LCP for Thai sites)

If you have more than 10% of URLs flagged Poor on mobile, that's an active ranking drag. Fixing it typically lifts organic traffic 10-20% within 60 days of being below the threshold.