Lighter websites, smaller footprint

Why this matters to a web studio

A website is not weightless. Every page view is a chain of physical events: a request travels from a visitor’s device to a data centre, a server draws electricity to respond, the file crosses a network to reach them, their phone or laptop spends battery rendering it, and the page stays in memory while they read it. None of that is visible to the visitor, but all of it is real.

Individually, a single page view is a rounding error. The problem is volume. A site that receives thousands of visits a month, for years, with a page that weighs several megabytes before it becomes useful, multiplies that small cost by a very large number. That cost is paid on every visit, not once at launch, and it does not get smaller on its own.

We are honest about where our leverage sits. Jones Digital is a small studio. The electricity our own office and equipment use is trivial, and if we disappeared tomorrow it would not register. What we can genuinely influence is the size of the pages we hand to clients — because we choose how much code, how many images and how many third-party scripts go into them. Those choices lock a site’s energy use in place for years, and they are the reason this policy exists.

The three places the energy goes

For any website, the footprint is roughly the sum of three things:

• Data transfer — the size of the files sent over the network every time someone loads a page
• Server and hosting — the energy used by the data centre to serve and store the site
• Visitor devices — the energy a phone, laptop or tablet uses to download, parse and render the page

Of the three, the last is often the largest and is the one most easily ignored — which is why a page that ships less code also costs less to view on the device someone actually owns.

What we do when we build

This is where our decisions matter most. None of the practices below are unusual or expensive — they are simply the difference between a site built carefully and one built by default. Every one of them is something we do on every project, not an optional extra.

Keep pages lightweight

We avoid heavy page builders, plugin bloat and third-party scripts that add weight without adding value. Every dependency has to earn its place. If a piece of functionality can be built in a few lines of our own code rather than pulling in a large library, we build it. We also write our CSS so it stays small, using a utility approach that ships only the styles a page actually uses rather than a large framework file in full.

Treat images as the main event

Images are usually the largest part of a page, so they get the most attention. We compress them, size them correctly for the space they occupy, and serve them in modern formats such as WebP and AVIF with sensible fallbacks for older browsers. We supply responsive versions so a phone is never made to download a desktop-sized file, and we set explicit dimensions so the page does not jump around while it loads.

Load only what a page needs

Images below the fold are lazy loaded, so a visitor who never scrolls never pays for them. Fonts are limited to the weights actually used. Video is only used where it earns its place — no silent autoplaying background loops that run a decode on every visit. Animation is done with CSS rather than heavy JavaScript libraries, and it is kept subtle and short. If a page does not need a component, that component is not loaded.

Deliver it efficiently

Where a project suits it, we build static or pre-rendered pages rather than generating every page on demand — the same content delivered for less energy. We use caching so repeat visits are served without redoing work, and we recommend hosting with a content delivery network, which serves visitors from a location near them rather than across the world.

Build it to last

The most sustainable website is one that does not need rebuilding every two years. Every rebuild consumes design time, development time and, often, new hardware. We build sites that can be updated, extended and added to rather than replaced, and we set clients up to manage their own content so routine changes do not require us at all.

Be careful with tracking

Analytics and marketing scripts are frequently the heaviest thing on an otherwise lean page, and they run on every visit. We add them only where there is a clear reason, keep the number of them low, and are happy to build a site with none at all where a client does not need them.

Why a lighter website is a better website

Not everything on this page needs an environmental argument behind it. Reducing page weight is one of the rare cases where the environmental choice and the commercial choice point in exactly the same direction. A lighter site is simply a better site to use.

• It loads faster, on every connection, which is the single most reliable driver of whether a visitor stays
• It scores better on Core Web Vitals — the load, responsiveness and stability signals Google uses as a ranking factor
• It works properly on slow mobile connections, which is still the reality for a large share of UK visitors outside the biggest cities
• It runs well on older, cheaper devices, rather than assuming everyone has a recent flagship phone
• It costs less to host and less to serve at scale, because you are moving fewer bytes
• It converts better, because every second of waiting is a percentage of visitors who leave before they see what you offer

This is why we do not treat sustainability as a separate service or an add-on. Building a site that loads quickly and does not waste a visitor’s data allowance is the same work as building a site that performs well in search and turns visitors into enquiries. If we had to justify page weight on environmental grounds alone, we would still do it — but we do not have to.

Measuring what we build

Page weight is measurable, and we measure it. We can tell you how large a page is, how many requests it makes, what the heaviest assets are and how quickly it renders on a simulated mobile connection. Those are facts taken from the site itself, not estimates, and we are happy to share them.

Estimating carbon is a different matter and deserves more caution. There are established tools that model the emissions of a page view based on page weight, the energy intensity of the network and data centre, and the device used. We can run one of those estimates for a page and talk through the result with you. What we will always be clear about is that it is an estimate produced by a model, not a measurement of your website’s actual energy use. The model does not know which data centre served the request, what the local grid was doing at that moment, or what device the visitor was holding.

So we treat those figures as a useful directional signal — good for comparing one version of a page against another, or for spotting the one asset that is responsible for most of the weight — and not as an audited number to publish. We will not present a modelled estimate as a measured fact, and we will not quote a saving in tonnes of CO₂ that we cannot stand behind.

Hosting

We do not own or operate data centres. For almost every project we host with a third-party provider, which means the energy that serves your site is largely determined by decisions we do not make. We think it is better to say that plainly than to imply otherwise.

What we can do is help you choose well, and be clear about how much a hosting choice actually tells you. Providers vary widely in how their data centres are powered, and the claims they make vary in quality too. When we help a client pick a host, we look for a credible, specific commitment to renewable electricity — one that names what it covers rather than relying on certificates and a logo. A provider that publishes detail about its energy sourcing is generally a better sign than one that simply puts a green badge on its pricing page.

We also weigh factors that reduce consumption directly: whether there is a content delivery network so files travel a shorter distance, whether the platform is efficient enough that we do not need oversized infrastructure to run a modest site, and whether the provider keeps its hardware in service rather than refreshing on a short cycle. We are happy to discuss any of this with you, and if you already have a host you would rather stay with, we will work with it and tell you honestly what we think of it.

What we do not claim

This section exists because a sustainability page that only lists good intentions is not worth much. Environmental claims in the UK are regulated — the Competition and Markets Authority has published guidance on green claims, and the Consumer Protection from Unfair Trading Regulations 2008 make vague or unsubstantiated environmental statements a genuine legal risk for businesses that make them. We would rather be accurate than impressive.

So, plainly:

• We are not carbon neutral. We have not measured our operations in enough detail to make that statement, and we would not make it if we had not.
• We do not claim net zero, carbon negative or climate positive. Jones Digital has no target date and no verified figure behind any of those terms.
• We have not been independently audited or certified by any environmental body. Nothing on this page is third-party verified.
• We do not buy carbon offsets as a substitute for reducing the weight of what we build. Reducing consumption comes first; offsets would, at our size, be a marketing gesture.
• We do not know the exact energy use of the sites we build. We know their page weight and their request count, and we can model the rest — that is the limit of what we can honestly say.
• We will not use your project to make an environmental claim on your behalf. If your customers need a verified figure, we will tell you we cannot supply one.

What is left after those exclusions is smaller, but it is real: we build lighter websites, we measure them, and we can show you the numbers. That is the claim we are prepared to make, and it is one we can support.

How we work as a studio

Jones Digital is a small, remote-first studio working with businesses across South Wales and remotely in the UK. These are the everyday things we do, and we will be honest about their scale: they are small levers compared with the weight of the sites we build. We list them because they are true, not because they are impressive.

• Working remotely means no daily commute and no office to heat, light and power.
• Meeting remotely by default avoids unnecessary travel. Where a meeting genuinely has to be in person, we plan it so one trip covers more than one purpose.
• We work digitally. Documents, files and client communication live online rather than being printed and posted, and we do not print for the sake of having a paper copy.
• We keep our equipment in service for as long as it is genuinely usable rather than upgrading on a fixed cycle, and we buy refurbished or repaired where that is the sensible option.
• We buy hardware when there is a reason to, not on a refresh schedule, and we do not hold spare machines we do not need.
• We choose tools with efficiency in mind and pay attention to how the providers we use run their own infrastructure.
• We are a sole trader business without a large supply chain, which keeps our operational footprint small — but also means there is very little for us to reduce, which is why we focus on our work rather than our office.

What clients can ask for

If sustainability matters to your business — because your customers ask about it, because your own commitments require it, or because you would simply rather not pay to serve files nobody looks at — tell us at the start of the project. None of this is an unusual request and none of it needs justifying.

You can ask us to:

• Build to a page weight and performance budget, agreed with you and checked before launch
• Tell you the page weight, request count and largest assets for any page we build
• Recommend hosting with a credible renewable electricity commitment, and explain what we looked for
• Reduce or remove third-party scripts and trackers, including adding none at all if you do not need analytics
• Avoid loading fonts, video or animation the page does not actually need
• Review an existing site and tell you honestly where the waste is, whether or not we built it
• Explain any decision we have made on a project in terms of weight, requests or performance

There is one thing we cannot provide, and we will say so upfront rather than after you have asked: we cannot give you an audited emissions figure or a certified environmental report for your website. If you need that for a tender, a regulatory disclosure or a customer questionnaire, we are not the right source, and we would rather tell you now than produce a number we cannot support.

Reviewing this policy

We review this page periodically — at minimum once a year — and update it as our practices change, as better methods become available, or as we find we are doing something that no longer holds up. When we review it we will look at the specific promises on it rather than just re-reading the wording: are we still measuring page weight, are we still avoiding unnecessary scripts, are the things we said we do still true.

We commit to being honest if we have not made progress. If we set out to change something and did not manage it, we will either say so on this page or remove the claim. A policy that quietly accumulates things we no longer do is worse than no policy at all, and it is exactly the failure mode this page is written to avoid.

If you have a suggestion, or you think there is something we should be doing that we are not, we would genuinely like to hear it. We would rather be corrected than left with a claim we cannot defend.

Contact for sustainability questions

If you want to ask about anything on this page — how we build for weight, what we measure, how we approach hosting, or whether we can work to a budget you have been given — email us at contactus@jonesdigital.co. If you are already a client and would like the page weight figures for your site, ask and we will send them over.

You can also read more about how we build in our process, see our pricing and the packages we offer, or book a free consultation. For anything relating to your personal information rather than the environment, our privacy policy sets out what we hold and why.