Websouls Research

How the Website Health Check works

What we measure, whose yardsticks we use, how we choose what you should fix first, and what the check deliberately does not do. Homepage only, and it says so.

In short. The verdict rests on public, widely used standards: Google PageSpeed Insights for speed, Google's Chrome UX Report for how fast the page is for real visitors, and the tests and point values published by Mozilla's HTTP Observatory for security headers. Our own contribution is the plain-language fix list, the code you can copy, and the checks a hosting company is well placed to run.

01Speed — Google PageSpeed (lab)

We ask Google PageSpeed Insights to test your homepage on an emulated mid-range phone over a throttled mobile connection, and show its performance score (0–100), when the main content appears (Largest Contentful Paint), and the page's total download size. Google treats 90+ as good and under 50 as poor. The Lighthouse version is printed on every result, because scores can shift slightly between versions. If Google cannot measure the page — for example, because a firewall turns its tester away — we say so and show nothing invented.

02Real visitors — Core Web Vitals (Chrome UX Report)

The same Google call returns what real Chrome users experienced on your page over the last 28 days, at the 75th percentile: loading (LCP, good ≤ 2.5 s), responsiveness (INP, good ≤ 200 ms) and visual stability (CLS, good ≤ 0.1). The page passes only when all three are good. When the page has too few visitors we fall back to the whole site's data, and label it; many smaller sites have none, and we say that plainly. Where real-visitor data exists, it outranks the lab test.

03Security headers — Mozilla HTTP Observatory's method

We read the response headers your server sends and apply the tests and point values Mozilla publishes for its HTTP Observatory: start from 100, lose points for each failing test, and earn bonus points only once the site already scores 90 or more. The grade scale is the same (A+ at 100 and above down to F below 25).

TestWhat it checks
Content Security PolicyWhether the site limits which scripts may run (the main defence against injected code). Report-only or 'unsafe-inline' policies lose points.
Strict-Transport-Security (HSTS)Whether browsers are told to use HTTPS only, for at least six months. max-age=0 switches it off.
Subresource IntegrityWhether external scripts are loaded securely (https://, not // or http://) and, for third-party scripts, pinned with an integrity hash.
X-Frame-Options / frame-ancestorsClickjacking protection. A header sent twice is ignored by browsers, so it counts as missing.
X-Content-Type-Optionsnosniff, sent once.
CookiesCookies set on the homepage carry Secure; session cookies also HttpOnly.
Referrer-PolicyA private policy earns a bonus.
Redirectionhttp:// redirects straight to https:// on the same host.

This is our implementation of Mozilla's published method, not a result from Mozilla's service. The two can differ when a site answers scanners differently — for example, a firewall showing one of them a challenge page, or cookies set for some visitors and not others. Cross-origin (CORS) checks are not run.

What the site owner can actually change. Hosted platforms such as Shopify, Wix, Squarespace and Webflow set every security header themselves; a store owner cannot change them. When we recognise one, we still show the grade exactly as Observatory's rules give it, but we label those tests "set by the platform" and leave them out of your fix list. Likewise, a site's own scripts written as //yourdomain/… cost 50 points under Observatory's rules, yet on an HTTPS-only page they load securely — we show that as a note, not a fix.

04Software and Google's unsafe-site list

From the files your homepage loads, we note the software it reveals — for WordPress sites, the WordPress version and the plugins and theme it uses, with any version numbers in their file addresses — and the PHP version if your server announces it. We compare these with the latest versions WordPress.org publishes and with published records of known security issues from Wordfence Intelligence. A version read from a file address is likely, not certain, and we say so; if a version is not shown, we make no claim about it. The homepage only reveals the add-ons it uses, so a complete check needs access to the site itself.

We also ask Google Web Risk whether your homepage is on Google's list of possibly unsafe sites (malware, phishing, unwanted software). A listing means Google suspects a problem and browsers may warn visitors. Google cannot guarantee that its information is comprehensive and error-free: some risky sites may not be identified, and some safe sites may be identified in error. Advisory provided by Google.

We never publish or keep these results. Websouls' own internal checks of sites it hosts are separate and are shared only with the site's owner.

05The verdict

VerdictWhen
In good shapePageSpeed 90 or more, real visitors pass (or there is no real-visitor data), and a security grade of B (70) or better — unless the site runs on a hosted platform that sets the headers itself (see §03).
Room to improveNothing failing badly, but short of the bar above — for example, real-visitor measures that Google rates "needs improvement".
Needs workAny real-visitor measure is in Google's "poor" range; or, without real-visitor data, PageSpeed is under 50 or the main content takes over 4 s; or a real exposure for visitors: the site is not on HTTPS, the page loads files over insecure http://, http:// visitors are not sent to https://, or the site runs software with a known high-severity security issue. A weak header grade on its own does not make a site "Needs work" — it stops it being called "In good shape".
Possibly hackedThe homepage shows text typical of a break-in (defacement), or Google's Web Risk list includes the site. The only advice shown is what to do about it.
Not live yetThe homepage is a placeholder, a parking page or the server's default page.
IncompleteGoogle could not measure speed this time. We never say "good" about what we could not measure.

06How fixes are ranked

Fixes are ordered by what matters most to visitors and security: failing real-visitor speed and missing HTTPS first, then scripts loaded insecurely, then policies and headers, then page basics. Every fix explains why in plain words and, where it helps, gives code to copy. Image-size advice comes only from Google's own audit of your page (images without width and height make the page jump as it loads); if Google could not test the page, we don't guess.

07Website basics — the research checklist

Below the verdict we also show a website basics score (0–100): what your served HTML declares about mobile setup, security basics, modernity, freshness and SEO tags, scored exactly the way the Pakistan Business Web Index 2026 — Websouls Research's study of Pakistani business websites — scores them. It is a useful checklist and it is comparable with the study, but it reads declarations, not timings, so it sits below the speed and security results rather than above them.

Two honest caveats. The study's instrument counts any width= attribute as a "fixed width" and any literal http:// text as insecure, so a correct change (adding image dimensions) can dip this number slightly, and harmless text (an SVG namespace) can hold it down. Research is correcting both in the next version of the instrument. Our fix list does not follow these quirks — it gives you the right advice even when it costs a point here. Points shown next to a fix ("+N basics") appear only where our check and the study's instrument agree exactly.

Coming soon: how your site compares with other Pakistani business websites — nationally, by city and by industry — from the same study. We'll switch it on once the study's population has been re-scored with the corrected instrument.

08Search basics — can Google find and read your homepage?

A short list of checks that decide whether your homepage can appear in Google at all, and whether Google reads it the way you intend. They are advice only and do not change any score. Only problems that are certain and serious join the "what to fix first" list: a noindex instruction or a robots.txt rule that blocks Google from your homepage (both also change the verdict to "Needs work", because they can remove the site from search), a canonical tag that points to another website or to a page that does not load, the http:// or www. version of your address showing an error, and broken addresses in your sitemap.

CheckHow we decide
Allowed in Googlenoindex or none in the robots or googlebot meta tag, or in the X-Robots-Tag header.
Homepage open to GoogleWe read your robots.txt with the matching rules Google documents: the Googlebot group if there is one (otherwise *), the longest matching rule wins, and Allow wins a tie. No robots.txt means nothing is blocked.
Canonical tagOne canonical, in the <head>, on your own site. If it names another address, we load that address and check it answers directly and is not marked noindex.
Search tags in the <head>Whether the title, description, canonical and robots tags appear before the page body starts. Google reads the canonical only in the <head>. Sites built with some JavaScript frameworks (for example Next.js streaming metadata) send these tags after the body starts.
Title, description, clean textTitle about 15–65 characters, description about 50–165 (Google measures pixels, so these are guides). Text encoded twice (&amp;amp;) is flagged because it shows as "&amp;" in search results.
Image descriptionsImages in the HTML your server sends with no alt attribute, or with a file name as alt text. alt="" marks a decorative image and is fine; tracking pixels and images hidden from screen readers are skipped.
Share linkWhether og:url (the address Facebook, LinkedIn and WhatsApp use) matches the canonical, and whether it loads directly.
http:// and www. versionsWe open each version of your address and follow its redirects ourselves: a certificate error, an error page or a loop needs fixing; more than two redirects, a second copy of the site, or a jump to another page is flagged.
Missing pagesWe open a made-up address on your site. It should answer 404; a page that answers "OK" or jumps to the homepage is a "soft 404".
SitemapFound from robots.txt or /sitemap.xml. We test up to 10 of its addresses, spread across the list; each should load directly, without a redirect or an error.

To run these checks we make up to about 15 small requests to your own website, and only to it: we never follow a redirect to another website or to a private network address. Where your server or firewall refuses us, the check says "not checked" — never "fail".

09What your host can see

Where available we add checks a hosting company is well placed to run — SSL certificate expiry, email deliverability records (SPF, DMARC, MX) and CMS/platform exposure — plus Lighthouse's accessibility score. These are shown as extras and do not change the verdict.

10Known limits

  • Homepage only. Not a crawl; interior pages aren't checked.
  • One moment in time. Lab speed varies a little between runs; real-visitor data is a 28-day view.
  • One vantage point. Headers are read from our server's location. A CDN or firewall can answer differently elsewhere.
  • If a firewall blocks our checker we tell you, show a command your developer can run to see the same thing, and offer a partial report from your pasted page source (no security grade, because headers aren't in the page).
  • Search basics read what your server sends. Tags and images added later by scripts are not seen; the sitemap check is a sample, not every address.
  • Nothing stored. We don't keep the address you check or the results.
← Run the Website Health Check
We are Pakistan’s leading Web Hosting Provider – trusting your site to us means a powerful online presence with an uptime that meets all your expectations, guaranteed.
Our Company
Our Services
Client Information
Support Center
Website Development
Contact Us
Payment Methods
Credit CardPaypalOnline Banking

Copyright © 2002-2026 Websouls. All Rights Reserved.