Website Health
Website health is more than SEO.
webioom evaluates your site across five real dimensions and organizes the results into one clearer view — not just how you rank in search.
The health score
What the number actually represents
Every completed scan produces an overall health score, plus a score for each of the five categories above. Each category starts from a clean baseline and is reduced by the issues found in it — more serious issues reduce it more than minor ones.
Reach matters too: the same kind of issue affecting many pages — especially your homepage — counts for more than an isolated instance on one rarely-visited page. The five category scores don't contribute equally to the overall number either; some categories tend to affect a site as a whole more than others.
The score is a snapshot of your most recent scan, not a permanent grade — rescanning after changes produces a fresh result. It's meant to be read alongside issue priority and severity, not used as the only signal on its own.
Example only — not a live report
Same severity, different impact
Two medium-severity issues can reduce a category score by very different amounts.
Bars illustrate relative score impact only, not real point values.
Report categories
Five categories, each with real checks
These are the categories every webioom report is organized into. The examples below are checks webioom actually performs today.
SEO
Search engines and social platforms rely on specific signals to represent your pages correctly — when those signals are missing or wrong, your pages are harder to find and less compelling to click.
- Page titles and meta descriptions that are missing or an ineffective length
- Missing or duplicated heading structure (e.g. more than one H1)
- Canonical tags that are missing, invalid, or point somewhere unexpected
- Missing Open Graph tags, which affects how links look when shared
- Pages accidentally excluded from search results, and an unreachable or invalid sitemap
Technical
None of the rest matters if a page isn’t reliably reachable — technical problems can quietly cost you visitors and search visibility without any visual sign on the page itself.
- Pages that are unreachable, return a server error, or a 404
- Missing HTTPS, or HTTPS that redirects back to an insecure HTTP URL
- Redirect chains and redirect loops
- Internal links that point to broken, missing, or redirecting pages
- robots.txt or your sitemap being unreachable
Accessibility
A meaningful share of visitors use assistive technology like screen readers — accessibility issues can make parts of your site effectively invisible to them.
- Images missing descriptive alt text
- A missing page language attribute
- Links or buttons with no readable text for screen readers
Performance
Slow or bloated pages lose visitors before they see anything — response speed and page weight directly shape first impressions.
- Slow initial page response
- Unusually large HTML documents
Content
A page with almost nothing on it gives visitors and search engines little reason to trust or rank it.
- Pages with very little visible text content
Reading a report
Severity vs. priority
Severity
How serious that kind of issue generally is — a fixed property of the issue type itself:
- CriticalSerious problems likely to affect most visitors or search visibility.
- HighSignificant issues worth addressing soon.
- MediumReal issues that matter, but are less urgent.
- LowSmaller refinements and best-practice items.
Priority
How strongly webioom recommends acting on this specific finding right now, relative to everything else in the report.
Two findings can share the same severity but a different priority. A medium-severity issue affecting one rarely-visited page ranks lower than the same kind of issue affecting your homepage and a dozen other pages — priority accounts for reach, severity alone doesn't.
Reading a report
Affected pages
webioom groups repeated findings so you see one entry per issue, not one row per page. Each entry shows exactly how many — and which — pages it affects, so you can immediately tell whether something is an isolated slip or a pattern worth fixing at the template or theme level, instead of page by page.
Example only
Missing image alt text
4 pages affected
Reading a report
webioom doesn't stop at naming a problem
Every finding in a report includes:
Description
Plain-language context for what was found and why it was flagged.
Recommendation
A specific, actionable suggestion for what to do about it.
Affected pages
Exactly which pages the issue was found on.
Action state
Where supported, whether it’s a Safe, AI-Assisted, or Guided fix.
From a report entry to a resolved issue
A report identifies the problem. webioom determines what kind of action is appropriate. Supported fixes move through Prepare, Review, Apply, and Verify — everything else stays a clear, guided recommendation you can act on yourself.