Blog

Core Web Vitals Singapore: The Mobile Performance Guide for 2026

15 April 2026 · Eugene

Core Web Vitals is the ranking signal most Singapore sites fail and most SEO agencies address superficially. “Improve site speed” is easy to recommend; specifying which image to compress, which render-blocking script to defer, or which web font to subset is harder — and that’s where performance gains actually live.

This guide covers what Core Web Vitals actually measure, the specific thresholds that matter for Singapore traffic, the highest-impact optimisations for SG sites, and how to measure real-user performance rather than synthetic scores.

What Core Web Vitals Measure

Core Web Vitals are three user-experience metrics Google uses as ranking signals:

LCP — Largest Contentful Paint

The time from navigation start until the largest visible element renders. Measures perceived load speed.

Thresholds (mobile):
– Good: ≤ 2.5 seconds
– Needs improvement: 2.5-4.0 seconds
– Poor: > 4.0 seconds

The “largest element” is usually a hero image, a main headline, or a primary card/banner. Most sites have LCP issues because their hero images aren’t optimised or their render-blocking resources delay rendering.

INP — Interaction to Next Paint (replaced FID in 2024)

The time from a user interaction (click, tap) until the next visible update. Measures responsiveness during use.

Thresholds:
– Good: ≤ 200 milliseconds
– Needs improvement: 200-500 milliseconds
– Poor: > 500 milliseconds

Most INP issues come from JavaScript execution blocking the main thread during user interactions.

CLS — Cumulative Layout Shift

The sum of visual layout shifts during a page’s lifecycle. Measures visual stability.

Thresholds:
– Good: ≤ 0.1
– Needs improvement: 0.1-0.25
– Poor: > 0.25

CLS issues typically come from images without dimensions, web fonts swapping visibly, or dynamically injected content (ads, banners) appearing above existing content.

Why Core Web Vitals Matter Specifically in Singapore

Three reasons SG Core Web Vitals deserve particular attention:

Mobile commerce dominance. Singapore has among the highest mobile internet usage globally. Most commercial searches — property, F&B, healthcare, retail — happen mobile-first. Slow mobile performance directly damages both rankings and conversion.

Device heterogeneity. Google measures Core Web Vitals on real user devices via Chrome User Experience Report (CrUX). Singapore’s user base spans high-end iPhones and mid-tier Android devices. Optimising for only flagship devices misses the mid-tier performance where most real users live.

Network conditions. Singapore has excellent network infrastructure overall, but 4G and occasional 5G represents real usage. Site performance needs to handle variable network conditions, not just fiber office connections.

How Core Web Vitals Are Measured

Two measurement methods, both matter:

Field Data (CrUX)

Real-user measurements from Chrome users who opted into anonymous data sharing. This is what Google actually uses for rankings.

Sources:
– Google Search Console Core Web Vitals report (bulk view)
– PageSpeed Insights (per-URL view with field + lab data)
– CrUX API for programmatic access

Field data reflects reality but requires enough traffic to generate meaningful samples. Low-traffic pages may not have CrUX data.

Lab Data

Synthetic measurements from tools that simulate page loads. Useful for diagnosing issues and iterating quickly.

Sources:
– PageSpeed Insights lab data
– WebPageTest
– Lighthouse (Chrome DevTools)
– Sitebulb, Screaming Frog performance analysis

Lab data is reproducible but doesn’t reflect real user experience. Optimising for Lighthouse scores without field data verification is common mistake.

Practical approach: Use field data for prioritisation (which pages have real-user problems), lab data for diagnostics (what’s causing the problems), and field data again for verification (did real-user performance actually improve?).

Highest-Impact Optimisations for Singapore Sites

For LCP (Largest Contentful Paint)

Optimise hero images.
Most LCP issues trace to the hero image on priority pages. Actions:
– Serve modern formats (WebP, AVIF) with proper fallback
– Generate responsive images with srcset and sizes attributes
– Preload critical hero images with <link rel="preload" as="image">
– Compress aggressively (Singapore users tolerate quality trade-offs for speed)

Reduce render-blocking resources.
– Inline critical CSS; defer non-critical CSS
– Defer non-critical JavaScript with defer or async
– Eliminate or defer third-party scripts where possible
– Audit chat widgets, analytics, A/B testing tools — these are common LCP killers

Optimise web fonts.
– Use font-display: swap to prevent invisible text
– Subset fonts to required glyphs only
– Self-host fonts where possible (Google Fonts can be slow)
– Preload critical font files

Server and CDN configuration.
– Use a CDN with Singapore edge presence (Cloudflare, CloudFront, Akamai)
– Enable HTTP/2 or HTTP/3
– Configure appropriate caching headers
– Minimise TTFB (Time to First Byte)

For INP (Interaction to Next Paint)

Reduce JavaScript bundle size.
– Code-split your JavaScript (especially for SPAs and React/Vue/Next.js sites)
– Remove unused dependencies
– Use tree-shaking and dead code elimination
– Audit bundle contents with tools like Webpack Bundle Analyzer

Audit third-party scripts.
Third-party scripts (analytics, ads, chat, A/B testing) are usually the biggest INP culprits. Actions:
– Delay loading non-critical third-party scripts
– Use async where possible
– Consider tag management that can conditionally load scripts
– Remove third-party scripts that don’t provide clear commercial value

Optimise hydration for SPAs.
For React, Vue, Next.js sites:
– Consider partial hydration or island architectures
– Optimise hydration timing for interactive elements
– Use server-side rendering or static site generation where appropriate

For CLS (Cumulative Layout Shift)

Specify image dimensions.
Every <img> tag should have explicit width and height attributes (or aspect-ratio CSS). This reserves space before the image loads, preventing shift.

Reserve space for ads and embeds.
If you display ads, embedded content, or dynamically injected content, reserve appropriate space with min-height or aspect-ratio containers.

Manage web font loading.
– Use font-display: optional or font-display: swap with size-adjust to minimise layout shift during font swapping
– Use font metrics overrides to match fallback font sizing

Avoid non-user-triggered layout changes.
Don’t inject content above existing content. Don’t animate layout-affecting properties (use transform instead of position/size changes).

Common Singapore Site Issues

Patterns we see repeatedly in SG site audits:

Oversized hero images. Uncompressed 3-4MB hero images on SG sites is unfortunately common. Proper image optimisation alone often resolves LCP issues.

Third-party script bloat. Singapore sites often accumulate tracking scripts (GA, Meta Pixel, LinkedIn Insight, Hotjar, multiple chat widgets, A/B testing platforms). INP suffers dramatically.

Unoptimised WordPress/Shopify themes. Many off-the-shelf themes include substantial bloat. Performance-focused theme selection or custom development matters.

Missing image dimensions. Legacy WordPress sites often have images inserted without dimensions. CLS suffers.

Shopify app sprawl. Shopify stores accumulate apps that each load their own scripts. Each app adds performance overhead.

Unoptimised fonts. Multiple font weights loaded from Google Fonts without subsetting is common. Fonts load slowly; text renders invisibly; LCP suffers.

How to Audit Your Core Web Vitals

Practical audit sequence:

Step 1: Search Console → Core Web Vitals report. Identify poor/needs-improvement URLs across mobile and desktop.

Step 2: For highest-traffic poor-performing URLs, run PageSpeed Insights. Review field data + lab diagnostics.

Step 3: Prioritise by (traffic × impact): fix issues affecting high-traffic templates first.

Step 4: For each issue, identify root cause using Lighthouse diagnostics + Chrome DevTools Performance tab.

Step 5: Implement fixes, verify in lab (should improve synthetic scores), then wait 28 days for CrUX data to update and confirm real-user improvement.

Step 6: Repeat monthly. Core Web Vitals drift over time as new content is added and third-party scripts accumulate.

Core Web Vitals and Rankings — What to Realistically Expect

Honest framing: Core Web Vitals are a ranking signal, but not a dominant one. Expect:

Sites that fail CWV: constrained ranking ceiling, particularly for competitive queries
Sites that pass CWV: no ranking boost per se, but no constraint
Moving from poor to good CWV: incremental ranking improvement over 2-3 months, especially on mobile

Core Web Vitals won’t make bad content rank. Good content + CWV compliance + other SEO fundamentals together produce strong rankings.

FAQ — Core Web Vitals Singapore

What are good Core Web Vitals scores?
LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1 on mobile. All three need to pass the 75th percentile threshold for the URL to be considered “good.”

How does Google measure Core Web Vitals?
Via Chrome User Experience Report (CrUX) — real-user field data from Chrome users who share usage data. This reflects actual visitor experience, not synthetic lab scores.

How long do Core Web Vitals take to update?
CrUX data updates on a 28-day rolling window. Changes take approximately a month to reflect in field data and Search Console.

Do Core Web Vitals affect desktop rankings too?
Yes, but mobile is weighted more heavily. Singapore’s mobile-dominant user base makes mobile CWV particularly critical.

What tools should I use to measure Core Web Vitals?
PageSpeed Insights (field + lab data per URL), Search Console (aggregate field data), Lighthouse (lab diagnostics), WebPageTest (detailed lab measurement).

Can I pass Core Web Vitals with a WordPress site?
Yes, with proper configuration. Choose performance-focused themes, limit plugins, use image optimisation plugins, configure caching properly, and audit third-party scripts.

Is Core Web Vitals the most important ranking factor?
No. Content quality, topical authority, search intent matching, and technical foundations beyond CWV all matter more. CWV is a ranking signal, not the primary one.

Why does my site have different CWV scores on different pages?
Template-specific issues — hero images, third-party scripts, layout patterns — vary per template. Fix template-level issues to resolve across all pages using that template.

Discuss Your Technical SEO

If your Singapore site is struggling with Core Web Vitals and you want specific technical recommendations rather than generic advice, reach out.

Book a free 30-minute consultation or email [email protected].