Performance Budgets for Small Business Websites

Websites tend to get heavier over time. One more tracking script, a bigger hero image, another plugin. Each seems harmless, but together they slow the site. A performance budget is a set of agreed limits that stops this creep.

What a performance budget is

It's a list of numbers your site should not exceed, such as how fast key pages should load or how much data they can transfer. Like a financial budget, it forces trade-offs: if you want to add something heavy, you must remove something else or justify going over.

Types of budgets

Metric budgets. Target thresholds for user-centered measures:

• Largest Contentful Paint at or below 2.5 seconds
• Interaction to Next Paint at or below 200 milliseconds
• Cumulative Layout Shift at or below 0.1

These match Google's "good" Core Web Vitals thresholds. See Core Web Vitals explained.

Quantity budgets. Limits on raw resources, for example:

• Maximum total page weight for key pages
• Maximum image size for hero images
• Maximum JavaScript size
• Maximum number of third-party scripts
• Maximum number of web font files

Timing budgets. For example, server response time under a chosen threshold. See what is TTFB.

How to set your own

1. Measure where you are. Test your main pages. See how to test website speed.
2. Look at your audience. If many visitors are on mobile or slow networks, aim stricter. See designing for slow connections.
3. Compare with competitors. If you can be faster than rivals, that's an advantage.
4. Pick a few numbers that matter, rather than dozens.
5. Make them achievable but ambitious. Start with limits slightly better than current performance, then tighten.
6. Write them down where everyone who updates the site can see them.

There's no universal "right" page weight. The right limits depend on your site, audience, and goals.

Put the budget into practice

Before adding anything, ask what it costs. A new plugin, chat tool, or video should be justified against the budget. See third-party scripts and website speed.

Set image guidelines for anyone uploading content: maximum dimensions and file sizes, plus preferred formats. See how to compress images.

Test regularly. Run speed checks monthly and after every significant change. Free tools and monitoring services can alert you when numbers slip.

Automate where possible. Developers can add checks to the build process that fail if limits are exceeded.

Review quarterly. Remove what's no longer needed. See website maintenance checklist.

Handle exceptions deliberately

Sometimes you'll want to exceed the budget, such as for a showcase page. Decide consciously and make up for it elsewhere.

Share it with your team and suppliers

Designers, developers, and marketers should know the limits before they work. Include them in your design brief and contracts. See website contract checklist.

The bottom line

Pick a few measurable limits, test against them regularly, and think twice before breaking them. A budget keeps a fast site fast.