· Fetching
A plain fetch against a rendered one
29 documentation, news and store product pages, plus 10 pages picked by hand
- pages where the plain fetch returned at least 90% of the browser's words
- 26 of 29
- pages where the plain fetch returned at least 90% of the browser's words
- median cost per 1,000 requests, plain and rendered
- $0.36 and $1.40
- median cost per 1,000 requests, plain and rendered
- median wall time at the client, plain and rendered
- 1.5 s and 10.0 s
- median wall time at the client, plain and rendered
- hand-picked pages where the plain fetch returned under half the words
- 8 of 10
- hand-picked pages where the plain fetch returned under half the words
Run of 2026-11-16.
Each page went to /scrape once as a plain HTTP fetch and once rendered in a browser, with markdown output and four requests in flight. Words are the markdown split on whitespace, and a page counts when both requests answered 200. Cost is the costs.total_cost field of the response. The 10 extra pages were chosen because we expected them to need a browser, so they say nothing about how common such pages are.
Source: How web scraping works: what a plain fetch gets and misses.