Back to Help Center
Results

Understanding Your Audit Scores

How scores are calculated, what each category means, and how to improve your ratings.

How Scores Are Calculated

Krokanti Audit uses two data sources to generate your scores:

  1. Google PageSpeed Insights API — Provides real Lighthouse scores for Performance, SEO, Accessibility, and Best Practices when available.

  2. Our rule engine — 30+ custom rules that check things PageSpeed doesn't cover: security headers, meta descriptions, structured data, robots.txt, alt text coverage, and more.

When PSI data is available, we use its scores as the primary input. The rule engine supplements with additional checks and provides recommendations regardless.

Score Categories

Performance (40% of Overall)

Based on Core Web Vitals and other speed metrics:

  • LCP (Largest Contentful Paint) — loading speed
  • CLS (Cumulative Layout Shift) — visual stability
  • INP (Interaction to Next Paint) — interactivity
  • TTFB (Time to First Byte) — server response speed
  • FCP (First Contentful Paint) — when first content appears
  • TBT (Total Blocking Time) — main thread blocking

SEO (30% of Overall)

How well search engines can crawl, understand, and rank your page:

  • Meta title and description quality
  • Heading structure (H1, H2, H3)
  • Canonical tags
  • Robots.txt and noindex directives
  • Sitemap presence
  • Structured data (JSON-LD)
  • Mobile friendliness
  • URL structure

Accessibility (20% of Overall)

WCAG 2.1 compliance and usability for people with disabilities:

  • Image alt text
  • Color contrast ratios
  • Form labels
  • ARIA attributes
  • Keyboard navigation signals
  • Link descriptions

Best Practices (10% of Overall)

Technical hygiene and security:

  • HTTPS implementation
  • Security headers (CSP, HSTS, X-Frame-Options)
  • Mixed content
  • Image sizing and formats
  • Font loading

Why My Score Changed

Scores can change between audits for several reasons:

  • Server load — PageSpeed tests real server conditions. If your server was busy, TTFB may be higher.
  • Network conditions — PSI uses a simulated 4G connection. This is consistent but your real-world timing may vary.
  • Content changes — New images, scripts, or CSS you've added
  • Third-party services — Slow responses from analytics, chat widgets, or ad networks

Score vs. Real-World Experience

A 90+ score doesn't guarantee a perfect experience for all users, and a 70 score doesn't mean your site is broken. The score reflects what a simulated test finds under standard conditions.

Field data (from real users via Google CrUX) is the most accurate picture. Use Google Search Console's Core Web Vitals report alongside Krokanti Audit for the full picture.

Was this article helpful? Let us know or browse more articles.