Scanned sites / pagespeed.web.dev / 2026-09-28-0329
pagespeed.web.dev scan from 2026-09-28 03:29:07 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-28-0329
Scanned 2026-09-28 03:29:07 UTC, finished 2026-09-28 03:29:32 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.
On September 28, 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
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 issue1 of 1 page have title issues.−10 points
- Meta descriptions1 issue1 of 1 page have meta description issues.−8 points
- HeadingsOK0 of 1 page have heading issues.
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites2 noted0 destinations answered with an error, 2 could not be determined (timeouts, rate limits or refusals), of 18 destinations checked.
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responses2 noted2 URLs did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
- 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 3 fetched assets.
- 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.−6 points
- Internal link countsOKInternal link counts for 1 page; none is a dead end or buried.
- Thin content1 issue1 of 1 page have fewer than 200 words.−8 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL formatOKAll 1 page URL are plain lowercase addresses without parameters.
- CanonicalsOK0 of 1 page have a canonical worth checking.
- Robots directivesOKNo page carries a robots directive; all 1 page are open to search engines.
- Anchor textOKEvery internal link has descriptive, followed anchor text.
- Title and heading structure1 noted1 of 1 page could use the title, heading and snippet space better.
- Image weight and alt lengthOKNo image is over 100 KB or carries alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- hreflangNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Structured dataNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Near duplicatesNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Soft 404sOKNone of 1 page answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positionsNot checkedNot checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
- PaginationNot checkedNot checked: this scan was crawled before this check existed. Scan the site again to run it.
- Headers and cookiesOK0 cookies set by the site; 11 response headers recorded across 4 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 1 page; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- SpellingNot checkedNot 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.
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 findingsWritten from an earlier version of the analysis (rules v4). 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 site needs several crucial fixes to improve its SEO health. Focus on the priority issues identified to enhance visibility and content quality.
- 1
Create a Sitemap
Why: A sitemap improves indexing and helps search engines navigate your site.
How: Create a sitemap at /sitemap.xml and list it in robots.txt. Use an online generator if needed.
Checks: sitemap-coverage
- 2
Add a Meta Description
Why: Meta descriptions improve click-through rates by providing concise summaries in search results.
How: Write a compelling meta description (150-160 characters) that includes relevant keywords.
Checks: meta-descriptions
- 3
Revise Title Tag
Why: A proper title tag improves search rankings and relevance.
How: Adjust the title tag to be at least 30 characters and include primary keywords.
Checks: titles
- 4
Enhance Content Length
Why: Thin content can affect search rankings and user engagement.
How: Expand page content to exceed 200 words, adding relevant information or insights.
Checks: thin-content
- 5
Fix Non-200 Responses
Why: Non-200 responses can hinder crawling and indexing.
How: Ensure the URLs returning 404 errors are corrected or removed from your site.
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 crawlThe website has some important security issues that need attention, including missing HTTP Strict Transport Security (HSTS) and a Content Security Policy (CSP) that is too lenient. Addressing these vulnerabilities will enhance the site's defenses against various attacks.
- 0 high
- 2 medium
- 1 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors may be intercepted when accessing the site without 'https://'.
Fix: Implement HSTS by adding the header: 'Strict-Transport-Security: max-age=31536000; includeSubDomains'.
Evidence: HTTP Strict Transport Security
- 2
Insecure Content Security Policy (CSP)Medium
Why it matters: The CSP allows inline scripts, reducing its effectiveness against injected scripts.
Fix: Update the CSP to remove 'unsafe-inline' and 'unsafe-eval', ensuring a stricter policy.
Evidence: Content Security Policy
- 3
Third-party scripts without Subresource IntegrityLow
Why it matters: Scripts from external domains could be compromised, allowing malicious code to run.
Fix: Use Subresource Integrity (SRI) for scripts from 'www.gstatic.com' and 'www.googletagmanager.com' or configure a CSP that restricts their usage.
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-_BLssKB2kafB2pDi3R4foA' '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.
- lovethework.localsloveus.comDR 6669/100 · rank 1877 · 226 pages
- spokanevalleychamber.orgDR 4669/100 · rank 1877 · 749 pages
- vetshield.caDR 069/100 · rank 1877 · 16 pages
- www.kcphysiotherapy.comDR 968/100 · rank 1922 · 87 pages
- unitar.orgDR 7868/100 · rank 1922 · 2,089 pages
- dac.siggraph.orgDR 8068/100 · rank 1922 · 1,571 pages
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.