What a website score actually means (and how to read one)
Most scores are opaque numbers. Here’s how NEXORA builds its score and why 'unavailable' is a result, not a bug.
Single-number scores are useful the way a temperature is useful: you know if something is off, but not what to do about it. NEXORA’s score is built to be decomposable all the way down to the individual check.
Six categories are weighted into one number: performance (0.20), security (0.20), SEO (0.20), accessibility (0.15), UX (0.15) and content (0.10). Each category is a list of pass/fail/broken/unavailable checks measured against the live response — the actual HTML, headers, robots.txt and sitemap that a browser would see.
The part most tools skip: when we can’t measure something, it is listed as unavailable rather than assigned a number. Real Core Web Vitals, for instance, need a running browser and real user traffic; a static analyzer faking an LCP number is guessing. We decline to guess, and the report tells you that a browser-based lab would close that gap.
When you see a big gap between the 'website did well on everything we looked at' summary and a headline score, check which categories contributed. Security and performance dominate the weighted total for a reason: slow and insecure sites lose conversions and trust first. If your score is 92, you should be able to explain all eight points it isn’t 100 — and the report shows you exactly where they came from.