WebToffee vs WP All Import Pro vs Super Speedy Imports
The same WebToffee-format files were run through WebToffee Free 2.6.5, WP All Import Pro 5.0.6 and Super Speedy Imports Pro 2.86.0 on the same four-vCPU server. Super Speedy Imports completed the initial 10,000-product import in 12.950 seconds and the update in 16.450 seconds.
Results for import users
| Operation | WebToffee Free | WP All Import Pro | Super Speedy Imports |
|---|---|---|---|
| Initial import | 886.904 s (14m 46.904s) | 381.098 s (6m 21.098s) | 12.950 s |
| Update | 358.644 s (5m 58.644s) | 538.577 s (8m 58.577s) | 16.450 s |
| Speed versus Super Speedy Imports, initial | 68.487 times slower | 29.428 times slower | Baseline |
| Speed versus Super Speedy Imports, update | 21.802 times slower | 32.740 times slower | Baseline |
There is one important update difference. Super Speedy Imports and WP All Import removed the 1,000 products omitted from the previous import file. WebToffee retained them, so its update completed less work and left 11,000 published products rather than the intended 10,000.
The initial file created 10,000 simple products with descriptions, excerpts, prices, weights, categories, brands and global Colour and Size attributes. The update changed 2,500 existing products, added 1,000 and omitted 1,000 from the previous file. Super Speedy Imports recognised the WebToffee headers automatically, so the exact source files did not need to be reformatted for migration.
Visitor and wp-admin response during each run
| Run | Visitor TTFB avg / max | wp-admin TTFB avg / max | Duration of import load |
|---|---|---|---|
| WebToffee initial | 218.00 / 553.20 ms | 474.26 / 1,513.50 ms | 886.904 s |
| WP All Import initial | 180.33 / 1,013.80 ms | 172.85 / 850.40 ms | 381.098 s |
| Super Speedy Imports initial | 144.53 / 429.50 ms | 293.55 / 1,537.50 ms | 12.950 s |
| WebToffee update | 142.38 / 176.80 ms | 224.31 / 834.10 ms | 358.644 s |
| WP All Import update | 151.42 / 1,019.40 ms | 161.99 / 638.30 ms | 538.577 s |
| Super Speedy Imports update | 127.19 / 341.80 ms | 200.66 / 1,212.80 ms | 16.450 s |
The short Super Speedy Imports windows contain fewer probes, so isolated maximums have a larger effect on their averages. The practical distinction is duration: seconds of import activity instead of several minutes.
Measured server use: initial import
| Importer | CPU avg / max | RAM avg / max | Disk busy avg / max | Baseline-adjusted CPU | Disk busy time | Writes |
|---|---|---|---|---|---|---|
| WebToffee Free | 27.60% / 59.49% | 1,136.9 / 1,298.8 MiB | 6.23% / 35% | 14.2561 vCPU-min | 55.222 s | 473.780 MiB |
| WP All Import Pro | 28.75% / 60.45% | 1,193.2 / 1,324.6 MiB | 15.62% / 41% | 6.5718 vCPU-min | 59.513 s | 626.823 MiB |
| Super Speedy Imports | 42.29% / 74.54% | 1,242.4 / 1,303.7 MiB | 19.43% / 55% | 0.3404 vCPU-min | 2.516 s | 197.129 MiB |
Measured server use: update
| Importer | CPU avg / max | RAM avg / max | Disk busy avg / max | Baseline-adjusted CPU | Disk busy time | Writes |
|---|---|---|---|---|---|---|
| WebToffee Free | 28.10% / 53.98% | 1,146.3 / 1,252.8 MiB | 7.35% / 36% | 5.6931 vCPU-min | 26.344 s | 255.765 MiB |
| WP All Import Pro | 28.55% / 55.30% | 1,235.0 / 1,371.2 MiB | 16.35% / 42% | 9.1564 vCPU-min | 88.071 s | 834.875 MiB |
| Super Speedy Imports | 43.51% / 66.14% | 956.7 / 1,041.0 MiB | 8.82% / 52% | 0.4346 vCPU-min | 1.441 s | 162.782 MiB |
Hosts should judge cumulative CPU and disk consumption, not only the highest percentage shown on a graph. Super Speedy Imports reaches a higher instantaneous CPU rate because it processes the work quickly, but its total CPU and disk use is much lower.
Projected annual impact per hosted domain
This projection assumes one initial import plus 364 daily updates. It is derived from the measured baseline-adjusted runs and is not a direct annual measurement.
| Annual resource | WebToffee Free | WP All Import Pro | Super Speedy Imports |
|---|---|---|---|
| CPU | 34.776 vCPU-hours | 55.659 vCPU-hours | 2.642 vCPU-hours |
| Disk busy | 2.679 hours | 8.921 hours | 0.146 hours |
| Disk writes | 91.379 GiB | 297.384 GiB | 58.056 GiB |
Projected domain capacity
The model below budgets a four-vCPU server to 50% sustained CPU, then combines each domain’s daily import cost with an illustrative amount of ordinary non-import CPU work.
| Ordinary CPU per domain/day | WebToffee domains | WP All Import domains | Super Speedy Imports domains |
|---|---|---|---|
| 10 vCPU-min | 183 | 150 | 276 |
| 20 vCPU-min | 112 | 98 | 140 |
| 40 vCPU-min | 63 | 58 | 71 |
| 80 vCPU-min | 33 | 32 | 35 |
At 20 ordinary vCPU-minutes per domain per day, this model fits 140 daily-import domains with Super Speedy Imports, compared with 112 using WebToffee and 98 using WP All Import. That is 25% more than WebToffee and 42.9% more than WP All Import in this particular CPU model.
Capacity-equivalent hosting cost
For every 1,000 domains running one update daily, the measured CPU difference is equivalent to 1.826 four-vCPU servers versus WebToffee and 3.028 versus WP All Import, using the same 50% CPU budget. At an illustrative €35.49 per server per month, that represents €777.61 per year of capacity versus WebToffee or €1,289.74 versus WP All Import. This is not a guaranteed cash saving: a host may realise it as extra headroom, fewer noisy-neighbour incidents or more domains per box.
Method, versions and reproducibility
- Server: four AMD EPYC-Genoa vCPUs, 8.12 GB RAM and SSD storage.
- Stack: WordPress 7.0.3, WooCommerce 11.0.0, PHP 8.2.33 and MariaDB 10.11.18.
- Importers: WebToffee Free 2.6.5, WP All Import Pro 5.0.6 plus WooCommerce add-on 4.0.6, and Super Speedy Imports Pro 2.86.0.
- WebToffee used a batch size of 100 rather than its smaller default.
- All six runs were recorded, monitored, allowed to complete and passed the deterministic bundle validator.
Download the complete reproduction ZIP. It contains the two exact CSV files, all six scenarios and configurations, environment and software inventories, a guide and checksums. No plugin packages are included. The compact result JSON and readable report are also public.
Absolute timings will vary with hardware, database state and hosting limits. This page reports one controlled scenario. The exact files and configurations are published so the result can be challenged and repeated.

Comments