Useful Stuff

What Does a Website Health Check Actually Check?

Free Website Health Check Audit

A website can be fast and still have problems. Here’s what a proper website health check should look at – and how it differs from Google PageSpeed Insights.

We’ve recently built a free website health check for Ullmatech.

On the surface, it sounds relatively straightforward.

Put a website into a tool, run a few tests, give it a score and tell the owner what needs improving.

Simple, right?

Not quite.

The more we worked on it, the more we realised that answering the question “Is my website actually any good?” is surprisingly difficult.

A website can have an excellent SEO score and still provide a terrible experience for visitors.

It can score highly on desktop but struggle badly on a phone.

It can have a fantastic PageSpeed result one minute and a considerably worse one a few minutes later.

And a website can score 90+ overall while still having some fairly obvious things that could be improved.

So what should a proper website health check actually look at?


What is a website health check?

A website health check is essentially a way of looking at the different things that contribute to a website working properly.

That includes the obvious stuff, such as speed and mobile usability, but also things that aren’t immediately visible when you visit a website.

A useful health check can look at areas such as:

  • Performance โ€“ how quickly pages load and become usable
  • Mobile โ€“ how well the website works on smaller screens
  • SEO โ€“ whether important search-engine fundamentals are in place
  • Technical health โ€“ underlying configuration and technical issues
  • Accessibility โ€“ potential barriers that could make the site harder to use
  • Responsive behaviour โ€“ whether content fits properly across different screen sizes
  • Indexability โ€“ whether search engines can access and understand the site correctly

The important thing is that these aren’t completely separate things.

A slow website can affect the user experience.

Poor mobile design can affect conversions.

Technical problems can prevent otherwise good content from being indexed.

Accessibility problems can make an otherwise attractive website difficult to use.

So rather than looking at one metric, a health check tries to give you a broader picture.


Google PageSpeed Insights vs a Website Health Check

If you’ve ever tested your website with Google PageSpeed Insights, you might reasonably wonder why you would need another website health check.

That’s a fair question.

Google PageSpeed Insights is a very useful tool, and we actually use Google’s PageSpeed data as part of the Ullmatech Website Health Check.

But the two tools are designed to answer different questions.

PageSpeed Insights is primarily concerned with the performance of a particular page.

A broader website health check looks beyond performance to consider other aspects of the website as well.

So while there is some overlap between the two, they’re designed to answer different questions. PageSpeed Insights is primarily concerned with the performance of an individual page, whereas the Ullmatech Website Health Check brings performance together with broader SEO, technical, mobile and accessibility checks.

Here’s a simple comparison of what each one looks at:

What is checkedGoogle PageSpeed
Insights
Ullmatech Website
Health Check
Page loading performanceโœ“โœ“
Core Web Vitalsโœ“โœ“
Mobile performanceโœ“โœ“
Desktop performanceโœ“โœ“
Performance recommendationsโœ“โœ“
SEO fundamentalsLimitedโœ“
Technical website checksLimitedโœ“
Indexabilityโ€”โœ“
Sitemap / robots checksโ€”โœ“
Responsive behaviourLimitedโœ“
Accessibilityโœ“โœ“
Overall website healthโ€”โœ“
Business-friendly summaryโ€”โœ“

The important distinction is this:

PageSpeed Insights asks: “How does this page perform?“

A website health check asks: “How healthy is this website overall?“

They’re therefore not really competing tools.

PageSpeed can be one piece of the puzzle. A health check puts that information alongside other factors.

And we’re certainly not going to pretend that we’ve built a better version of Google’s PageSpeed Insights.

We haven’t.

Google has built an excellent performance-testing tool.

We’ve built something that looks beyond performance.


1. Website performance

Let’s start with the thing most people think of when they hear “website health”.

Speed.

How quickly does the page load?

How quickly can someone see the main content?

How long before the page becomes properly usable?

Performance matters because nobody enjoys waiting for a website to load.

But there’s an important distinction here.

A website health check shouldn’t simply say:

Performance: 78

and leave it at that.

A useful check should help explain why.

A page might be slowed down by:

  • Large images
  • Unused JavaScript
  • Render-blocking resources
  • Poorly configured caching
  • Third-party scripts
  • Large CSS files
  • Slow server response times
  • Fonts and other resources loading inefficiently

That’s much more useful to a business owner than a number on its own.


2. Mobile performance

This deserves its own category.

A website that looks fantastic on a desktop computer isn’t necessarily a good website.

Try it on a phone.

Is everything readable?

Do buttons fit comfortably on the screen?

Can you tap links without accidentally hitting something else?

Does anything stick out beyond the edge of the screen?

Do images scale properly?

Does the layout still make sense?

And perhaps most importantly:

How quickly does it actually load on a mobile connection?

Mobile performance can be considerably different from desktop performance.

That’s why we don’t think a website health check should simply test the desktop version and call it a day.


3. SEO

SEO is another area where a health check can become much more useful than a simple “SEO score”.

There are some fairly basic things every website should get right.

For example:

  • Page titles
  • Meta descriptions
  • Heading structure
  • Canonical URLs
  • Indexability
  • Sitemap availability
  • Robots.txt
  • Internal links
  • Image alt text
  • Open Graph information
  • Structured data
  • Broken links

None of these things guarantees that a website will suddenly appear at the top of Google.

That’s not how SEO works.

But if the foundations aren’t right, you’re making life harder for search engines – and potentially for your visitors too.


4. Technical health

This is the stuff most website owners never see.

And that’s precisely why it’s worth checking.

A website might look completely normal while having technical problems underneath.

A proper health check can look at things such as:

  • HTTPS
  • Canonicalisation
  • Crawlability
  • Indexability
  • Redirects
  • Broken resources
  • Missing metadata
  • Technical configuration
  • Sitemap configuration
  • Mobile viewport settings

You don’t necessarily need to understand all of these things.

That’s rather the point.

A website health check should translate technical problems into something a normal human can understand.

There’s little value in telling someone:

Your canonical configuration has an issue.

and leaving them to Google what that means.

It’s much more useful to explain what the problem is, why it matters and what could be done about it.


5. Accessibility

Accessibility is sometimes treated as something that only matters to organisations with specific legal or compliance requirements.

We think that’s the wrong way to look at it.

At its simplest, accessibility is about making your website usable by as many people as reasonably possible.

That means considering things such as:

  • Colour contrast
  • Form labels
  • Keyboard navigation
  • Image alternative text
  • Heading structure
  • Link clarity
  • Button labels
  • Focus states
  • Appropriate HTML structure

And there is an interesting side effect:

Many accessibility improvements also make websites easier for everyone to use.

Clear buttons are useful to everyone.

Readable text is useful to everyone.

Logical navigation is useful to everyone.


6. Is the website actually responsive?

This sounds obvious.

But we’ve lost count of the number of websites we’ve visited where something looks fine on a laptop but falls apart at a slightly different screen size.

Responsive design isn’t simply:

“Does it work on an iPhone?“

There are thousands of different screen sizes and combinations of browsers and devices.

A useful website should adapt.

Content shouldn’t disappear off the side of the screen.

Buttons shouldn’t become impossible to tap.

Text shouldn’t become microscopic.

Images shouldn’t force the page wider than the viewport.

And layouts shouldn’t suddenly become unusable because somebody is viewing the site on a slightly narrower device than the designer happened to own.

That’s why responsive behaviour is worth checking separately.


7. Does the website actually work for the business?

This is probably the most important question of all.

What is the website actually supposed to achieve?

For one business, the goal might be generating enquiries.

For another, it might be selling products.

For another, it might be getting people to book appointments.

For another, it might simply be establishing credibility before somebody picks up the phone.

A technically brilliant website that doesn’t help the business achieve its objective isn’t necessarily a successful website.

You can have:

  • brilliant PageSpeed
  • perfect SEO fundamentals
  • excellent accessibility
  • technically clean code

…and still have a website that doesn’t generate a single enquiry.

That’s why automated testing has limits.

A tool can tell you a lot about the website.

It can’t completely understand your business.


And then we discovered something annoying about website speed tests

This was probably the most interesting part of building our own Health Check.

We wanted to make the performance result more reliable, so we initially decided to run Google’s PageSpeed test three times and use the middle result.

The logic seemed sensible.

If we got:

60 โ†’ 79 โ†’ 87

we could use 79 rather than allowing one unusually good or bad test to determine the result.

Except there was a problem.

Google was sometimes giving us the same test result three times.

The requests were technically separate, but the results weren’t necessarily independent.

So we changed the way we ran the tests.

We experimented with staggering them.

We looked at duplicate timestamps.

We looked at the individual test results.

Eventually we found a way to make each test genuinely distinct while still testing the same cached version of the website.

And that’s when we started seeing the variation we expected.

The same website could produce results such as:

87

60

79

within the same set of tests.

The website hadn’t suddenly become 27 points worse.

The measurement had simply varied.

That’s an important distinction.


So should you trust a website health score?

Yes – but don’t treat it as gospel.

A score is useful as a way of summarising a larger set of information.

It’s particularly useful for:

  • Spotting obvious problems
  • Comparing a website with itself over time
  • Identifying areas worth investigating
  • Giving a business owner somewhere to start

But a score of 86 doesn’t mean:

“Your website is 14% bad.”

And a score of 96 doesn’t mean:

“Don’t touch anything.”

The useful part isn’t necessarily the number.

It’s what’s behind the number.


What we think a useful website health check should tell you

Building ours has changed the way we think about website audits.

We don’t think the ideal report should simply say:

Your website scored 72/100.

It should tell you:

What’s working?

So you know what you don’t need to worry about.

What’s not working?

So you know where the problems are.

How important is each problem?

Not every warning deserves an emergency redesign.

What could you do about it?

Ideally, in language that doesn’t require a degree in web development.

And does it actually matter to your business?

Because ultimately, that’s the question.


Does a low score mean you need a new website?

Absolutely not.

Sometimes a few relatively simple changes can make a noticeable difference.

You might need:

  • Better image optimisation
  • Improved caching
  • Cleaner code
  • A few SEO fixes
  • Better mobile spacing
  • Improved accessibility
  • Better calls to action
  • A clearer navigation structure

You don’t necessarily need to throw the whole website away.

On the other hand, sometimes an audit exposes a much bigger problem.

If the site is difficult to navigate, outdated, slow, impossible to maintain and no longer reflects the business, then continually patching it probably isn’t the best answer either.

That’s where a proper assessment becomes useful.


What should you actually check on your website?

If you’re looking at your own website, we’d start with these five questions:

1. Is it fast enough?

Especially on mobile.

2. Can Google understand and index it properly?

Good content isn’t much use if search engines can’t properly access it.

3. Does everything technically work?

Links, forms, redirects, images, HTTPS, navigation and so on.

4. Can everyone use it?

Think accessibility, readability and mobile usability.

5. Does it actually help your business?

This is the one automated test can’t answer for you.


Frequently Asked Questions

What is a website health check?

A website health check is a broader assessment of a website’s performance, SEO, technical configuration, mobile experience, accessibility and other factors that can affect how well the site works for visitors and search engines.

What is the difference between a website health check and Google PageSpeed Insights?

Google PageSpeed Insights is primarily a performance testing tool. It measures how a particular page performs, including metrics such as Core Web Vitals and loading performance.

A broader website health check looks beyond speed to assess areas such as SEO, technical configuration, mobile usability, responsive behaviour and accessibility.

The two can therefore complement each other rather than replace one another.

How do I check the health of my website?

Is a website health score important?

A health score can be useful as a summary of a larger set of checks, but it shouldn’t be treated as an absolute measure of how good a website is.

The individual findings behind the score are usually more useful than the number itself.

Why do website speed test results change?

Performance tests can vary because of factors such as network conditions, server response times, caching, resource loading and the testing environment.

That’s why running a single performance test and treating its score as a permanent measurement can be misleading.

Does a low website health score mean I need a new website?

No.

Some websites can improve significantly through relatively straightforward changes to performance, SEO, accessibility, responsive design or technical configuration.

A redesign may be appropriate when the underlying website has broader problems, but a low score alone isn’t enough to establish that.

Should I use Google PageSpeed Insights as well as a website health check?

Yes.

PageSpeed Insights is useful for investigating page performance in detail. A broader health check can put that performance information alongside other aspects of the website.

There’s no reason you can’t use both.


The point of a website health check

Building ours has changed the way we think about website audits.

We don’t think the point is to produce the biggest possible list of problems.

You can find something wrong with almost any website if you look hard enough.

The point is to identify the things that actually matter.

A good website health check should give you a clearer picture of where your website is today, what deserves attention and what probably doesn’t.

And sometimes the conclusion will be:

Your website is fine. Leave it alone.

Other times it might be:

There are a few things worth fixing.

And occasionally it might be:

Yep. It’s probably time for a new website.

The important thing is having enough information to know which one applies.


Want to see how your website scores?

We’ve built a free Ullmatech Website Health Check that looks at performance, SEO, technical health, mobile usability and accessibility.

There’s no obligation and no need to book a call.

Run the check, see what it finds, and decide what – if anything – you want to do about it.

Ullmatech

Make your website work harder for your business.

Start a Project

Let's build your next
digital product.

Whether you need a high-performance WordPress website or a custom Laravel application, we build systems designed to scale.