Directory · Web performance and monitoring
WebPageTest — what a crawler receives from webpagetest.org
Website measurement, not a product review. This page records what machine clients received from webpagetest.org. It does not evaluate WebPageTest software, features, pricing or support.
AI assistants are being shown something other than your site.
AI visibility 73/100, measured 2026-10-27 14:35 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can technically reach this site and would struggle to get anything quotable out of it.
Held at D A high-severity finding sets the letter.
5
findings
✗
llms.txt on its host
✗
entity map on its host
8
scans on record since 2026-09-18
The three stages, in the order an engine hits a site
Each stage gates the next: an engine that cannot reach a page never reads it, and one that cannot read it never quotes it.
Stage 1 · 40% of the score
Reach
Can a named answer-engine crawler get your pages at all?
At least one answer engine was refused, challenged or served less than a browser.
- What each crawler getsn/a
- Crawler permissions100
- Machine-file chainn/a
- Speed100
- Server & hosting50
- Internal linksn/a
- Mobilen/a
- exposuren/a
Stage 2 · 30% of the score
Read
Once it has the bytes, can it find the words?
The content is buried in markup, or the files that guide a crawler are missing.
- Page weight & textn/a
- Machine files60
- Sitemapn/a
- Crawl wasten/a
- Accessibility structuren/a
- Image signalsn/a
- Instructions for agentsn/a
- URL namingn/a
- errpagesn/a
Stage 3 · 30% of the score
Quote
Is there a specific fact it can state and attribute?
Not measured on this scan; left out rather than counted as zero.
- Structured datan/a
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signalsn/a
- Linked datan/a
- Quotable contentn/a
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is read, the lowest of the three.
What to fix
5 findings on this site, 3 of them scored serious. Every one is named below; the top one is shown in full, free. What we saw, why each matters, how to fix it and the bytes behind it are what a licence buys — or we implement the whole list for you.
1 High 2 Medium 1 Low 1 Note
1No XML sitemap foundNo sitemap at any conventional path and none declared.HighDeveloper
What we saw
No sitemap at any conventional path and none declared.
Why it matters
Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.
How to fix it
Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.
Developer: a template, theme or application change — a developer touches it
Fix it with a coding agent
Paste into Claude Code, Cursor or Codex, opened on the code that serves this site.
Show prompt
You are working in the codebase (or server/CDN configuration) that serves webpagetest.org. A crawler audit found the problem below. Fix it at the source, keep the change as small as possible, and do not change anything a visitor sees unless the fix requires it. Finding: No XML sitemap found (NO_SITEMAP_FOUND, high severity) Page: https://webpagetest.org/ What was measured: No sitemap at any conventional path and none declared. Why it matters: Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found. How to fix it: Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt. Rule and examples: https://crawlcheck.io/rules/NO_SITEMAP_FOUND Full report (markdown): https://crawlcheck.io/r/qdyvs6t5uw.md When you are done: 1. Tell me which files or settings you changed and why. 2. If the fix is a server, CDN or cache setting you cannot change from the code, say exactly where it is set. 3. After deploying, re-scan at https://crawlcheck.io/?url=webpagetest.org . The fix counts when NO_SITEMAP_FOUND is gone from the new report.
Why this was decided
| Rule | NO_SITEMAP_FOUND · rule pack sv34 · scope core |
|---|---|
| Evaluated | 2026-10-27 14:35:31 UTC |
| Decision | d1:5bf6d6a42bfd8634cd04 · finding f1:a021b19c73df00bba9af resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build c1d5ec39 from EWR · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /sitemap.xml | 404 | 1,727 | 6af64542f82e | already_held |
| read: /sitemap_index.xml | 404 | 1,727 | 6af64542f82e | already_held |
| read: /wp-sitemap.xml | 404 | 1,727 | 6af64542f82e | already_held |
3 more in the manifest.
Artifacts: manifest:2c66d22d99c383b4a51267e0d431c316f11c6b2e64b161bab8286643aa184060
Grade effect Caps the letter at D. Without it the letter would be C (score 73). Moves no points; the score is built from the measured rows.
Rule NO_SITEMAP_FOUND under scoring rules v34 · fingerprint NO_SITEMAP_FOUND|/ · persisting (10 scans)
Verify the fix Re-scan after the change. This finding is cleared when NO_SITEMAP_FOUND is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
NO_SITEMAP_FOUND · full transcript
Open the other 4
What we saw, why it matters, how to fix it, and the evidence bytes for every finding — on this report and every re-scan. From $29 a month.
Unlock the findingsOr have them fixed
We implement the list on your site and re-measure, with a sealed before and after. One site, $100 once.
Get this fixed — $100The main product
We fix the 5 findings on webpagetest.org. $100, once.
3 of them are scored serious. One site. You keep the grade for free — this is the part where the list stops being a list.
- Every finding implemented on the site itself: machine files, schema, NAP, the lot
- An entity map authored for your business, not a template with the name swapped
- Measured again afterwards — the before and the after, sealed, so it is evidenced rather than claimed
- Thirty days of monitoring included
- Work starts within two business days
What it covers · one payment, nothing recurring
What changed
No change recorded between the readings on file yet.
8 scans on record, first 2026-09-18. Score movements are shown only between readings taken under the same score version; finding codes are comparable across all of them.
Is this your site?
This listing reads the public record. Claim it and Watch keeps that record on your terms: every list this page holds back, finding age, and twice-daily re-measurement. Free for 30 days, no card.
Claim the record for webpagetest.orgIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If webpagetest.org is yours you can prove it in a minute and for nothing — a DNS TXT record or one meta tag on the home page, both checkable by anyone.
Claiming marks you as the verified owner and lets you correct the category and the company name. It moves no score, no rank and no position.
Claim this listing — free or ask about a verified profile
Dispute or re-scan
If a reading here is wrong, it is our instrument that is wrong, and we want to know. Tell us what is wrong and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.
By email instead: hello@crawlcheck.io. Category “Web performance and monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.