Scanned sites / pagespeed.web.dev / 2026-11-06-0442

pagespeed.web.dev scan from 2026-11-06 04:42:38 UTC DR 92

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

Scan 2026-11-06-0442

Scanned 2026-11-06 04:42:38 UTC, finished 2026-11-06 04:43:23 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 November 6, 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 33 checks found something to fix, led by title tags (1), meta descriptions (1), thin content (1); 25 checks passed. Most of the points went to title tags (−10), meta descriptions (−8), thin content (−8). 4 checks found something the score does not count, listed as noted. 4 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 33
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 sites2 noted
    0 destinations answered with an error, 2 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 validation1 noted
    1 of 1 page have HTML problems: 1 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    No page carries structured data (1 indexable page checked).
  • Near duplicatesOK
    No near duplicates among 0 pages with enough text to compare.
  • 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 positionsOK
    0 of 0 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • 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.
  • SpellingOK
    No unfamiliar lower-case words on 1 page (English pages only).

Where this scan sits among all scanned sites

2873 sites, median 80%, average 79%

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

0751500%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 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%: 0 sites34%: 0 sites35%: 2 sites36%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 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

Your site has several key issues including a missing sitemap, title and meta description problems, and thin content. Addressing these can improve your site's health score and visibility.

  1. 1

    Create a Sitemap

    Why: A sitemap helps search engines discover your content.

    How: Create a sitemap for your site and make it available at /sitemap.xml.

    Evidence: One URL: no sitemap found.

    1 page affected

    Checks: sitemap-coverage

  2. 2

    Fix Title Tag

    Why: A descriptive title improves user experience and search rankings.

    How: Revise the title to be descriptive and longer than 30 characters.

    Checks: titles

  3. 3

    Add a Meta Description

    Why: Meta descriptions can increase click-through rates from search results.

    How: Write a concise meta description that summarizes your page's content.

    Evidence: One page has no meta description at all.

    1 page affected

    Checks: meta-descriptions

  4. 4

    Improve Page Content

    Why: More content can improve SEO rankings and user engagement.

    How: Add more relevant content to surpass 200 words.

    Checks: thin-content

  5. 5

    Check Non-200 Responses

    Why: Addressing errors improves site reliability and user trust.

    How: Investigate and fix non-200 responses from your assets if necessary.

    Checks: status-codes

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 site has a few important security issues that need addressing. It lacks an HTTP Strict Transport Security header, which can lead to interception of traffic. Additionally, its Content Security Policy is too permissive, allowing inline scripts, and there are unprotected third-party scripts. Fixing these issues will enhance security significantly.

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

    Missing HTTP Strict Transport Security (HSTS) HeaderMedium

    Why it matters: Without HSTS, users typing the site address may be intercepted on initial connections.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Weak Content Security PolicyMedium

    Why it matters: The current CSP allows inline scripts, which reduces its effectiveness against script injection attacks.

    Fix: Update the CSP to disallow 'unsafe-inline' and 'unsafe-eval' by revising the `script-src` directive.

    Evidence: Content Security Policy

  3. 3

    Third-party Scripts Lack Subresource IntegrityLow

    Why it matters: Scripts from external domains can change if those services are compromised, potentially affecting your site.

    Fix: Implement Subresource Integrity (SRI) by adding a hash to the script tags from www.gstatic.com and www.googletagmanager.com.

    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-pQ6_6Q6Egqxr5xwiA4BsDA' '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.