How heavy is your website?
What makes pages heavy, how to measure page weight in your own browser and what to cut first, with examples from our work.

Contents8
Every time someone opens a page on your website, their phone or computer downloads all of it: the text, the images, the fonts, the scripts and anything those scripts fetch in turn. The total is the page’s weight, and it is measured in kilobytes or megabytes.
Weight is not the only thing that decides how fast a page feels, but it is one of the easiest to see and one of the easiest to reduce. A lighter page usually loads sooner on a weak connection, uses less of a visitor’s data package and asks less of the networks, servers and devices that carry it. That last point is why page weight comes up in conversations about digital sustainability: data transfer and the devices that process it use electricity, so sending less of it is a small, practical place to start.
This post is for small organisations and businesses that want to know where their weight comes from and what to do about it.
What makes a page heavy
On most small websites, a handful of things account for most of the weight. Text is rarely one of them.
- Images. Photos uploaded straight from a camera or phone are often several times larger than the space they fill on screen. A gallery or a long page of products multiplies the problem.
- Video. A background video that plays automatically is downloaded whether or not anyone watches it, and it is often the single largest file on the page.
- Web fonts. Each family, weight and style is a separate file. Three families in several weights each, with full character sets, add up quickly.
- Third-party scripts. Analytics, advertising tags, social media embeds and tracking pixels each load their own code, and some load more code after that.
- Chat widgets. A chat bubble in the corner often loads a large script on every page, even for visitors who never open it.
- Sliders and carousels. A rotating banner loads every slide’s image, not only the one on screen, and usually a script library to animate them.
- Embedded maps and players. A map or video embed brings its provider’s code with it. That can be worth it on a contact page and wasteful on every page.
None of these is wrong in itself. The question is whether each one earns its weight on the page where it appears.
How to measure it
You do not need special tools. The browser you already use can show the weight of any page.
The network panel
In Chrome, Edge or Firefox, open the developer tools (F12, or right-click and choose Inspect) and go to the Network tab. Tick “Disable cache” so you see what a first-time visitor downloads, then reload the page.
At the bottom of the panel you will see the number of requests and the amount transferred. Transferred is the compressed size that travelled over the network, which is what matters for the visitor’s connection. Chrome also shows a larger “resources” figure, which is the size after decompression.
Then look closer:
- sort by size to find the largest files
- filter by type (images, scripts, fonts, media) to see which group dominates
- check the domain of each request to see how much comes from other companies’ servers
PageSpeed Insights
PageSpeed Insights runs a test on Google’s servers and lists opportunities such as images that could be smaller and code the page does not use. Our article on why website speed matters explains how to read its results and what the main metrics mean.
A few habits that help
- Test several page types, not only the homepage. A product or gallery page is often much heavier.
- Try the site on a phone using mobile data, not only on office Wi-Fi.
- Write the numbers down: weight, number of requests and the largest file. They are your baseline for comparing later changes.
What to cut first
Start where the weight is. In most cases that means this order.
Images first. Resize each image to the largest size it is actually displayed at, compress it and use a modern format such as WebP or AVIF. Offer several sizes so phones do not download a desktop image. Load images further down the page only when the visitor gets close to them, but let the main image at the top load straight away.
Then autoplay video. Replace a background video with a still image, or show a poster image with a play button so the video downloads only when someone asks for it.
Then third-party scripts. Make a list of every external script: what it does, who owns it and who looks at what it collects. Remove the ones nobody uses. Load the ones you need, such as a chat or booking widget, only when the visitor interacts with them, or only on the pages where they matter.
Then fonts. Use fewer families and weights. Serve them as WOFF2 files from your own domain, and cut them down to the characters your languages need. For Albanian and English, the Latin characters, including ë and ç, are enough.
Then sliders. One clear image and one clear message usually do more than five rotating ones, and they weigh a fraction as much.
After each change, measure again with the same method and check that forms, menus and other features still work.
Hosting choices
Where and how a site is served affects how much work each visit causes.
- Static hosting. A site built ahead of time into HTML files, with a tool like Hugo, does not need a database query or server code for each visit. The server only sends files.
- Caching. Files that rarely change, such as styles, scripts, fonts and images, can be stored by the visitor’s browser and reused on the next page or the next visit. Give those files names that change when their content changes, so updates still reach people.
- A CDN. A content delivery network keeps copies of your files on servers in many locations and serves each visitor from a nearby one. Many static hosts include one.
Static hosting does not make a page light on its own. A static page with large images and heavy scripts is still heavy. It does remove a whole layer of work from every visit.
Why it matters on mobile networks
In Albania, as in many places, people often open websites on a phone over mobile data. Coverage and speed vary with the place and the time: a city centre, a village in the hills and a crowded beach in August are very different conditions. Many people also use data packages with a monthly limit, so every heavy page uses part of their allowance.
A lighter page holds up better across those conditions. It is not a guarantee of speed, but it gives every visitor a better starting point, including the ones on the weakest connection.
Two projects where weight was part of the message
Some organisations have a particular reason to care about page weight: their work is about the environmental cost of technology.
Dirty Data Centers
Dirty Data Centers is a campaign site by the Athena Coalition about the environmental impact of large data centers in the United States. We built it in 2024 with Hugo, and it is hosted on GitLab Pages.
The campaign’s arguments are written as text with links to their sources, there is a section for partner organisations, and an embedded form lets supporters prepare a letter to decision-makers. That form is a third-party script worth keeping, because the letter is the action the page exists for. A site arguing about the energy demands of computing should not add needless weight of its own, and a text-first, static site keeps the focus on the arguments.
Green Screen Coalition
The Green Screen Coalition connects climate justice with digital rights, bringing together funders and practitioners in a shared network. We built the site in 2023 with Hugo and Bootstrap, hosted on GitLab Pages, with light and dark themes.
The site presents the coalition’s catalyst fund, resource library and blog in two languages, with a newsletter signup for updates. For an organisation that works on the climate implications of technology, a static site with a clear structure fits the subject.
How we keep ueb.al light
We apply the same rules to our own site:
- Fonts. The main text and code typefaces are two variable fonts, self-hosted as WOFF2 files and cut down to Latin characters, which include ë and ç.
- Images. Blog images are generated by Hugo as WebP in several widths from one source file, with their dimensions set so the layout does not jump. Images below the first screen load lazily.
- No analytics. The site does not load an analytics script, as our privacy policy states. The Cal.com booking widget loads only when you choose to book a call.
- Scripts by page. The scripts for blog posts, the quiz and the job application form load only on the pages that use them.
- Static hosting. The site is built with Hugo, minified and published to GitHub Pages.
At the bottom of every page, the footer shows how much that page weighs, measured by your own browser as it loads. You can compare it with the network panel and check our work.
A short checklist
- Measure your three most visited pages and write down the weight and number of requests.
- Find the largest file on each and ask whether it needs to be that size.
- List every third-party script and remove the ones nobody uses.
- Check whether any video plays automatically.
- Count your font files.
- Measure again after each change.
If you want help finding what makes your site heavy, look at examples in our portfolio or send us your site.


