Agent view · Findings · 2026-11-18
The quote form was the slow part: 980 ms cut to 50 ms
This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/the-quote-form-was-the-slow-part-980-ms-to-50: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.
| status | 200 |
|---|---|
| content-type | text/markdown; charset=utf-8 |
| vary | Accept |
| link | <https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/the-quote-form-was-the-slow-part-980-ms-to-50>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory" |
| cache-control | public, max-age=900, stale-while-revalidate=2400 |
| bytes | 12,831 |
| words | 1,954 |
| sha-256 | 279cc1fa693c78ecd0c6be8bdc5c237ca67f4929d6bd6723c07de2d4aeb8a7c5 |
| repr-digest | sha-256=:J5zB+mk8eOzQxr6L3FwjfKZ/SSnWvWcjwH3i1K64p8U=: ← matches the body shown |
| signature-input | sig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795181431;expires=1795185031;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="oXWn_UqOsrMILuwktZRXEg";tag="crawlcheck-page" |
| signature | sig1=:z6r28GMz8us/JG4KtZCOoDNDJrB5wFUMiCz0vounIustY5DZg8Zx/Q3tyYx4ZmhKyUOPR8RJ2MEyjY0Re/FAAQ==: |
| verified | yes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba |
Findings · 2026-11-18 · By [VSNARY | Emmanuel Orta](/author) # The quote form was the slow part: 980 ms cut to 50 ms A tree service home page froze for almost a second while it loaded. We blamed our own scripts first. Google's test showed the quote form was doing it. On a tree service site we run, Google's PageSpeed test measured 980 ms of blocking time on the home page: the page was on screen but could not respond. 16 of the 18 slow tasks in Google's report came from the third-party quote form and the captcha it loads, not from the site's own code. Loading the form when a visitor first touches, scrolls or types, instead of 1.5 seconds after the page opens, cut the reading to 50 ms. On this page - What was wrong - Our first fix was aimed at the wrong thing - What Google's report actually said - The fix: load the form when someone shows up for it - The result - How to check your own site - What this does not show ## What was wrong # The home page of a tree service site we run looked finished within a couple of seconds, but for almost a full second it could not react to a tap. Google's PageSpeed test calls this Total Blocking Time and wants it under 200 ms. The page measured 980 ms. Blocking time is not about how long a page takes to appear. It is the time the browser is too busy running scripts to respond. On a phone, that is the moment someone taps Call and nothing happens. ## Our first fix was aimed at the wrong thing # We assumed the site's own scripts were the cause, so we trimmed them: the script file the home page loads went from 434 KB to 106 KB. On our own test machine the blocking time fell from 480 ms to 175 ms. That looked like a win. Google's test did not move. It still read 980 ms. The difference was the machine. Google's test simulates a mid-range phone. Our test ran on a fast computer, which gets through the same scripts so quickly that the slow ones barely show. **A speed test on a fast machine can hide the problem your visitors have.** ## What Google's report actually said # PageSpeed lists every long task and the script behind it. We read that list instead of guessing: | Long tasks on the home page | Count | | --- | --- | | Total | 18 | | From the quote form and the captcha it loads | 16 | | From everything else on the page | 2 | The quote form is a third-party widget. It loads its own scripts, and those load a captcha. Together they were doing nearly all of the blocking, on a form that sits below the first screen on both phone and desktop. Visitors were paying for it before they could see it. ## The fix: load the form when someone shows up for it # The form used to start loading 1.5 seconds after the page opened, for every visitor. Now it starts when the visitor first touches the screen, scrolls, presses a key or moves the mouse. If none of that happens, it loads on its own after 15 seconds. Nothing visible changed. The form is below the first screen, and it is ready about a second after the first touch or scroll, which is before anyone can reach it. ## The result # | Site | Measured by | Before | After | | --- | --- | --- | --- | | Tree service home page | Google PageSpeed, blocking time | 980 ms | 50 ms | | Tree service home page | Google PageSpeed, largest content paint | not recorded | 2.2 s | | Fencing home page, same form | CrawlCheck lab reading, blocking time | 1.26 s | 289 ms | The fencing site is better and not finished: 289 ms is still above the 200 ms mark, and we have not yet read Google's task list for that page. We are not calling it fixed. ## How to check your own site # - Run your home page through Google's PageSpeed test on the mobile setting. Read the number from that test, not from a test on your own computer. - Open the long-task list and the third-party section. Each row names the script responsible. - For every outside widget in that list — a form, a chat box, a map, a review feed — ask where it sits on the page. If it is below the first screen, it does not need to load before the visitor moves. - Load it on first touch or scroll, with a timer as a fallback. Then run the same test again. A slow image is the other common cause, and it shows up differently. We wrote up one of those in [a slider that took 8 seconds](/blog/a-slider-that-took-8-seconds-three-328-kb-pngs). ## What this does not show # - Real visitors. These are lab readings. The numbers from actual visits are a rolling 28-day average and will take weeks to reflect the change. - More leads. We verified the form still loads and still submits. We have not measured whether more people fill it in. - That every form is slow. This was one widget on two sites. Read your own task list. *Published by CrawlCheck. Both sites are run by the person who builds CrawlCheck.* CrawlCheck’s dataset when this page loaded: 570,959 sites measured. Written by [Emmanuel Orta](/author) · VSNARY I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post. [Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta) Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-quote-form-was-the-slow-part-980-ms-to-50%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-quote-form-was-the-slow-part-980-ms-to-50%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=The%20quote%20form%20was%20the%20slow%20part%3A%20980%20ms%20cut%20to%2050%20ms)[Email](mailto:?subject=The%20quote%20form%20was%20the%20slow%20part%3A%20980%20ms%20cut%20to%2050%20ms&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fthe-quote-form-was-the-slow-part-980-ms-to-50)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta) ## Questions this post answers ### What is Total Blocking Time? The time during loading when the browser is too busy running scripts to respond to a tap or click. Google's PageSpeed test treats 200 ms or less as good on mobile. ### Why did our own test show a better number than Google's? Our test ran on a fast computer. Google's test simulates a mid-range phone, where the same scripts take much longer. The phone number is the one visitors feel. ### Does delaying a form lose leads? The form here sits below the first screen and is ready about one second after the first touch or scroll. We verified it still loads and submits. We have not measured a change in lead volume. ### What if the visitor never touches the page? The form loads on its own after 15 seconds, so it is always there for someone who waits. ### Can I do this with any third-party widget? Any widget below the first screen can wait for the first touch or scroll: forms, chat boxes, maps and review feeds. Something visible at the top of the page should not be delayed this way. ## Related findings [2026-11-13 A slider that took 8.8 seconds: three 328 KB PNGs A home page slider took 8.8 s to paint in a lab test. Three fixes brought it to 2.1 s: show the first slide early, unchain fonts,](/blog/a-slider-that-took-8-seconds-three-328-kb-pngs)[2026-09-23 Correction: the owner's own scans came back locked The site owner's scans came back locked while the report page opened in full. What was wrong, what changed, and how to test gated](/blog/the-owner-could-not-read-his-own-scans)[2026-10-08 Can an AI agent use your contact form? A two-minute test Five checks in a private window show whether an AI agent can finish your quote form: overlays, the form in the page, field labels](/guides/can-an-ai-agent-use-your-contact-form) The main product Found this on your own site? **We fix it for $100.** Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after. [Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v) [What it covers](/pricing#fix) · [scan first, it is free](/) Free browser extension Check this on any site you open, **without leaving the page.** CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account. [Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post) [What it does](/extension) Write for the library Measured something yourself? **Submit an article.** Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published. [Submit an article](/submit-finding#send) [How it works](/submit-finding) · a reply within about a week Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections). ## Comments Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*. Send for review Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan. [All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy) We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io) #### How we measure, and our own machine files CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io). **Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing. **Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours. **Pages:** [Keys](/keys) · [/](/) · [Listing check](/listing-check) · [SDK](/sdk) | **Glossary:** [AI classifiers: Sourcing](/glossary/ai-classifiers/sourcing) · [CAWG training and data mining assertion](/glossary/cawg-training-assertion) · [Video sitemap](/glossary/video-sitemap) · [Heading hierarchy](/glossary/heading-hierarchy) · [Content binding](/glossary/content-binding) · [variableMeasured](/glossary/variable-measured) | **Directory:** [Yugabyte](/directory/yugabyte) | **Registry:** [casalemedia.com](/registry/casalemedia.com) [Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)
Same body as a file: /blog/the-quote-form-was-the-slow-part-980-ms-to-50.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.