Your website is slow on Nepali mobile data because most pages are built and tested on fast office fibre, then opened by customers on a crowded 4G signal with a phone that has far less power. Good website speed on mobile comes from lighter images, fewer scripts, decent hosting and testing on a real phone, not from one magic plugin.
Below I explain why speed costs you enquiries, how to test it the way your customers see it, and the fix list I work through on a slow site. If you are planning a new site, start with my guide to website design in Nepal for the bigger picture.
Website speed means how quickly your page becomes usable on a real phone.
Website speed is the time between a customer tapping your link and being able to read, scroll and tap on your page without waiting. A page can show its logo in one second and still take six seconds before the main photo appears or the menu button responds.
Why is my website slow on mobile data but fine on office Wi Fi?
Your site feels fine in the office because a fibre connection hides heavy pages, while most of your visitors use mobile data that is slower and far less steady. In Nepal, the gap between those two experiences is wide.
Figures from the Nepal Telecommunications Authority for mid 2026, reported by Himal Press, show 27.62 million mobile broadband subscriptions, which is 88.73% of all broadband subscriptions in the country. Those are subscriptions, not unique people, but the direction is clear: your site is mostly opened over mobile networks.
Those networks are also unpredictable. Ookla has left Nepal out of its global mobile speed index since June 2024, according to MEA Tech Watch in 2025, citing “inconsistent and highly variable mobile internet speeds”. In plain words, a customer in Narayangadh at 8 pm and a customer in Thamel at 11 am can get very different speeds on the same network.
Add the phone itself. In my experience many customers browse on budget Android phones, and those phones take longer to process heavy scripts. So the same page that opens instantly on your laptop can stall on the phone your customer actually holds.
Slow website speed costs you visitors, enquiries and trust.
A slow page loses people before they read a single word, so every rupee you spent on design, ads and content works harder when the page is fast. Most visitors will not wait long.
Google research published in 2016, shared on the AMP Project blog, found that 53% of mobile site visits are abandoned when pages take longer than three seconds to load. The data is old and from global networks, but my experience with Nepali visitors says patience has not grown since then.
A customer taps your link in a Facebook ad, a Google result or a Viber message. If the page sits blank, they go back and tap the next result. You paid for that click, and you lost it before the page appeared. A page that jumps around or ignores the first tap also feels careless, and people judge the business the same way.
Core Web Vitals are Google’s three plain measures of how a page feels.
Core Web Vitals are three measurements Google uses to judge loading, response and visual stability on real visits. They turn “this page feels slow” into numbers you can test and fix.
Here are the thresholds that count as good, as set out on Google’s web.dev guide to Web Vitals in 2026.
| Measure | What it means in plain words | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the biggest thing on screen, usually the main photo or headline, appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page reacts when someone taps a button or menu | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps while it loads | 0.1 or less |
Google measures these at the 75th percentile of page loads, split by mobile and desktop. So your page passes only if most real visits are good, not just your best one.
Do these scores change your ranking? Google’s page experience documentation, updated in September 2026, says Core Web Vitals are used by its ranking systems, but also that good scores do not guarantee top positions. My view is simple. Speed will not rescue weak content, but slow speed can waste good content.
How do you test your website speed the way your customers see it?
You test website speed with a mix of Google’s free tools and a real phone on mobile data, because lab scores alone can mislead you. I use these steps on every site I review.
- Run PageSpeed Insights on your key pages. Test the homepage, a service or product page and your contact page, not only the homepage. Look at the mobile tab first.
- Read the field data before the score. The top section shows real visitor data from Chrome users when your site has enough traffic. The coloured score below is a lab test on a simulated phone. Field data reflects real visitors.
- Open the Core Web Vitals report in Google Search Console. It groups slow URLs together, so you can see whether one template, such as every product page, is the problem.
- Test on a budget phone, on mobile data, with Wi Fi switched off. Clear the cache first, then count the seconds until you can read the heading and tap the call button.
Write down the results before you change anything, so you can tell whether a fix worked.
These are the usual reasons a Nepali business website loads slowly.
Most slow sites I see in Nepal suffer from the same few problems: oversized images, too many scripts, slow or distant hosting, and features nobody needed.
Page weight is the first suspect. The HTTP Archive Web Almanac 2025 found that the median mobile home page is 2.6 MB, with images making up the largest share, around 911 KB. Many Nepali business homepages I audit are far heavier than that, because photos go straight from a DSLR or phone onto the site without resizing.
- Huge photos. A 4,000 pixel wide photo displayed at 400 pixels on a phone still downloads in full.
- Sliders and autoplay videos. A homepage slider with five large images often loads all five before the visitor sees the first.
- Too many plugins. Each plugin can add its own scripts and styles to every page, even pages that do not use it.
- Third party scripts. Chat widgets, tracking pixels, embedded Facebook feeds and Google Maps all load code from other servers.
- Heavy fonts. Loading four weights of two fonts, plus a full Devanagari font, adds weight before any text can show.
- Slow server response. Cheap overloaded hosting, or a server far away with no caching, makes every page wait before it even starts.
This is the fix list I work through on a slow website.
I fix speed in order of impact: images first, then scripts, then hosting and caching, then the finer details. This order gets the biggest gains for the least risk to a working site.
| Problem | Fix | Typical effort |
|---|---|---|
| Oversized images | Resize to display size, compress, serve WebP or AVIF, lazy load images below the first screen | Low |
| Slow main image | Do not lazy load the hero image; tell the browser to load it first; keep it small | Low |
| Layout jumping | Set width and height on images, reserve space for banners and embeds | Low |
| Too many plugins | Remove unused plugins, replace heavy ones, stop scripts loading on pages that do not need them | Medium |
| Third party scripts | Keep only the pixels you use, load chat widgets after the page, swap embedded maps for a static image linking to Google Maps | Medium |
| Slow server | Turn on page caching, use a CDN, upgrade hosting or move closer to your visitors | Medium |
| Heavy theme or page builder | Simplify templates, or rebuild key pages with a lighter theme | High |
One warning on the hero image. Google’s web.dev guide to optimising LCP says never to lazy load your LCP image, because the browser then delays the very thing your visitor is waiting for. I see this often when a plugin lazy loads every image by default.
If your server is slow to respond, nothing else fully makes up for it. I cover local versus international hosting in my article on domains and hosting in Nepal, and how the platform you choose affects speed in WordPress, Shopify or custom code.
What does fixing website speed cost, and what drives the effort?
The cost of fixing website speed depends on how the site was built, not on how slow it is. A site that only needs image compression and caching is a short job, while a site built on a heavy theme with dozens of plugins may need key templates rebuilt.
These decide the effort:
- The platform and theme. A clean WordPress theme is easier to speed up than a theme bundled with every feature imaginable.
- Hosting. Sometimes the honest fix is a better hosting plan, which is a yearly cost rather than a one off job.
Speed is not a one time fix either, because new photos, plugins and tracking codes add weight back. Check your main pages monthly as part of regular website maintenance, so the gains you paid for do not disappear by next Dashain.
These are the speed mistakes I see business owners make most often.
The most common mistake is chasing a perfect score instead of a fast experience for real customers on mobile.
- Testing only on office Wi Fi. Your customers are not sitting on your fibre line.
- Paying for bigger hosting before fixing images. More server power does not shrink a 5 MB photo.
- Ignoring the pages that make money. Owners test the homepage, while customers land on product and service pages from Google and ads.
My approach is to design for a budget phone on a weak signal first.
I design every site for the slowest realistic visitor first, then let faster devices enjoy the extra polish. Speed is much cheaper to build in than to bolt on later.
On an ecommerce build like the Goreto Gears store, with many product photos and activity filters, image handling and filter scripts are where I focus my speed effort, because those are the parts that grow every time a new product is added. On content heavy sites such as a hospital with a large doctor directory, I keep listing pages light and load detail only when someone opens a profile.
What I tell clients is this: before you ask for a video background, ask whether your customer on a bus in Chitwan would wait for it.
These are the questions business owners ask me most about website speed.
What is a good PageSpeed Insights score for a business website?
Aim to pass Core Web Vitals in the field data first, then treat a mobile lab score in the green as a bonus. A score in the high 80s with passing field data is better than a perfect lab score with real visitors failing. Always judge the mobile tab, not desktop.
How big should a web page be for visitors on mobile data?
Lighter is always better, and I aim well below the 2.6 MB median mobile home page that the Web Almanac reported for 2025. In my experience most service pages can stay under about 1 MB if images are sized properly. Product pages with many photos should load extra images only when needed.
Will a CDN like Cloudflare make my website faster in Nepal?
Usually yes, especially if your server is abroad. A content delivery network keeps copies of your files on servers closer to your visitors, and Cloudflare announced a Kathmandu data centre back in February 2018. It will not fix oversized images or a slow theme, so do those fixes as well.
Is hosting in Nepal always faster than hosting abroad?
Not always. A well run server abroad with caching and a CDN can beat a slow, overloaded local server. Test the server response time from Nepal before you choose, and pick hosting on reliability and support as well as location.
How often should I check my website speed?
Check your main pages every month, and always after adding a plugin, a tracking code or a batch of new photos. The Core Web Vitals report in Search Console will also flag pages that slip.
Here is what I would do next if I were you.
Run PageSpeed Insights on your three most important pages today, then open them on your own phone with Wi Fi switched off. If the main content takes more than a few seconds to appear, start with the images and work down the fix list above.
If you would rather have someone review it for you, I look at speed as part of every website design and development project, whether it is a new build or a rescue of an existing site. Send me your website address through my contact page and I will tell you what is slowing it down and what is worth fixing first.
These are the sources I used for this article.
- Himal Press, Total telephone subscriptions in Nepal hit 30.31 million (NTA data, 2026)
- MEA Tech Watch, Nepal delisted from Ookla’s global mobile broadband speed index (2025)
- AMP Project blog, The need for mobile speed (Google research, 2016)
- web.dev, Web Vitals
- Google Search Central, Understanding page experience in Google Search results
- HTTP Archive Web Almanac 2025, Page weight
- web.dev, Optimize Largest Contentful Paint
- Cloudflare blog, Kathmandu data centre (2018)