What it measures
The test measures the time required to create two small PDFs, serialize them, load them again, copy their pages into one new PDF, and serialize the merged output. That is a local browser workload similar to a simple merge, not a complete performance profile.
Run a local browser test
This creates two small six-page PDFs, merges them in this tab, and reports the elapsed browser time. No document is selected, uploaded, or sent to a server.
Results vary with browser, device load, memory, and file shape. This is a repeatable local workload, not a vendor-versus-vendor speed claim.
Methodology
- Generate two six-page documents with short text on each page.
- Serialize both documents in the browser.
- Load the generated bytes and copy all twelve pages into a new document.
- Serialize the merged document and report elapsed time, output size, and page count.
How to interpret the result
Use the number to compare repeated runs on the same device, browser, and power state. Do not compare it directly with a cloud provider’s marketing number: the workloads, hardware, network, queue, and measurement boundaries are different.
Limitations
- It uses generated text pages, not your real PDFs.
- It does not measure upload or download time.
- It does not test OCR, image-heavy scans, passwords, forms, annotations, or conversions.
- It does not prove that every tool or every operation is local.
For a meaningful workflow test
Use a copy of a representative file, record the browser and device, run the same task more than once, and inspect the output. Never use a public benchmark as a substitute for the privacy, retention, security, or compliance requirements of your organization.
People also ask
Common questions
Does the benchmark upload my PDF?
No. It generates test PDFs in the browser and merges them in the same tab. It does not ask you to choose a document.
Does a faster result prove a tool is better?
No. The result only describes this small generated workload on this device at this moment. Correctness, privacy, format support, and output quality also matter.
Why can my result change between runs?
Browser tabs, device temperature, available memory, power mode, and background work can all affect elapsed time.
Can I use this to size a production workflow?
Use it as a baseline only. Test representative files, including scans, forms, annotations, and large images, before making an operational decision.