Super Speedy Imports vs WebToffee Free
In the deterministic repeat, Super Speedy Imports Pro 2.86.0 imported the same 10,000-row WebToffee-format CSV 68.487 times faster than WebToffee Free 2.6.5. The matching update was 21.802 times faster, while Super Speedy Imports also removed the 1,000 products omitted from the previous import file and WebToffee retained them.
Results for store owners
| Operation | WebToffee Free | Super Speedy Imports | Difference |
|---|---|---|---|
| Initial 10,000-product import | 886.904 s | 12.950 s | 68.487 times faster |
| 10,000-row update | 358.644 s | 16.450 s | 21.802 times faster |
The same files were used byte for byte. Super Speedy Imports recognised the WebToffee headers automatically, which is the important migration point: existing WebToffee CSV feeds do not need to be rebuilt.
Correctness difference on the update
Both plugins changed the intended 2,500 products and added 1,000. Super Speedy Imports removed the 1,000 omitted originals and finished with 10,000 published products. The recorded WebToffee configuration retained those products and finished with 11,000. The WebToffee timing therefore represents less update work.
Measured server impact
| Run | CPU avg / max | RAM avg / max | Disk busy avg / max | Cumulative CPU | Cumulative disk busy | Cumulative writes |
|---|---|---|---|---|---|---|
| WebToffee initial | 27.60% / 59.49% | 1,136.9 / 1,298.8 MiB | 6.23% / 35% | 14.2561 vCPU-min | 55.222 s | 473.780 MiB |
| Super Speedy Imports initial | 42.29% / 74.54% | 1,242.4 / 1,303.7 MiB | 19.43% / 55% | 0.3404 vCPU-min | 2.516 s | 197.129 MiB |
| WebToffee update | 28.10% / 53.98% | 1,146.3 / 1,252.8 MiB | 7.35% / 36% | 5.6931 vCPU-min | 26.344 s | 255.765 MiB |
| Super Speedy Imports update | 43.51% / 66.14% | 956.7 / 1,041.0 MiB | 8.82% / 52% | 0.4346 vCPU-min | 1.441 s | 162.782 MiB |
Page response during the import
| Run | Audience | Before avg | During avg / max | After avg |
|---|---|---|---|---|
| WebToffee initial | Visitor | 148.52 ms | 218.00 / 553.20 ms | 165.10 ms |
| Super Speedy Imports initial | Visitor | 120.26 ms | 144.53 / 429.50 ms | 106.24 ms |
| WebToffee initial | wp-admin | 149.28 ms | 474.26 / 1,513.50 ms | 184.46 ms |
| Super Speedy Imports initial | wp-admin | 130.76 ms | 293.55 / 1,537.50 ms | 153.46 ms |
| WebToffee update | Visitor | 151.82 ms | 142.38 / 176.80 ms | 153.20 ms |
| Super Speedy Imports update | Visitor | 138.32 ms | 127.19 / 341.80 ms | 125.12 ms |
| WebToffee update | wp-admin | 166.44 ms | 224.31 / 834.10 ms | 164.00 ms |
| Super Speedy Imports update | wp-admin | 131.58 ms | 200.66 / 1,212.80 ms | 129.64 ms |
The Super Speedy Imports windows contain fewer samples because the jobs finish in seconds. The largest benefit is that the period of import load is much shorter.
Managed-host projection
For one initial import plus 364 daily updates, the measured runs project to 34.776 vCPU-hours, 2.679 disk-busy hours and 91.379 GiB of writes per WebToffee domain per year. Super Speedy Imports projects to 2.642 vCPU-hours, 0.146 disk-busy hours and 58.056 GiB of writes.
Across 1,000 daily-import domains, the CPU difference is equivalent to 1.826 four-vCPU servers under a 50% sustained CPU budget. At an illustrative €35.49 per server per month, that is €64.80 per month or €777.61 per year of capacity. This is a projection, not a guaranteed cash saving.
Environment and reproducibility
The runs used the same four-vCPU, 8.12 GB server with WordPress 7.0.3, WooCommerce 11.0.0, PHP 8.2.33 and MariaDB 10.11.18. WebToffee used a batch size of 100 rather than its smaller default. Images were excluded so the benchmark isolates CSV processing and WooCommerce data writes.
Download the complete reproduction ZIP, inspect the compact result JSON, or read the data report.
Detailed run pages
- WebToffee initial import
- WebToffee update
- Super Speedy Imports initial import
- Super Speedy Imports update
For all three importers, see WebToffee vs WP All Import Pro vs Super Speedy Imports.
Comments