Scanned sites / pagespeed.web.dev / 2026-09-16-0311
pagespeed.web.dev scan from 9/16/2026, 3:11:33 AM
Scan 2026-09-16-0311
Scanned 9/16/2026, 3:11:33 AM, finished 9/16/2026, 3:13:35 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.
On September 16, 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 issue1 of 1 page have title issues.
- Meta descriptions1 issue1 of 1 page have meta description issues.
- HeadingsOK0 of 1 page have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responsesOK2 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 1 indexable page have indexability warnings.
- Image alt textOK0 of 3 image references have no alt attribute. 1 use an empty alt (decorative), which is fine.
- Heavy assetsOK0 assets larger than 500 KB among the 3 heaviest.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage1 issueNo sitemap found. Tried: https://pagespeed.web.dev/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
- Thin content1 issue1 of 1 page have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1042 sites, median 82%, average 80%
pagespeed.web.dev scores 68%, higher than 9% of the 1042 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsYour site has several issues affecting its SEO health. Key improvements include fixing non-200 responses, enhancing title tags and meta descriptions, and creating a sitemap. These actions will optimize your site's visibility and engagement.
- 1
Fix Non-200 Responses
Why: Two URLs (robots.txt, sitemap.xml) return 404 errors which hinder indexing.
How: Create valid robots.txt and sitemap.xml files. Ensure they are accessible.
Checks: status-codes
- 2
Enhance Title Tag
Why: Title is too short, impacting search visibility.
How: Change the title to be more descriptive and at least 30 characters long.
Checks: titles
- 3
Add Meta Description
Why: Meta description is missing, reducing click-through rates from search results.
How: Write a compelling meta description (150-160 characters) for the homepage.
Checks: meta-descriptions
- 4
Create a Sitemap
Why: No sitemap is present, making it difficult for search engines to index your pages.
How: Generate a sitemap.xml file and ensure it lists all relevant pages.
Checks: sitemap-coverage
- 5
Increase Content Depth
Why: The page has fewer than 200 words, which may affect rankings.
How: Add more informative content to increase total word count above 200.
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 crawlThe site has some important security issues to address, particularly regarding strict transport and content security policies. Implementing the recommended fixes will enhance your website's protection against potential attacks.
- 0 high
- 2 medium
- 1 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted on their first request if they access the site without HTTPS.
Fix: Implement the HTTP header: `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload`.
Evidence: HTTP Strict Transport Security
- 2
Content Security Policy VulnerabilitiesMedium
Why it matters: Allowing 'unsafe-inline' and 'unsafe-eval' reduces the effectiveness of the CSP against script injections.
Fix: Update CSP to disallow inline scripts: `script-src 'self';` without 'unsafe-inline'.
Evidence: Content Security Policy
- 3
Third-party Scripts Lack Subresource IntegrityLow
Why it matters: Without Subresource Integrity, a compromise of third-party scripts can alter site behavior.
Fix: Consider adding CSP entries that restrict known domains, or utilize Subresource Integrity (SRI) for script tags.
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-oefLNvUS51WAljcb-GyzPw' '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.
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.