Scanned sites / pagespeed.web.dev / 2026-09-19-0315

pagespeed.web.dev scan from 9/19/2026, 3:15:27 AM

Scan 2026-09-19-0315

Scanned 9/19/2026, 3:15:27 AM, finished 9/19/2026, 3:16:29 AM. 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 19, 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 14 checks found something to fix, led by title tags (1), meta descriptions (1), sitemap coverage (1); 10 checks passed. 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 14
  • Title tags1 issue
    1 of 1 page have title issues.
  • Meta descriptions1 issue
    1 of 1 page have meta description issues.
  • HeadingsOK
    0 of 1 page have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    2 URLs did not return a 2xx response.
  • 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 the 3 heaviest.
  • 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.
  • Thin content1 issue
    1 of 1 page have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1098 sites, median 82%, average 80%

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

028560%: 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%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 0 sites49%: 0 sites50%: 3 sites51%: 4 sites52%: 1 site53%: 1 site54%: 2 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 6 sites59%: 3 sites60%: 5 sites61%: 8 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 9 sites66%: 7 sites67%: 15 sites68%: 27 sites69%: 12 sites70%: 23 sites71%: 22 sites72%: 24 sites73%: 24 sites74%: 30 sites75%: 26 sites76%: 38 sites77%: 37 sites78%: 34 sites79%: 33 sites80%: 44 sites81%: 53 sites82%: 49 sites83%: 45 sites84%: 55 sites85%: 47 sites86%: 47 sites87%: 47 sites88%: 56 sites89%: 38 sites90%: 51 sites91%: 38 sites92%: 25 sites93%: 17 sites94%: 16 sites95%: 8 sites96%: 10 sites97%: 4 sites98%: 2 sites99%: 1 site100%: 12 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 important issues to address, including non-200 responses, missing title tags, meta descriptions, and a sitemap. These changes can enhance visibility and SEO performance significantly.

  1. 1

    Fix Non-200 Responses

    Why: Non-200 responses (404 errors) can harm user experience and SEO.

    How: Create the missing files: robots.txt and sitemap.xml to prevent 404 errors.

    Checks: status-codes

  2. 2

    Add Title Tag

    Why: A descriptive title enhances click-through rates and improves SEO.

    How: Update the title tag to something more descriptive (at least 30 characters).

    Checks: titles

  3. 3

    Create Meta Description

    Why: Meta descriptions encourage users to click and can boost search rankings.

    How: Add a compelling meta description (between 50-160 characters).

    Checks: meta-descriptions

  4. 4

    Implement Sitemap

    Why: A sitemap helps search engines better understand your site structure.

    How: Create a sitemap.xml and list it in your robots.txt file.

    Checks: sitemap-coverage

  5. 5

    Improve Page Content

    Why: More content enhances SEO and user engagement.

    How: Add more detailed content to exceed 200 words.

    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

The website has several security issues that need addressing. Primarily, the absence of HTTP Strict Transport Security (HSTS) can expose users to man-in-the-middle attacks. Additionally, the Content-Security-Policy allows potential vulnerabilities through the use of inline scripts. Third-party scripts lack Subresource Integrity (SRI), which poses risks if those scripts are compromised.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted on their first request if they type the URL without 'https://'.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Weak Content Security Policy (CSP)Medium

    Why it matters: The CSP allows 'unsafe-inline' scripts, reducing protection against XSS attacks and script injection.

    Fix: Update the CSP to disallow 'unsafe-inline' and 'unsafe-eval', and use strict sources instead.

    Evidence: Content Security Policy

  3. 3

    Third-party Scripts Without Subresource Integrity (SRI)Low

    Why it matters: These scripts can be altered by an attacker, exposing the site to malicious code execution.

    Fix: Add Subresource Integrity (SRI) to the scripts from 'www.gstatic.com' and 'www.googletagmanager.com' if supported. Alternatively, adjust CSP to restrict or approve these domains.

    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/ → script-src 'report-sample' 'nonce-UsUEyTEh5Jir2Fnd6IWwtw' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/PagespeedUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /_/PagespeedUi/cspreport
  • 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.

This report was produced by the DIY SEO Hub Site Spider crawling pagespeed.web.dev from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.

pagespeed.web.dev scan 2026-09-19-0315 | DIY SEO Hub