Page Speed Budget: Deciding What Your Website Design Can Afford

A page speed budget works exactly like a money budget: you decide what you can afford before you start spending, and every fancy thing you add costs something. Most websites get slow the same way most people go broke, not one big purchase, just hundreds of small ones nobody tracked. A slider here, a font there, a chat widget, an autoplay video. Each seemed cheap. Together they weigh six megabytes.

In Nepal this matters double. A big share of your visitors are on NTC or Ncell mobile data, sometimes on 4G that behaves like 3G in a crowded Ratna Park. A page that feels fine on your office WiFi can take eight seconds for them. They will not wait. Research keeps landing on the same cliff: past about three seconds, bounce rates climb steeply.

What a speed budget actually looks like

Pick hard numbers before design starts. A sensible budget for a business site in 2026:

• Total page weight: under 1.5 MB, ideally under 1 MB
• Largest Contentful Paint: under 2.5 seconds on mobile
• Requests: under 50
• JavaScript: under 300 KB
• Fonts: two families maximum, subsetted

Then every design decision gets checked against the budget, the same way you would check a quotation against your bank balance.

What things cost

Rough prices in kilobytes, so you can shop wisely. A properly compressed hero image in WebP: 80 to 150 KB. The same image exported carelessly from a phone: 3,000 KB. A Google font family with four weights: 100 to 200 KB. An embedded YouTube video: 500 KB or more of scripts before anyone presses play. A typical live-chat widget: 300 to 900 KB. A slider plugin: 200 to 400 KB, for a feature visitors mostly ignore anyway.

See the pattern? Images and third-party widgets are where budgets die. Not your HTML.

Spending the budget where it counts

A budget is not about making everything ugly and bare. It is about choosing. If a full-width video of your restaurant genuinely sells the atmosphere, spend the kilobytes there and go minimal everywhere else: system-adjacent fonts, no slider, one chat channel instead of three. Trade-offs, made on purpose. That is the entire discipline.

Honest admission: some things are worth being slightly slower for. An eSewa or Khalti payment integration adds scripts, and you obviously keep it. A booking calendar earns its weight. The autoplay drone video of your building probably does not.

How to measure against your budget

Two free tools cover almost everything. PageSpeed Insights gives you the Google-eye view: Largest Contentful Paint, layout shift, and a mobile score, measured on hardware slower than your phone, which is exactly the point. Your browser's own network tab (right-click, Inspect, Network) shows the receipt: every file the page loads, its size, and the total at the bottom. Sort by size, and the three heaviest items are usually your entire problem.

Test the mobile numbers, not desktop. Desktop scores flatter everyone. And test your real pages, the service page and the contact page, not just the homepage you polished for launch day. Visitors from ads and search land everywhere.

Keeping the budget after launch

Sites gain weight the way people do after Dashain. The marketing team adds a popup, someone uploads a 4 MB photo, a plugin update drags in a new library. Check monthly: run PageSpeed Insights, look at total weight, compare against your budget. Five minutes. If a number jumped, find what got added.

How WebsNP works with speed budgets

Every site we build starts with performance targets, not excuses afterwards. We compress and convert images, limit fonts, skip bloated page builders where possible, and host on our own NVMe servers, which are the fastest storage tier you can reasonably buy in this market. On-page SEO and SSL are included, and Google rewards the speed side of that directly in rankings. Fixed-price quote within 24 hours, delivery in 2 to 7 days for most sites. Tell us your must-have features and we will tell you honestly what they cost, in rupees and in kilobytes.