Performence Test Wordops vs SlickStack

susbtance_D

I recently got hold of a very good annual deal on some decent hardware. I’ll be idling my VPS for a few months since I don’t currently need it — the project I got it for will only be deployed post-summer.

I’ve been using WordOps for a few years now because it made it easy to spin up small projects on the same VPS while hosting a couple of WordPress instances.

For my main business site, I'm still running a single WordPress install — nothing else on the box — but still using WordOps. Lately, I’ve been toying with the idea of ditching WordOps for my main site and switching to SlickStack (SS). However, I haven’t come across any real-world comparisons between the two — just feature tables — and I’m unsure if it’s worth the effort to move to SS.

I did try Webinoly before but ended up moving to WordOps after encountering a paywall around its documentation (at least that’s what I remember).

I’m willing to run some tests on a blank VPS with Ubuntu or Debian — whichever works best.

Any suggestions on what kind of tests I can conduct and report back, other than Lighthouse or GTmetrix?

Thanks!
🙂

marty

There are various tools for load testing to determine a server's ability to cope with a sustained volume of traffic. Not sure it will show much of a difference though as these both use the same stack (Nginx + FastCGI cache). You also need to be wary of comparing like with like - if it's a VPS with shared resource allocation (as most are) rather than a dedicated server then other factors (noisy neighbours, CPU steal time, IO contention) may skew results significantly from one run to the next.

susbtance_D

marty
Fair point. I can see time of the day, neighbours etc skewing the result. I guess multiple test different time of the day can average that out.

I believe, like me many run it on shared resources rather of the bare metal or VDS¿

First test typical lighthouse.
Slickstack defualt install is with its own theme. I changed it to twenty twenty five

Wordops

Performance: 99
First Contentful Paint: 0.4 s
Largest Contentful Paint: 0.4 s
Total Blocking Time: 0 ms
Cumulative Layout Shift: 0.075
Speed Index: 0.5 s

SlickStack (Twenty Twenty Five theme)

Performance: 100
First Contentful Paint: 0.4 s
Largest Contentful Paint: 0.4 s
Total Blocking Time: 0 ms
Cumulative Layout Shift: 0
Speed Index: 0.8 s

SlickStack (Default Theme)

Performance: 81
First Contentful Paint: 1.9 s
Largest Contentful Paint: 1.9 s
Total Blocking Time: 0 ms
Cumulative Layout Shift: 0.01
Speed Index: 1.9 s

I'll run multiple test using ab and wrk every 2 hours or so for 24 hours to get a average the results.

Approach is
My test Vps

#!/bin/bash
date > top_log.txt
top -b -d 1 -n 30 > top_log.txt &

My other VPS (Different Country, 21ms is avg ping)

#!/bin/bash
date
wrk -t4 -c100 -d30s http://test.com/

I'll be running these test next weekend as I have some time in hand. If you guys think the process or approach can be changed, I'll be glad to adapt, modify or add to it.

Benchmark test system (nothing extraordinary but good enough in my opinion for my use case of like max 20 API calls a day and a private dashboard which I'll be deploying post summer)

Basic System Information:

Uptime : 1 days, 17 hours, 43 minutes
Processor : Intel(R) Xeon(R) Gold 6122 CPU @ 1.80GHz
CPU cores : 2 @ 1795.781 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 7.7 GiB
Swap : 1024.0 MiB
Disk : 77.4 GiB
Distro : Ubuntu 24.04.2 LTS
Kernel : 6.8.0-60-generic
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online

IPv6 Network Information:

Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 133.40 MB/s (33.3k) | 1.06 GB/s (16.6k)
Write | 133.75 MB/s (33.4k) | 1.07 GB/s (16.7k)
Total | 267.15 MB/s (66.7k) | 2.13 GB/s (33.4k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.09 GB/s (2.1k) | 1.06 GB/s (1.0k)
Write | 1.15 GB/s (2.2k) | 1.13 GB/s (1.1k)
Total | 2.25 GB/s (4.3k) | 2.20 GB/s (2.1k)

iperf3 Network Speed Tests (IPv4):

Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 6.69 Gbits/sec | 3.66 Gbits/sec | 7.12 ms
Eranium | Amsterdam, NL (100G) | 7.18 Gbits/sec | 4.58 Gbits/sec | 0.538 ms
Uztelecom | Tashkent, UZ (10G) | 1.93 Gbits/sec | 2.08 Gbits/sec | 97.6 ms
Leaseweb | Singapore, SG (10G) | 992 Mbits/sec | 1.07 Gbits/sec | 164 ms
Clouvider | Los Angeles, CA, US (10G) | 1.15 Gbits/sec | 672 Mbits/sec | 153 ms
Leaseweb | NYC, NY, US (10G) | 2.25 Gbits/sec | 2.12 Gbits/sec | 80.1 ms
Edgoo | Sao Paulo, BR (1G) | 938 Mbits/sec | 487 Mbits/sec | 189 ms

iperf3 Network Speed Tests (IPv6):

Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 6.51 Gbits/sec | 5.31 Gbits/sec | 7.16 ms
Eranium | Amsterdam, NL (100G) | 6.79 Gbits/sec | 7.14 Gbits/sec | 0.589 ms
Uztelecom | Tashkent, UZ (10G) | 1.92 Gbits/sec | 2.23 Gbits/sec | 97.5 ms
Leaseweb | Singapore, SG (10G) | 977 Mbits/sec | 1.34 Gbits/sec | 164 ms
Clouvider | Los Angeles, CA, US (10G) | 1.18 Gbits/sec | 1.16 Gbits/sec | 153 ms
Leaseweb | NYC, NY, US (10G) | 2.82 Gbits/sec | 2.64 Gbits/sec | 78.3 ms
Edgoo | Sao Paulo, BR (1G) | 1.03 Gbits/sec | 910 Mbits/sec | 189 ms

Geekbench 6 Benchmark Test: