Most slow WordPress sites in Nepal are slow for the same handful of reasons, and nearly all of them are fixable in an afternoon. Here is the order to work through, from largest effect to smallest.
First, measure properly
Test from a location that matches your audience. A site scoring well when tested from Frankfurt tells you nothing about the experience in Kathmandu. Use PageSpeed Insights and, if your tool allows, select a South Asian test location.
Watch three numbers in particular:
- TTFB (Time To First Byte) — how long the server takes to start responding. Above about 600 ms means a server or hosting problem, not a front-end one.
- LCP (Largest Contentful Paint) — when the main content appears. Aim below 2.5 seconds.
- CLS (Cumulative Layout Shift) — how much the page jumps while loading. Aim below 0.1.
If TTFB is bad, no amount of image optimisation will save you. Fix the server first.
1. Page caching (largest single win)
Without caching, every visitor triggers PHP execution and a series of database queries to rebuild a page that has not changed. Page caching stores the finished HTML and serves that instead.
Install one caching plugin — only one. Running two is a classic cause of bizarre, hard-to-diagnose behaviour. Reasonable choices are LiteSpeed Cache (if your host runs LiteSpeed), WP Super Cache, or W3 Total Cache.
Enable page caching, browser caching and GZIP or Brotli compression. That alone commonly cuts load time by half or more.
2. Images
Images are usually the bulk of a page's weight, and Nepali sites frequently serve 3 MB photographs straight from a phone camera.
- Resize before uploading. A full-width banner rarely needs to exceed 1920 px wide; a blog thumbnail needs about 400 px.
- Use WebP. Typically 25–35% smaller than JPEG at equivalent quality, and supported by every current browser.
- Enable lazy loading. WordPress does this natively now — confirm a plugin has not disabled it.
- Always set width and height attributes, which prevents layout shift and improves CLS.
3. Cut down the plugins
Every active plugin adds PHP execution, and often its own CSS and JavaScript to every page. Sites carrying 40+ plugins are common and almost always slow.
Deactivate anything unused, then check what remains for known-heavy offenders: page builders, "all-in-one" suites, sliders, and any plugin loading assets sitewide for a feature used on one page. Deactivate one at a time and re-measure to find the real cost of each.
4. Clean the database
Over years, wp_options, post revisions, spam comments and orphaned metadata accumulate. Two specific things to check:
- Autoloaded options. Every page load reads all options marked autoload. When abandoned plugins leave megabytes there, every request pays. Aim to keep it under about 1 MB.
- Post revisions. WordPress keeps unlimited revisions by default. Limit them in
wp-config.phpwithdefine('WP_POST_REVISIONS', 5);
5. Hosting choices that matter
Server location
For a mainly Nepali audience, a server in Nepal removes 200–300 ms of latency per round trip compared with a European or American host — and a page load involves many round trips. This is discussed in more detail in our guide to web hosting in Nepal.
PHP version
Run PHP 8.2 or newer. PHP 8 is substantially faster than 7.4, and older versions no longer receive security fixes. Most control panels let you switch versions in a couple of clicks — test on staging first.
Object caching
For WooCommerce or membership sites, where much of the traffic cannot be page-cached because it is personalised, Redis object caching makes a large difference. It requires a VPS or a host that provides Redis.
NVMe storage and HTTP/2
NVMe drives markedly improve database-heavy workloads. HTTP/2 or HTTP/3 lets the browser fetch many files over one connection instead of queueing them — significant on high-latency connections, which describes much of mobile Nepal.
6. Add a CDN if you serve visitors abroad
If your audience is entirely within Nepal and your server is in Nepal, a CDN adds little. If you also serve the diaspora or international customers, a CDN caches your static files close to them. Cloudflare's free tier is sufficient for most sites.
A realistic checklist
- Measure TTFB, LCP and CLS from a South Asian location
- Enable a single page-caching plugin with compression
- Resize and convert images to WebP; confirm lazy loading is active
- Remove unused plugins and re-measure
- Upgrade to PHP 8.2+
- Clean the database and limit revisions
- Add Redis object caching if the site is personalised
- Add a CDN if you have international visitors
Frequently asked questions
Why is my site fast for me but slow for visitors?
Your browser has cached the assets, and you may be close to the server. Always test in a private window, and preferably from a different network.
Will a caching plugin break my site?
It can, particularly with WooCommerce carts, login states and forms. Exclude cart, checkout and account pages from the cache — every serious caching plugin supports these exclusions and most configure them automatically.
Is shared hosting able to run a fast WordPress site?
Yes, comfortably, for typical business sites — provided the host uses NVMe storage, current PHP, and does not oversell. Caching matters more than the hosting tier for most sites.
How much speed does moving to a Nepali server actually gain?
For a database-driven site previously hosted in the US or Europe, TTFB improvements from around 800 ms to under 200 ms are common. The gain is smaller if your site was already well cached behind a CDN.
Next steps: see hosting plans in Nepal or read about when a VPS makes sense.