Rudra Analyzer

Sample data — not a real website

Sample website audit report

This is what you get after a check: an overall health score, a score for each area, the problems to fix first with the evidence behind them, and how to fix each one.

Analyze my website — free

Sample data. “Maple Street Bakery” (maple-street-bakery.example) is a made-up website. These scores and findings were written to show what a report looks like — they were not measured on a real site. Your own report is built only from what the checks observe on your pages.

Website health — 76 / 100

Needs attention
Checks performed
30
Passed
19
Warnings
6
Failed
5
Info
0
Not tested
0

Scores by area

  • Website security71 / 100Needs attention3/5 checks passed
  • SEO68 / 100Needs attention4/7 checks passed
  • Speed74 / 100Needs attention3/5 checks passed
  • Accessibility76 / 100Needs attention3/5 checks passed
  • Mobile experience81 / 100Needs attention3/4 checks passed
  • Links & page errors88 / 100Needs attention3/4 checks passed

Fix these first

The most important problems we found, with the easier fixes listed first.

  1. High prioritySEO

    Search results have no description of this page

    Observed: (missing)

    https://maple-street-bakery.example/

    Search engines show the description under your page title. Without one they pick a random sentence from the page, which is rarely the one that earns the click.

    Issue id: seo-meta-desc-missing

    How to fix
  2. Medium priorityWebsite security

    Browsers aren't told to always use the secure connection

    Observed: (header missing)

    https://maple-street-bakery.example/

    Without it, a visitor's first request can be made over plain HTTP, where it can be intercepted on an untrusted network.

    Issue id: sec-hsts

    How to fix
  3. Medium prioritySEO

    Links shared on social media have no preview

    Observed: 0 of 3 tags present

    https://maple-street-bakery.example/

    When someone shares the page in a chat or on social media, it appears as a bare link instead of a card with a picture.

    Issue id: seo-og

    How to fix
  4. Medium priorityAccessibility

    Four images have no description for screen readers

    Observed: .gallery img:nth-child(1)

    People using a screen reader hear the file name, or nothing. Search engines also use the description to understand the picture.

    Issue id: a11y-img-alt

    How to fix
  5. Medium priorityAccessibility

    Some text is hard to read against its background

    Observed: 2.9:1

    Low-contrast text is hard to read in sunlight and for anyone with reduced vision.

    Issue id: a11y-color-contrast

    How to fix

Quick wins

Smaller problems that should not take long to fix.

What is already working

Checks your page passed, grouped by area.

  • Website security

    • Passed: Site is served over HTTPS
    • Passed: Certificate is valid
    • Passed: X-Content-Type-Options set

  • SEO

    • Passed: Page has a title
    • Passed: Page has one main heading
    • Passed: Canonical URL set
    • Passed: robots.txt found

  • Speed

    • Passed: Layout stays stable while loading
    • Passed: Page responds quickly to input
    • Passed: Text files are compressed

  • Accessibility

    • Passed: Page language is declared
    • Passed: Headings are in a logical order
    • Passed: Links have readable names

  • Mobile experience

    • Passed: Viewport meta tag present
    • Passed: No horizontal overflow — Tablet (768px)
    • Passed: No horizontal overflow — Desktop (1440px)

  • Links & page errors

    • Passed: No JavaScript errors on load
    • Passed: All images load
    • Passed: Contact form has a submit button

What should I do next?

You have the findings. Pick the route that suits you — all three start from this report.

  • Fix it yourself

    Every finding below comes with what we observed and how to fix it. It costs nothing.

    See the fix steps
  • ₹999

    Get a detailed audit

    More depth in every area, with screenshots and a report you can download and share.

    Get detailed audit

  • Get help fixing it

    Send us this site and our team will reply with what we'd fix and a quote. Nothing is charged until you agree.

    Request website fixes

Detailed findings

Everything we found, grouped by area. Each item explains what we found, why it matters and what to do about it.

Website security

Needs attention · 71 / 100 · 3/5 checks passed · 2 issues

  • Medium priorityQuick fix

    Browsers aren't told to always use the secure connection

    What we found
    The home page response has no Strict-Transport-Security header.
    Evidence
    Observed
    (header missing)
    Expected
    max-age of at least 31536000
    Where
    https://maple-street-bakery.example/
    Why it matters
    Without it, a visitor's first request can be made over plain HTTP, where it can be intercepted on an untrusted network.
    What you should do
    Send Strict-Transport-Security: max-age=31536000 from the server or CDN once every page works over HTTPS.
    Technical details
    Issue code
    sec-hsts
    Technical name
    Missing Strict-Transport-Security header
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    HTTP response
    Area
    Website security
  • Low priorityBigger job

    No policy limiting where scripts can load from

    What we found
    The response does not set a Content-Security-Policy.
    Evidence
    Observed
    (header missing)
    Where
    https://maple-street-bakery.example/
    Why it matters
    A policy limits the damage if a script is ever injected into a page. It is defence in depth, not a sign that the site has been attacked.
    What you should do
    Start with a report-only policy, review what it would block, then enforce it.
    Technical details
    Issue code
    sec-csp
    Technical name
    No Content-Security-Policy header
    Severity
    info
    Confidence
    High confidence — directly observed
    Source
    HTTP response
    Area
    Website security
Checks performed5 checks · 3 passed · 1 warning · 1 failed

SEO

Needs attention · 68 / 100 · 4/7 checks passed · 3 issues

  • High priorityQuick fix

    Search results have no description of this page

    What we found
    No <meta name="description"> tag was found in the page head.
    Evidence
    Observed
    (missing)
    Expected
    120–160 characters
    Where
    https://maple-street-bakery.example/
    Why it matters
    Search engines show the description under your page title. Without one they pick a random sentence from the page, which is rarely the one that earns the click.
    What you should do
    Add a 120–160 character description that says what the bakery sells and where.
    Technical details
    Issue code
    seo-meta-desc-missing
    Technical name
    Missing meta description
    Severity
    critical
    Confidence
    High confidence — directly observed
    Source
    HTML
    Area
    SEO
  • Medium priorityQuick fix

    Links shared on social media have no preview

    What we found
    og:title, og:description and og:image are not set.
    Evidence
    Observed
    0 of 3 tags present
    Where
    https://maple-street-bakery.example/
    Why it matters
    When someone shares the page in a chat or on social media, it appears as a bare link instead of a card with a picture.
    What you should do
    Add og:title, og:description and og:image to the page head.
    Technical details
    Issue code
    seo-og
    Technical name
    Missing Open Graph tags
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    HTML
    Area
    SEO
  • Low prioritySome work

    Search engines aren't told this is a local business

    What we found
    No JSON-LD or microdata was found on the page.
    Why it matters
    Structured data lets search engines show opening hours, address and ratings directly in results.
    What you should do
    Add LocalBusiness (Bakery) JSON-LD with the name, address and opening hours.
    Technical details
    Issue code
    seo-structured-data
    Technical name
    No structured data
    Severity
    info
    Confidence
    High confidence — directly observed
    Source
    HTML
    Area
    SEO
Checks performed7 checks · 4 passed · 2 warnings · 1 failed

Speed

Needs attention · 74 / 100 · 3/5 checks passed · 2 issues

  • Medium prioritySome work

    Two large images are slowing the page down

    What we found
    The hero photo and one gallery photo are far larger than the size they are shown at.
    Evidence
    Observed
    1.8 MB and 940 KB
    Occurrences
    2

    2 examples

    • Hero photo: 1.8 MB, shown at 1200×600

      https://maple-street-bakery.example/img/hero.jpg

    • Gallery photo: 940 KB, shown at 400×300

      https://maple-street-bakery.example/img/oven.jpg

    Why it matters
    Images are usually the heaviest thing on a page. On a phone connection these two alone add over a second to the load.
    What you should do
    Resize them to the displayed size, convert to WebP or AVIF, and lazy-load the gallery.
    Technical details
    Issue code
    perf-images
    Technical name
    Oversized images
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    Lighthouse
    Area
    Speed
  • Medium prioritySome work

    The main content takes a while to appear

    What we found
    The largest element (the hero photo) appeared after 3.4 seconds in the lab test.
    Evidence
    Observed
    3.4 s
    Threshold
    2.5 s or less is good
    Where
    https://maple-street-bakery.example/
    Why it matters
    Visitors judge speed by when the main content shows up. Past about 2.5 seconds, more of them leave before it does.
    What you should do
    Fix the hero image first — it is the element being measured.
    Technical details
    Issue code
    perf-lcp
    Technical name
    Largest Contentful Paint is slow
    Severity
    warning
    Confidence
    Medium confidence
    Source
    Lighthouse
    Area
    Speed
Checks performed5 checks · 3 passed · 1 warning · 1 failed

Accessibility

Needs attention · 76 / 100 · 3/5 checks passed · 2 issues

  • Medium priorityQuick fix

    Four images have no description for screen readers

    What we found
    4 <img> elements have no alt attribute.
    Evidence
    Occurrences
    4

    2 examples

    • CSS selector:
      .gallery img:nth-child(1)
      HTML snippet:
      <img src="/img/sourdough.jpg">
    • CSS selector:
      .gallery img:nth-child(2)
      HTML snippet:
      <img src="/img/croissant.jpg">
    Why it matters
    People using a screen reader hear the file name, or nothing. Search engines also use the description to understand the picture.
    What you should do
    Describe each product photo in a few words; use an empty alt for purely decorative images.
    Technical details
    Issue code
    a11y-img-alt
    Technical name
    Images missing alt text
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    axe-core
    Area
    Accessibility
  • Medium priorityQuick fix

    Some text is hard to read against its background

    What we found
    3 text elements fall below the 4.5:1 contrast ratio.
    Evidence
    Observed
    2.9:1
    Expected
    4.5:1 or higher
    Occurrences
    3
    Why it matters
    Low-contrast text is hard to read in sunlight and for anyone with reduced vision.
    What you should do
    Darken the grey used for the opening hours and footer links.
    Technical details
    Issue code
    a11y-color-contrast
    Technical name
    Insufficient colour contrast
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    axe-core
    Area
    Accessibility
Checks performed5 checks · 3 passed · 1 warning · 1 failed

Mobile experience

Needs attention · 81 / 100 · 3/4 checks passed · 1 issue

  • Medium prioritySome work

    The page is wider than a phone screen

    What we found
    On Mobile (375px) the page is 412px wide. Widest offender: table.price-list.
    Evidence
    Observed
    Mobile (375px)
    Occurrences
    1

    1 example

    • Mobile (375px): 412px wide vs 375px screen

      CSS selector:
      table.price-list
    Why it matters
    Visitors on phones have to scroll sideways, and anything past the edge is easy to miss.
    What you should do
    Give the price table its own overflow-x:auto container, or stack its columns on small screens.
    Technical details
    Issue code
    resp-overflow
    Technical name
    Horizontal overflow detected
    Severity
    warning
    Confidence
    High confidence — directly observed
    Source
    Browser
    Area
    Mobile experience
Checks performed4 checks · 3 passed · 1 failed
  • Failed

    No horizontal overflow — Mobile (375px)

    Observed: page 412px vs 375px screen

    See finding: No horizontal overflow — Mobile (375px)
  • Passed

    Viewport meta tag present

    Observed: width=device-width, initial-scale=1

  • Passed

    No horizontal overflow — Tablet (768px)

  • Passed

    No horizontal overflow — Desktop (1440px)

Links & page errors

Needs attention · 88 / 100 · 3/4 checks passed · 1 issue

Checks performed4 checks · 3 passed · 1 warning
  • Warning

    Links on the page work

    Observed: 1 of 42 returned an error

    See finding: Links on the page work
  • Passed

    No JavaScript errors on load

  • Passed

    All images load

  • Passed

    Contact form has a submit button

How to read a report

Every finding comes from an observation
A finding is reported only when a check saw it: a missing tag in the HTML, a header absent from the response, an element measured wider than the screen. Recommendations explain those findings; they never add new ones.
Evidence and confidence are shown
Each issue lists what was observed, what was expected, where, and how confident the check is. A directly observed value is high confidence; a lab estimate is not.
Lab results are not field results
Speed is measured in a controlled lab test on a simulated phone. It varies between runs and is not the same as what your real visitors experience.
Security checks are read-only
The security area is a posture assessment: HTTPS, certificates, headers and cookies, read from normal responses. Nothing is exploited, brute-forced or probed beyond what any browser requests.
Automated checks have limits
They cannot judge whether your content is persuasive, whether a design is pleasant, or every accessibility barrier a person would meet. Areas that could not be tested are labelled “Not tested”, never scored.

The full list of checks, the tools behind them and how each score is calculated is on the methodology page.

Get your website audited

The free check covers your home page and takes about a minute. No credit card, and no account needed to see the results.

Analyze my website — freeGet help fixing a website