CrawlCheck

Agent view · Findings · 2026-08-21

Analytics added 650 ms to every request: how we found it

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/our-analytics-was-adding-650ms-to-every-request: 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.

status200
content-typetext/markdown; charset=utf-8
varyAccept
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/our-analytics-was-adding-650ms-to-every-request>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes12,596
words1,787
sha-25600be33c1cca3bd6920d5a399c32024c6b1890b76d888ddd840177be928700e6e
repr-digestsha-256=:AL4zwcyjvWkg1aOZwyAkxrGJC3bYiN3YQBd76ShwDm4=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795311480;expires=1795315080;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="N81PGCM-cI-dBUvjYHAcqA";tag="crawlcheck-page"
signaturesig1=:s5ge1t4eHLTPSR4a9swBHAWDSmEYgg382NBCPX/GeBoHoBnczVs5Q1FiiFktf76CFaQfx9ge8JwzV64LC2+LBw==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3599 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-08-21 · By [VSNARY | Emmanuel Orta](/author)

# Analytics added 650 ms to every request: how we found it

Our own field data said 70% of the homepage's LCP was time to first byte. The server was recording each visit before it started answering. Moving that work after the response cut TTFB to 85 ms.

CrawlCheck's own field data showed that time to first byte was 70% of the homepage's Largest Contentful Paint, about one second, on a page with nothing slow in it. The server recorded each visit for analytics before it started answering, so every response, robots.txt included, waited about 650 ms. Sending the response first and recording the visit afterwards cut TTFB from about 1,014 ms to 85 ms on the homepage. If TTFB is high on simple pages, check what your server waits for before it answers.

On this page

- How did two pages locate it?
- What was wrong?
- What did the fix change?
- How do you check your own server for this?

Field reading, homepage
Largest Contentful Paint 1,440 ms

Time to first byte 1,014 ms

Render delay 427 ms

We added real-visit performance measurement so we could see [field data](/glossary/field-data) for sites the Chrome UX Report will never cover. Its first reading was about our own homepage, and it was not flattering.

| Field reading, homepage | Value |
| --- | --- |
| Largest Contentful Paint | 1,440 ms |
| Time to first byte | 1,014 ms |
| Render delay | 427 ms |

Seventy percent of [LCP](/glossary/lcp) was time to first byte. Nothing on the page was slow; the server had simply not started answering yet. A second of [TTFB](/glossary/ttfb) on a mostly static page is not an image, font or rendering problem. It is the server doing something before it speaks.

## How did two pages locate it? #

Before profiling anything, we compared two trivial responses that sat on opposite sides of the visit-recording step: one served before it ran, one after.

| Response | Work done | TTFB |
| --- | --- | --- |
| Small script, served before recording | serve a static string | 56 ms |
| Small JSON response, served after recording | serve a smaller static object | 700 ms |

The response doing less work took twelve times longer. The only difference was whether it waited for the recording. That is a fixed tax of about 650 ms, and every response but one was paying it.

## What was wrong? #

On every request the server recorded the visit, waited for the recording to complete, and only then worked out what was being asked for. Analytics never needs to finish before a byte is sent. Next to the code was a note explaining why the recording could not be moved. The note was wrong: the means to move it had been available the whole time. A confident wrong note is worse than none, because it tells the next reader not to look.

## What did the fix change? #

| Response | Before | After |
| --- | --- | --- |
| Small JSON response | 720 ms | 60 ms |
| Homepage | about 1,014 ms | 85 ms |

Re-measured a day later, the responses held between 49 ms and 76 ms. Faster is not proof the recording still works, so we sent three test requests and read the visit counter before and after. It went up by exactly three: the visits are still recorded, just no longer while the visitor waits.

## How do you check your own server for this? #

- **Compare a trivial [URL](/glossary/url) with a real page.** Fetch [robots.txt](/glossary/robots-txt) and your homepage with `curl -o /dev/null -s -w "%{time_starttransfer}"` from outside your network. If the tiny file is nearly as slow as the page, something runs on every request before the answer starts.
- **Suspect anything that records visits.** Analytics, logging and security plugins that run before the response are the usual cause of a fixed delay on every URL.
- **Use field data, not one lab run.** A lab score is one sample from one place; see [field data without CrUX](/guides/core-web-vitals-field-data-for-low-traffic-sites-without-crux) and [why one Lighthouse run is not a finding](/blog/one-lighthouse-run-cannot-support-a-finding-225-percent-variance).
- **Re-read the code next to a note that says something is impossible.** The note is a claim, not evidence.

TTFB figures are time to first byte from an ordinary HTTP client with a cache-busting query, taken from outside the network serving the site, before the fix, right after it, and again a day later.

This is one of the corrections CrawlCheck publishes when its own output was wrong. [All of them are listed together](/blog?kind=corrections).

CrawlCheck’s dataset when this page loaded: 582,334 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%2Four-analytics-was-adding-650ms-to-every-request%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-analytics-was-adding-650ms-to-every-request%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=Analytics%20added%20650%20ms%20to%20every%20request%3A%20how%20we%20found%20it)[Email](mailto:?subject=Analytics%20added%20650%20ms%20to%20every%20request%3A%20how%20we%20found%20it&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Four-analytics-was-adding-650ms-to-every-request)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### How was the 650 ms delay found?

By comparing two trivial responses on opposite sides of the visit-recording step. The one doing less work answered twelve times slower, which located a fixed delay without a profiler.

### Why can analytics slow down every page on a site?

If the server records the visit and waits for that to finish before it starts answering, every response pays the wait, including tiny files such as robots.txt. Recording after the response is sent removes it.

### How do I check whether my server has a fixed delay on every request?

Measure time to first byte for a trivial file such as robots.txt and for a real page, from outside your network. If the tiny file is nearly as slow as the page, something runs before every response.

### Did moving the analytics lose any visit data?

No. Three test requests raised the visit counter by exactly three after the fix. The visits are still recorded, just after the response has gone out.

## Related findings

[2026-10-18 How to verify Amazonbot and Amzn-SearchBot by IP address Amazon publishes Amazonbot and Amzn-SearchBot addresses on web pages. How to check a request against them, and how many claims we](/guides/how-to-verify-amazonbot-and-amzn-searchbot)[2026-11-13 Both our SDKs cut a tool list at 300 with no warning CrawlCheck's lockfile and both SDKs fingerprinted only the first 300 tools of an MCP server, unmarked. Fixed 11 November 2026.](/blog/our-sdks-cut-a-tool-list-at-300-with-no-warning)[2026-10-22 Did your SEO fix work? Compare fixed and untouched pages Did a website fix move search traffic? Compare fixed and untouched pages over the same 28 days. Five steps, a spreadsheet layout,](/guides/how-to-tell-if-a-website-fix-moved-traffic-fixed-vs-untouched-pages)

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:** [/](/) · [Listing check](/listing-check) · [SDK](/sdk) · [Certificates](/certificates) · [Site](/video/site) | **Registry:** [videohive.net](/registry/videohive.net) · [Place: San francisco](/registry/place/ca/san-francisco) | **Datasets:** [Mississippi](/datasets/state/mississippi) · [Technologies: Bootstrap](/datasets/technologies/bootstrap) · [Problems: Robots ctype](/datasets/problems/robots-ctype) | **AI crawlers:** [Klaviyoaibot](/ai-crawlers/klaviyoaibot) | **Glossary:** [AI classifiers: Digital presence signals](/glossary/ai-classifiers/digital-presence-signals)

[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/our-analytics-was-adding-650ms-to-every-request.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.