
Lots of web designers say their websites are “fast” and “SEO-friendly”. We’d rather put a number on it. Every static website we build is guaranteed to score between 95 and 100 for both Performance and SEO in Google Lighthouse, on mobile and desktop.
That’s a bold promise, so this post explains it properly: what Lighthouse is, what those two scores actually measure, how we test them (fairly, and more than once), what we do to hit them, and — just as important — what the guarantee does and doesn’t cover.
Short version: Lighthouse is Google’s free health check for web pages. We test every page we build on mobile and desktop, on the live site, and we don’t hand it over until it scores 95 or more for speed and SEO.
What is Google Lighthouse?
Lighthouse is a free testing tool made by Google. You point it at a web page and it loads that page the way a visitor would, measures how quickly things appear, checks the code for common mistakes and gives you scores out of 100 in four areas: Performance, Accessibility, Best Practices and SEO.
Scores are colour-coded: 90–100 is green (good), 50–89 is orange (needs improvement) and anything under 50 is red (poor). Our guarantee sits at the very top of the green band.
By default Lighthouse tests as if you were on a mid-range mobile phone on a slow 4G connection — deliberately tougher than a laptop on office broadband. That’s a good thing: most people visiting a small business website are on their phone, and if a page is quick under those conditions, it’ll fly everywhere else.
What the Performance score measures
The Performance score is about one simple question: how quickly does the page become useful to the person looking at it? Lighthouse works that out from a handful of timings. Three of them are part of Google’s Core Web Vitals — the measurements Google uses to judge “page experience” — so they’re worth understanding.
- Largest Contentful Paint (LCP) — how long until the biggest thing on screen (usually the main photo or headline) has appeared. It’s the moment a visitor feels the page has “loaded”. Google counts 2.5 seconds or less as good.
- Cumulative Layout Shift (CLS) — how much the page jumps around while it loads. You know when you go to tap a button and an image loads above it, pushing everything down so you tap an advert instead? That’s layout shift. Lower is better; 0.1 or less is good.
- Interaction to Next Paint (INP) — how quickly the page responds when you tap, click or type. Because INP needs a real person interacting, Lighthouse measures a stand-in called Total Blocking Time (TBT): how long the phone is too busy running code to respond to you. Less code to run means less blocking.
Lighthouse also looks at First Contentful Paint (when anything first appears) and Speed Index (how quickly the visible page fills in). It blends all of these into the single Performance score.
What the SEO score measures
The SEO score is different. Rather than timing anything, it’s a checklist of the technical basics that help search engines find, read and understand a page. Things like:
- Does the page have a proper title and meta description (the text Google shows in search results)?
- Does the page load successfully, rather than returning an error?
- Is the page allowed to be indexed, and is the robots.txt file (the instructions for search engines) valid?
- Can search engines follow the links, and do the links have descriptive text rather than “click here”?
- Do images have alt text (a written description for people using screen readers, which search engines read too)?
- Is the canonical address set correctly, so Google knows which version of a page is the “real” one?
We want to be straight with you here: a perfect SEO score doesn’t guarantee you’ll be top of Google. Rankings depend on lots of things Lighthouse can’t see — your content, your competition, reviews, links from other websites and how long your site has been around. What a high score does tell you is that nothing technical is getting in the way. It’s the foundation; we’ve written more about what goes on top of it in why your business needs SEO and 8 SEO no-nos.
How we test
A Lighthouse score is only meaningful if it’s measured fairly, so here’s exactly how we do it.
- We test the live website, not a copy on our computer. Hosting, caching and the real domain all make a difference, so the score that counts is the one your visitors will get.
- We test on mobile and desktop. Mobile is the harder test, and the one we care about most, but we check both.
- We test every page, not just the home page. A fast home page is no use if your services or contact page is slow.
- We run each test several times. Lighthouse scores naturally wobble by a few points from one run to the next — network conditions and the testing computer vary. So we never judge a page on a single lucky (or unlucky) run; we look at the typical result across several.
- We use two tools. PageSpeed Insights runs Lighthouse on Google’s own servers, which keeps things consistent and is easy for you to run yourself. We also use the Lighthouse panel built into Chrome DevTools, which runs on our own computer and shows us in detail what to fix. (If you try DevTools yourself, use a private/incognito window — browser extensions can drag the score down.)
- We check again after launch. Once the site is live on your domain, we re-run the tests to make sure nothing changed on the way.
PageSpeed Insights can also show real-world data from Chrome users visiting your site, alongside the Lighthouse test. A brand-new site won’t have enough visitors for that yet, which is another reason we rely on careful, repeated Lighthouse tests at launch.
How we make websites this fast
There’s no single trick. A 95–100 score comes from lots of small decisions that all point the same way. These are the things we do on every site — and on this one, which you can test yourself.
- Pages built in advance. We build sites with Astro, which creates every page as a finished, ready-to-go file before the site goes live. Your visitor’s phone doesn’t have to assemble anything; it just shows the page. (We explain more in AI and Astro: how we build faster websites.)
- Very little JavaScript. JavaScript is the code that makes things interactive, and it’s the main thing that keeps phones busy (that Total Blocking Time from earlier). We only use it where it’s genuinely needed — a menu, a form, a gentle animation — so there’s very little for a phone to process.
- Images shrunk and resized automatically. Every photo is converted to the modern WebP format and saved at several sizes when the site is built, so a phone downloads a small version and a big desktop screen gets a larger one. Each image also has its size reserved on the page, so nothing jumps around as it loads (good for CLS), and the main image at the top of the page is loaded first (good for LCP).
- Fonts hosted with the site. Instead of fetching fonts from Google Fonts on every visit, we download them when the site is built and serve them from your own domain. The most important ones are preloaded — the browser is told to fetch them straight away — and matching fallback fonts stop the text jumping when they arrive.
- Styles built into the page. The styling (CSS) is small, so we put it directly into each page rather than in a separate file the browser has to fetch before it can show anything.
- Hosting on a global network. Our sites run on Cloudflare, which serves your pages from data centres all over the world — including several in the UK — so the page comes from somewhere close to your visitor rather than a single server miles away.
- Analytics only after consent. Tracking tools like Google Analytics are among the heaviest things on many websites. On ours, they only load once a visitor has said yes in the cookie banner, so they don’t slow the page down for anyone who hasn’t agreed to them.
- SEO built in from day one. Every page gets a proper title and description, a canonical address, image descriptions and sensible headings. The site has an automatic sitemap (a list of every page for Google), a robots.txt file, and structured data — hidden labels that tell Google things like your business name, where you’re based and how to contact you.
What the guarantee covers — and what it doesn’t
We’d rather be clear now than have a misunderstanding later.
What it covers:
- Static websites we design and build — business sites, brochure sites, portfolios and blogs built the way we describe above.
- The Performance and SEO scores in Google Lighthouse, on both mobile and desktop, measured on the live site, using the testing approach set out in this post.
- Every page of the site, as we hand it over at launch.
What it doesn’t cover:
- Heavy third-party add-ons. Things like embedded YouTube videos, Google Maps, booking or chat widgets, social media feeds, review widgets and advertising or tracking scripts all load code from other companies’ servers, which we can’t control. They can knock points off any website’s score, however well it’s built. We’ll always tell you the likely impact before adding one.
- Changes made after launch. If new pages, very large photos or extra scripts are added later, the scores can change. If we look after your site on a maintenance plan, we’ll keep an eye on this for you.
- Websites that aren’t static, such as online shops or web apps with logins and live data. These can still be very fast, but they’re a different kind of project, so we’ll talk you through what to expect.
- Search rankings. As above, a 95–100 SEO score means the technical basics are right; it isn’t a promise of a position in Google.
If any page scores under 95 for Performance or SEO, on mobile or desktop, when we launch your site, we’ll fix it free of charge. The guarantee applies at launch only.
Quick answers
Can I check the scores myself? Yes, and we’d encourage it. Go to PageSpeed Insights, paste in your web address and press Analyse. Try it a few times, as the scores move around a little.
Why does my score change each time I test? Lighthouse is timing a real page load, and small differences in the network and the testing computer change the result slightly. A drop of a few points between runs is normal; a big, consistent drop means something has changed on the site.
Does a faster website really make a difference? Yes. People don’t wait for slow pages, especially on a phone, and page experience is one of the things Google looks at. We’ve covered more ways to improve this in how to speed up your website.
My current website scores badly. Can you help? Absolutely. Our free website audit will show you where your site stands and what’s slowing it down.
The bottom line
A Lighthouse score isn’t the whole story of a good website — great design, clear words and a site that suits your business matter just as much. But it’s an honest, independent measure of whether the technical foundations are right, and it’s one anyone can check. That’s why we’re happy to put a number on it.
If you’d like a website that’s fast, well built and ready for Google from day one, get in touch for a friendly chat.


