Webfold
Menu

Benchmark · Directional

Footprint of a scrape or crawl

One Webfold scrape took 90 ms with 14.9 MB of peak memory. A local 50-page crawl ran about 11.7 times faster than Crawl4AI 0.9.3. That is 90.6 against 8.2 documents a second. Both figures are directional.

Memory for one scrape. Speed on a local crawl against Crawl4AI.

Last updated , the newest measurement or check on record for this page.

Run: 20 September 2026 and 15 September 2026

What question does this benchmark ask?

How light is Webfold to run? How does it compare with a Python crawler on a local test?

How was it run?

  • Single scrape and headless run: one 16-core Linux host, directional.
  • Local HTTP crawl: 5 repeats of 50 pages against Crawl4AI 0.9.3, no network involved.

What are the results?

Peak memory, megabytesShorter is better
Idle headless instance
5.5 MB
One-shot headless run
7.1 MB
Single scrape
14.9 MB
Local crawl, documents per secondLonger is better
Webfold
90.6
Crawl4AI 0.9.3
8.2
MeasurementResult
Single scrape, peak memory14.9 MB
Single scrape, wall time90 ms
One-shot headless run, peak memory7.1 MB
Idle headless instanceabout 5.5 MB
Local crawl vs Crawl4AI, paired medianabout 11.7 times faster
Local crawl memory, sampled27,284 KiB vs 120,124 KiB

Webfold is small enough to run beside an application or in a short-lived job.

What does this not show?

Know the limits

  • Directional: one host, not a standard instance, and a marker-smoke check for quality in the crawl comparison.
  • These figures do not cover coverage, cost or whole-service latency.

Source: webfold-bench: bench/measured-2026-09-20.md and bench/competitive/RESULTS.md

Which other benchmarks are there?

Check it on your own pages.

Run the command-line tool on your content.

Join the waitlistRead the quickstart