Scanned sites / plausible.io / 2026-09-28-0542

plausible.io scan from 9/28/2026, 5:42:45 AM

Scan 2026-09-28-0542

Scanned 9/28/2026, 5:42:45 AM, finished 9/28/2026, 5:59:24 AM. Found with 42backlinks.com tool directory

Site: https://plausible.io/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

76/ 100Good

On September 28, 2026 the Site Spider crawled 447 pages and 574 assets of plausible.io, starting from https://plausible.io/. It scored 76 out of 100, a good result. 13 of 16 checks found something to fix, led by heavy assets (45), broken links (85), title tags (145); 2 checks passed. Most of the points went to heavy assets (−6), broken links (−4.9), title tags (−4.2). 1 check found something the score does not count, listed as noted. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium2 medium and 2 low findings. See the security findings ↓

Pages crawled
447
Assets fetched
574
Status
Completed
Checks with issues
13 of 16
CoverageComplete crawl

1,021 of 1,022 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 385 left unchecked.

  • Title tags145 issues
    145 of 287 pages have title issues. 62 noindex or canonicalized pages excluded.
    −4.2 points
  • Meta descriptions153 issues
    153 of 287 pages have meta description issues. 62 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 287 pages have heading issues. 62 noindex or canonicalized pages excluded.
  • Broken links85 issues
    85 internal links point at 85 broken URLs.
    −4.9 points
  • Links to other sites11 issues
    11 destinations answered with an error, 67 could not be determined (timeouts, rate limits or refusals), 385 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.3 points
  • Redirects12 issues
    13 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses85 issues
    98 URLs did not return a 2xx response. 98 of them are pages, 85 with an error status; the rest are assets or redirects.
    −2.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability4 issues
    4 of 288 indexable pages have indexability warnings. 61 pages noindex by design.
    −0.1 points
  • Image alt text163 issues
    163 of 1626 image references have no alt attribute. 163 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets45 issues
    45 assets larger than 500 KB among 574 fetched assets.
    −6 points
  • Orphan pages8 issues
    8 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage130 issues
    1 sitemap listing 163 URLs: 124 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
    −2.2 points
  • Internal link countsOK
    Internal link counts for 349 pages.
  • Thin content6 issues
    6 of 287 pages have fewer than 200 words. 62 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1349 sites, median 80%, average 79%

plausible.io scores 76%, higher than 32% of the 1349 scanned sites. See the full ranking.

039780%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 2 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 5 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 9 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 14 sites63%: 12 sites64%: 8 sites65%: 14 sites66%: 14 sites67%: 27 sites68%: 24 sites69%: 14 sites70%: 32 sites71%: 29 sites72%: 39 sites73%: 33 sites74%: 41 sites75%: 40 sites76%: 49 sites77%: 45 sites78%: 59 sites79%: 48 sites80%: 67 sites81%: 78 sites82%: 66 sites83%: 61 sites84%: 60 sites85%: 45 sites86%: 50 sites87%: 47 sites88%: 49 sites89%: 36 sites90%: 29 sites91%: 30 sites92%: 18 sites93%: 8 sites94%: 10 sites95%: 5 sites96%: 7 sites97%: 3 sites98%: 1 site99%: 2 sites100%: 50 sites76% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your site has several issues needing attention, especially broken links and meta descriptions. Addressing these will enhance user experience and SEO.

  1. 1

    Fix Broken Links

    Why: 85 links are broken, leading to poor user experience and SEO penalties.

    How: Update or remove broken links on the site, redirecting if necessary.

    Checks: broken-links

  2. 2

    Improve Meta Descriptions

    Why: 153 pages have issues, affecting click-through rates.

    How: Write unique and relevant meta descriptions for affected pages.

    Checks: meta-descriptions

  3. 3

    Address Title Tag Issues

    Why: 145 title tags are problematic, impacting search visibility.

    How: Ensure each title is unique and within optimal length (50-60 characters).

    Checks: titles

  4. 4

    Shrink Heavy Assets

    Why: Large assets can slow down the site, affecting performance.

    How: Optimize or replace large assets, focusing on those over 500 KB.

    Checks: heavy-assets

  5. 5

    Remedy Non-200 Responses

    Why: 98 URLs returned errors, harming site credibility.

    How: Check and correct the 98 URLs for proper functionality.

    Checks: status-codes

  6. 6

    Update Sitemap Coverage

    Why: 124 URLs missing in the sitemap can lead to poor indexing.

    How: Ensure all relevant pages are included in the sitemap and that broken links are fixed.

    Checks: sitemap-coverage

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

The website lacks several key security headers, which could expose users to risks such as man-in-the-middle attacks, clickjacking, MIME sniffing, and unwanted referrer data sharing. Implementing these headers will enhance the overall security posture significantly.

  • 0 high
  • 2 medium
  • 2 low
  • 0 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be exposed to man-in-the-middle attacks when accessing the site over HTTP.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-OptionsMedium

    Why it matters: Lack of X-Frame-Options allows clickjacking attacks which can deceive users into clicking on hidden elements.

    Fix: Add the header: X-Frame-Options: DENY or use a Content Security Policy with frame-ancestors.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-OptionsLow

    Why it matters: Without this header, the browser may incorrectly interpret file types, leading to potential security issues.

    Fix: Add the header: X-Content-Type-Options: nosniff

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-PolicyLow

    Why it matters: Absence of a Referrer-Policy can expose sensitive URL information when users navigate away from the site.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade

    Evidence: Referrer policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://plausible.io/ → no strict-transport-security
    • https://plausible.io/simple-web-analytics → no strict-transport-security
    • https://plausible.io/lightweight-web-analytics → no strict-transport-security
    • https://plausible.io/privacy-focused-web-analytics → no strict-transport-security
    • https://plausible.io/open-source-website-analytics → no strict-transport-security
    • https://plausible.io/eu-hosted-web-analytics → no strict-transport-security
    • https://plausible.io/for-ecommerce → no strict-transport-security
    • https://plausible.io/for-saas → no strict-transport-security
    • https://plausible.io/for-freelancers-agencies → no strict-transport-security
    • https://plausible.io/for-bloggers-creators → no strict-transport-security
    • https://plausible.io/for-public-sector → no strict-transport-security
    • https://plausible.io/white-label-web-analytics → no strict-transport-security
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://plausible.io/ → no x-frame-options
    • https://plausible.io/simple-web-analytics → no x-frame-options
    • https://plausible.io/lightweight-web-analytics → no x-frame-options
    • https://plausible.io/privacy-focused-web-analytics → no x-frame-options
    • https://plausible.io/open-source-website-analytics → no x-frame-options
    • https://plausible.io/eu-hosted-web-analytics → no x-frame-options
    • https://plausible.io/for-ecommerce → no x-frame-options
    • https://plausible.io/for-saas → no x-frame-options
    • https://plausible.io/for-freelancers-agencies → no x-frame-options
    • https://plausible.io/for-bloggers-creators → no x-frame-options
    • https://plausible.io/for-public-sector → no x-frame-options
    • https://plausible.io/white-label-web-analytics → no x-frame-options
  • FoundMIME sniffing protectionLow

    61 of 349 HTML pages send x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://plausible.io/ → no x-content-type-options
    • https://plausible.io/simple-web-analytics → no x-content-type-options
    • https://plausible.io/lightweight-web-analytics → no x-content-type-options
    • https://plausible.io/privacy-focused-web-analytics → no x-content-type-options
    • https://plausible.io/open-source-website-analytics → no x-content-type-options
    • https://plausible.io/eu-hosted-web-analytics → no x-content-type-options
    • https://plausible.io/for-ecommerce → no x-content-type-options
    • https://plausible.io/for-saas → no x-content-type-options
    • https://plausible.io/for-freelancers-agencies → no x-content-type-options
    • https://plausible.io/for-bloggers-creators → no x-content-type-options
    • https://plausible.io/for-public-sector → no x-content-type-options
    • https://plausible.io/white-label-web-analytics → no x-content-type-options
  • FoundReferrer policyLow

    61 of 349 HTML pages send referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://plausible.io/ → no referrer-policy
    • https://plausible.io/simple-web-analytics → no referrer-policy
    • https://plausible.io/lightweight-web-analytics → no referrer-policy
    • https://plausible.io/privacy-focused-web-analytics → no referrer-policy
    • https://plausible.io/open-source-website-analytics → no referrer-policy
    • https://plausible.io/eu-hosted-web-analytics → no referrer-policy
    • https://plausible.io/for-ecommerce → no referrer-policy
    • https://plausible.io/for-saas → no referrer-policy
    • https://plausible.io/for-freelancers-agencies → no referrer-policy
    • https://plausible.io/for-bloggers-creators → no referrer-policy
    • https://plausible.io/for-public-sector → no referrer-policy
    • https://plausible.io/white-label-web-analytics → no referrer-policy
11 checks passed, 1 not applicable
  • OKHTTPS

    All 349 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 61 of 349 pages.

  • OKPermissions policy

    permissions-policy is set on all 349 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKCookie flags

    All 2 cookies carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    3 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Sites scoring near plausible.io

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling plausible.io from its pages as published, the way a search engine does. It shows summary figures only.

Own plausible.io?

plausible.io scan 2026-09-28-0542 | DIY SEO Hub