Scanned sites / pagespeed.web.dev / 2026-09-25-0320

pagespeed.web.dev scan from 2026-09-25 03:20:41 UTC DR 92

A newer scan exists. See the latest report for pagespeed.web.dev.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-09-25-0320

Scanned 2026-09-25 03:20:41 UTC, finished 2026-09-25 03:28:06 UTC. Found with 42backlinks.com tool directory

Site: https://pagespeed.web.dev/

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

68/ 100Needs work

On September 25, 2026 the Site Spider crawled 1 page and 3 assets of pagespeed.web.dev, starting from https://pagespeed.web.dev/. It scored 68 out of 100, a result that needs work. 4 of 26 checks found something to fix, led by title tags (1), meta descriptions (1), thin content (1); 19 checks passed. Most of the points went to title tags (−10), meta descriptions (−8), thin content (−8). 3 checks found something the score does not count, listed as noted. 11 checks were not run because the crawl fetched nothing for them. 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 1 low findings. See the security findings ↓

Pages crawled
1
Assets fetched
3
Status
Completed
Checks with issues
4 of 26
CoverageComplete crawl

4 of 4 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 18 link destinations on other sites were checked.

  • Title tags1 issue
    1 of 1 page have title issues.
    −10 points
  • Meta descriptions1 issue
    1 of 1 page have meta description issues.
    −8 points
  • HeadingsOK
    0 of 1 page have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites3 noted
    0 destinations answered with an error, 3 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses2 noted
    2 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 1 indexable page have indexability warnings.
  • Image alt textOK
    0 of 3 image references have no alt attribute. 1 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 3 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1 issue
    No sitemap found. Tried: https://pagespeed.web.dev/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −6 points
  • Internal link countsOK
    Internal link counts for 1 page; none is a dead end or buried.
  • Thin content1 issue
    1 of 1 page have fewer than 200 words.
    −8 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 1 page URL are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 1 page have a canonical worth checking.
  • Robots directivesOK
    No page carries a robots directive; all 1 page are open to search engines.
  • Anchor textOK
    Every internal link has descriptive, followed anchor text.
  • Title and heading structure1 noted
    1 of 1 page could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 1 page answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 4 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 1 page; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2284 sites, median 79%, average 78%

pagespeed.web.dev scores 68%, higher than 14% of the 2284 scanned sites. See the full ranking.

0571140%: 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%: 1 site15%: 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%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 16 sites59%: 7 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 45 sites70%: 41 sites71%: 68 sites72%: 70 sites73%: 65 sites74%: 70 sites75%: 71 sites76%: 88 sites77%: 91 sites78%: 104 sites79%: 87 sites80%: 107 sites81%: 106 sites82%: 114 sites83%: 95 sites84%: 107 sites85%: 84 sites86%: 67 sites87%: 71 sites88%: 62 sites89%: 61 sites90%: 33 sites91%: 44 sites92%: 34 sites93%: 20 sites94%: 14 sites95%: 10 sites96%: 9 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 sites68% 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your website needs several improvements including fixing URLs, optimizing title tags, adding meta descriptions, and creating a sitemap. These changes should enhance your site’s SEO health significantly.

  1. 1

    Fix Non-200 Responses

    Why: 404 errors can hurt SEO and user experience.

    How: Update or remove the URL that is returning a 404 status: https://pagespeed.web.dev/robots.txt.

    Checks: status-codes

  2. 2

    Optimize Title Tag

    Why: A short title tag can lower click-through rates.

    How: Change the title tag to be more descriptive (at least 30 characters). For example, 'PageSpeed Insights: Optimize Your Website Performance'.

    Checks: titles

  3. 3

    Add Meta Description

    Why: Missing meta descriptions affect search rankings and visibility.

    How: Create a compelling meta description summarizing the page. Example: 'Use PageSpeed Insights to assess and optimize your website performance.'

    Checks: meta-descriptions

  4. 4

    Create Sitemap

    Why: A sitemap helps search engines index your site more efficiently.

    How: Generate a sitemap and place it at /sitemap.xml. Then, reference it in your robots.txt file.

    Checks: sitemap-coverage

  5. 5

    Address Thin Content

    Why: Thin content may be ignored by search engines.

    How: Add more valuable content to the page, aiming for at least 200 words. Expand on the purpose and benefits of PageSpeed Insights.

    Checks: thin-content

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

This review identifies security concerns for your website related to HTTP headers and content security policies. Addressing these issues will strengthen your site's defenses against attacks and protect user data.

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

    Missing HSTS HeaderMedium

    Why it matters: Without the HTTP Strict Transport Security (HSTS) header, users can be exposed to man-in-the-middle attacks.

    Fix: Implement HSTS by adding the header: 'Strict-Transport-Security: max-age=63072000; includeSubDomains; preload'.

    Evidence: HTTP Strict Transport Security

  2. 2

    Weak Content Security PolicyMedium

    Why it matters: The current Content-Security-Policy allows 'unsafe-inline' scripts, which compromises protection against Cross-Site Scripting (XSS) attacks.

    Fix: Update your CSP to eliminate 'unsafe-inline' and 'unsafe-eval' to improve security.

    Evidence: Content Security Policy

  3. 3

    Third-Party Scripts Without IntegrityLow

    Why it matters: Scripts from external domains lack Subresource Integrity (SRI), making site security vulnerable to compromises in those scripts.

    Fix: Add Subresource Integrity hashes for scripts or restrict loading them using a Content Security Policy that explicitly names these hosts.

    Evidence: Third-party scripts

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://pagespeed.web.dev/ → no strict-transport-security
  • NoteContent Security Policy

    A Content-Security-Policy is set, but it allows inline or eval scripts ('unsafe-inline' / 'unsafe-eval'), which removes most of its protection against injected scripts.

    • https://pagespeed.web.dev/ → require-trusted-types-for 'script';report-uri /_/PagespeedUi/cspreport, script-src 'report-sample' 'nonce-d8ZETRvATiz0D0N2rI6oCA' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/PagespeedUi/cspreport;worker-src 'self'
  • NoteThird-party scripts

    Scripts run from 2 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)

    • www.gstatic.com (1 script tag)
    • www.googletagmanager.com (1 script tag)
10 checks passed, 3 not applicable
  • OKHTTPS

    All 1 crawled page were served over HTTPS.

  • OKClickjacking protection

    x-frame-options is set on all 1 HTML page.

  • OKMIME sniffing protection

    x-content-type-options is set on all 1 HTML page.

  • OKReferrer policy

    A referrer policy is set through a <meta name="referrer"> tag.

  • OKPermissions policy

    permissions-policy is set on all 1 HTML page.

  • OKSoftware version disclosure

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

  • OKMixed content

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

  • OKForms over HTTPS

    1 form 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.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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 pagespeed.web.dev

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

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

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

Own pagespeed.web.dev?

  • Claim this site to manage the listing, hide it from the public lists, or keep it.
  • Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming pagespeed.web.dev. Removal needs no account and no proof of purchase.