Slow Website? Fix TTFB and Hosting Before More Plugins
Why Time to First Byte kills PageSpeed on Indonesian sites, how to measure TTFB, and what to change in hosting, PHP, caching, and CDN before frontend micro-optimizations.
On this page
If mobile PageSpeed keeps failing after image compression and “optimization” plugins, look at TTFB—Time to First Byte. When the HTML document itself arrives late, LCP cannot recover.
This is especially common on cheap shared hosting serving visitors across Indonesia.
What TTFB means in practice
TTFB is the wait until the browser receives the first byte of the response. It includes:
- DNS lookup (sometimes);
- TCP/TLS handshake;
- server queue + PHP bootstrap;
- database work to render HTML;
- network distance to the origin.
A beautiful theme cannot hide a 1.2s HTML wait.
How I measure it
- Chrome DevTools → Network → document request → Timing.
curl -o /dev/null -s -w '%{time_starttransfer}\n' https://example.com/- PageSpeed / CrUX field data for real-user latency.
- Compare origin vs CDN edge (Cloudflare orange cloud on/off for a test).
Targets I aim for on business brochure sites:
- good: often under ~0.4–0.6s from a nearby region;
- investigate: consistently above ~0.8–1.0s on HTML.
Exact numbers vary by network—trends matter more than one lab run.
Common causes on client projects
1. Distant or overloaded hosting
US/EU shared hosts without a CDN produce painful latency for ID users. Even Singapore can feel slow if the plan is CPU-throttled.
2. No page cache
WordPress/Laravel rendering HTML on every anonymous visit is expensive. Full-page cache (server, LiteSpeed, Redis + page cache, or static export) usually beats another minify plugin.
3. Heavy plugins and admin-ajax chatter
Chat widgets, page builders, and security scanners can force dynamic paths. Cache HTML for public pages; exclude carts and logged-in users carefully.
4. Slow database queries
Unindexed meta queries, bloated revision tables, and object-cache misses inflate TTFB. Fix the query—or cache the page.
5. TLS and HTTP version
HTTP/2/3 at the edge helps multiplexing; it does not fix a cold PHP origin at 900ms.
Fix order that actually works
- Measure TTFB on the homepage HTML.
- Enable page cache / static hosting where possible.
- Put Cloudflare (or another CDN) in front for assets and, when safe, HTML.
- Upgrade PHP (8.2+) and hosting tier if CPU steal is visible.
- Then resume frontend work (images, fonts, JS).
WordPress checklist
- page cache plugin or host-level cache—not three overlapping caches;
- object cache (Redis) on dynamic sites;
- disable unused plugins;
- keep admin and preview URLs uncached;
- verify cache HIT headers after purge tests.
Keyword intent
People searching penyebab website lambat, TTFB tinggi, hosting website lambat Indonesia, and cara percepat TTFB wordpress need hosting/cache diagnosis first. Frontend polish is step two.