You don't need a redesign or a developer on retainer to make a real dent in your page weight. You need an hour, a laptop with Chrome, access to your site's admin area and one page to focus on: usually the home page, or whichever page gets the most visits. This checklist is the order we'd work in. Each step links to a fuller guide if you want the detail, so you can stay on the clock. Write down what you change as you go; you'll want it at the end.
Minutes 0–10: measure before you touch anything
- Check the page with GreenTracer. Note the grade, the grams per page view, the data measured and which device (mobile or desktop) the result is based on. The report uses the heavier of the two, so that's the one to beat.
- Open the page in Chrome, open DevTools (F12) and the Network panel, tick “Disable cache” and reload. The status bar shows the total transferred. Click the Size column header to sort by size.
- Write down the five largest files. That list is your plan for the rest of the hour. Our guide on how to check your page weight walks through this in more detail.
Minutes 10–25: the biggest images
If an image is on your top-five list, start there. The usual culprits are a hero photo uploaded straight from a camera or stock site, a slider with several full-width images, or a logo saved as a large PNG.
- Resize the largest image to roughly the width it is actually shown at, and export it as WebP or AVIF.
- Replace the file in your media library rather than uploading a second copy alongside it.
- If a slider repeats the same message five times, consider keeping the best slide.
Image weight: the quickest win covers formats, sizes and lazy loading properly. In fifteen minutes, aim to fix one or two files well rather than all of them badly.
Minutes 25–40: plugins, widgets and embeds
Go back to your Network list and look at which domains the larger files come from. Anything that isn't your own domain came from a plugin, widget, tag or embed. For each one, ask a plain question: who uses this, and when did they last look at it?
- Deactivate plugins you no longer use, such as an old popup, a slider you replaced or a social feed nobody updates. Do it one at a time and check the page still works. Our guide to finding unused JavaScript helps with the less obvious ones.
- Put maps, chat and video behind a click where you can, so the full embed loads only for visitors who want it. See maps, chat and embeds on demand.
- Review tracking tags. Old pixels and tags from finished campaigns often linger. Our article on cookie banners, tags and your carbon test explains why some tags don't show up in the test but still load for visitors who accept.
Minutes 40–45: fonts
Filter the Network panel to “Font” and count the files. If you see several weights and styles of the same family, check which ones the design actually uses. Dropping an unused italic or extra-bold weight is often a single setting in your theme or font plugin. If you want to go further, keep the look, lose the weight explains how.
Minutes 45–55: caching and compression
These two settings live on your server or hosting control panel, so this step is mostly a check. In the Network panel, click your main page request and a stylesheet or script from your own domain, and look at the Response Headers:
- Compression. Text files (HTML, CSS, JavaScript) should show a
content-encodingofbr(Brotli) orgzip. Google's Lighthouse guidance says text-based resources should be served compressed, and that Brotli can reduce file sizes more than the alternatives. Images like JPEG are already compressed, so don't expect this header on them. More in text compression: gzip and Brotli. - Caching. Images, fonts, CSS and scripts should carry a
cache-controlheader with amax-age. Lighthouse's cache policy guidance suggests caching unchanging static files for a long time, such as a year or longer. See browser caching explained.
If either is missing, that's a question for your host or web person rather than a ten-minute fix. One honest note: GreenTracer measures a first visit with nothing cached, so better caching helps your returning visitors but won't change your result. Compression does, because it reduces the bytes the test measures.
Minutes 55–60: re-check and compare
Clear any caching plugin or CDN cache so the live page reflects your changes, then check the same page again. Your saved report keeps the earlier check in its history, so you can compare the data measured side by side, not just the grade. Each megabyte you removed lowers the estimate by about 0.148 g CO₂e per page view under the Sustainable Web Design Model v4, or about 0.121 g on a host listed as green.
If the number barely moved, look at the device the result is based on; a fix that only helped mobile won't show if desktop is heavier. And if it moved a lot, download the PDF of the report and file it with your list of changes. GreenTracer doesn't re-check pages automatically, so put a reminder in your diary to check again after your next round of changes.
