Website Speed + SEO for Thai Sites: Core Web Vitals Checklist
Where we're coming from
Start from what real visitors’ phones measure, not a desktop score from the office: find the element that fails, fix images and Thai fonts first, then cut third-party scripts. Speed supports rankings; it does not outrank relevance.
"Thai website speed SEO" comes up often in buyer conversations. This page captures the framing we use from actual client work, not vendor-marketing slide decks.
Quick answer
Measure with field data first: the Core Web Vitals report in Google Search Console and PageSpeed Insights show how real visitors’ phones load your pages. A page passes when, at the 75th percentile of visits, Largest Contentful Paint (LCP) is 2.5 seconds or less, Interaction to Next Paint (INP) is 200 milliseconds or less and Cumulative Layout Shift (CLS) is 0.1 or less. Then fix in this order: the largest image or video on the first screen (compress it, size it, load it first), Thai web fonts (load only the scripts and weights you use, with a size-matched fallback), then chat widgets and tracking tags. Speed supports rankings, but Google still aims to show the most relevant page first, even when its page experience is poor.
Updated: 2026-10-01
Key takeaways
- Judge speed by field data from real visitors (Search Console, PageSpeed Insights), not one lab score from an office laptop.
- Pass marks at the 75th percentile: LCP 2.5 s or less, INP 200 ms or less, CLS 0.1 or less.
- Find the page’s LCP element first (often the hero image, a video poster or the headline); make it small and load it before anything else.
- A Thai page needs Thai and Latin glyphs: load each subset only where it is used, preload only the weight on the first screen, and use a size-matched fallback so text does not jump.
- Chat widgets, pixels and tag managers compete with the page for the main thread; load them after the page is usable.
- Test on a mid-range Android phone on mobile data, not on office Wi-Fi.
Decision guide
| Option | Best for | Watch out for |
|---|---|---|
| Images and hero video | LCP fails and the LCP element is an image or video: serve AVIF or WebP sized to the screen (srcset) and give that image fetchpriority="high" | Never lazy-load the first-screen image, and set width and height on every image to reserve its space, or CLS gets worse |
| Thai web fonts | Text appears late, or the page jumps when the font finishes loading | font-display: swap without a size-matched fallback (size-adjust, ascent-override) only trades invisible text for jumping text; leave line-height room for Thai vowels and tone marks above and below the line |
| Third-party scripts (chat, pixels, tag manager) | INP fails: the page feels stuck after a tap | Removing a tag removes the data it collects; check with marketing which tags still feed a report |
| Hosting, CDN and caching | The server responds slowly (high TTFB) on every page, even simple ones: use a CDN with a point of presence in or near Thailand | A CDN only helps what can be cached; pages generated on every request still need a fast origin server |
| Rebuild | The theme or page builder loads so much code that fixes do not move the field data | The new site must keep the old URLs (or 301-redirect them), titles and structured data, or rankings drop during the move |
Budget guide
| Item | What it covers | Budget |
|---|---|---|
| Landing page (rebuilt) | One page, server-rendered, SEO built in, delivered in 5–10 days | From THB 9,900 |
| Company website (rebuilt) | 3–5 man-days, delivered in 2–4 weeks | THB 23,970–39,950 |
| Speeding up the current site | Audit the field data, LCP element, fonts and scripts first, then size the man-days | From THB 7,990 per man-day |
Frequently asked questions
Do Core Web Vitals affect Google rankings?
Yes. Core Web Vitals are part of the page experience signals Google’s ranking systems use, but Google says it still aims to show the most relevant content even when page experience is poor. Speed helps when several pages are similarly relevant; it will not rescue a page that does not answer the search.
What are the passing Core Web Vitals thresholds?
At the 75th percentile of visits: LCP 2.5 seconds or less, INP 200 milliseconds or less and CLS 0.1 or less, assessed separately for mobile and desktop. INP replaced First Input Delay (FID) in March 2024.
Why does my PageSpeed score differ from Search Console?
The PageSpeed Insights score is a lab test (Lighthouse): one load on a simulated mid-range phone over a slow 4G connection. Search Console and the real-user section of PageSpeed Insights come from real Chrome users over the previous 28 days, and Google Search assesses Core Web Vitals from that field data. A low-traffic site may have no field data yet; use lab tests until it does.
How do we stop Thai fonts slowing the page?
Use a font split by script (Google Fonts serves Thai and Latin as separate unicode-range files) or subset a self-hosted one; load only the weights you use; preload the one on the first screen; and pair font-display: swap with a fallback sized via size-adjust so text does not jump. Leave line-height room too: Thai vowels and tone marks stack above and below the line and get clipped in tight boxes.
Is a hero video bad for speed?
Not by itself, but on mobile it is often the largest thing on the first screen, and Chrome counts a video’s poster image and first frame as LCP candidates. Use a compressed poster sized for the screen, do not autoplay a large file on mobile data, or show a still image on small screens.
Should we fix the current site or rebuild it?
Fix first if the problem is a few heavy images, fonts or scripts. Rebuild when the theme or page builder loads so much code that fixes do not move the field data. If you rebuild, keep the old URLs or 301-redirect them, along with titles and structured data. At iReadCustomer a landing page is delivered in 5–10 days and a company website in 2–4 weeks, depending on scope.
Sources
Our closest related service
Website & Landing Page
See details →Other guides
Contact Us