The new Gold standard of high performance WordPress hosting
Some preface: FlyingHost is built by the team behind FlyingPress, which is included at no extra cost, and builds on what FlyingCDN was, also included. The driving force behind FlyingPress is Gijo Varghese, someone I consider among the very best in WordPress performance optimization. I’ve followed his work since the earliest Flying plugins, discussed plenty of ideas with him over the years, and I’m proud to call him a friend.
TLDR: Give FlyingHost a try. I genuinely don’t think you’ll be disappointed.
The long praise follows;
I was invited to test FlyingHost in early June and immediately jumped at the opportunity.
I started with two small domains, comparing FlyingHost directly against my own optimized VPS setup using Redis, HTTP/3, Nginx and PHP-FPM. Despite being relatively small sites, they use custom paths, constants and React/Vue-based backend functionality.
I thought my VPS performed well. It did. FlyingHost simply performed way better.
That convinced me to test something heavier: a WooCommerce installation with several thousand products, lots of custom development code and Elementor. On our shared hosting environment at work, tasks like bulk operations and admin-ajax add-to-cart requests struggled. FlyingHost simply handled them.
Admin-ajax requests were around 100–200ms, WooCommerce product listings loaded in roughly a second, and Elementor opened in around 1–1.5 seconds. This was without Redis object caching or extensive optimization.
Naturally, results will vary between websites, but I already knew FlyingHost was something special.
I even demonstrated it at the agency where I work. The reaction was basically: once pricing is confirmed and the service leaves beta, we may start replacing some of our higher-end hosting setups and custom VPS configurations.
Then came the real test.
I moved my main site: a 70+GB WordPress installation with 10 custom post types, 60,000+ published items, 42,000 drafts, 48,000 published comments and a roughly 12GB database. It also runs WPML, SearchWP, FacetWP and a huge amount of custom configuration and code.
There were a few small migration issues, but the FlyingHost team helped resolve them. About two days later, I moved it into production and cancelled the VPS that previously hosted all three sites.
What makes this even more impressive is how much FlyingHost has improved since that initial test.
FlyingPress is now included. Flyingpress now support Redis Object Caching out of the box FlyingHost. Pricing turned out to be excellent. Their Cockpit control panel gained useful resource insights, integrated Patchstack security with virtual patching, flexible backups that do not count towards your storage allowance and also incredibly fast manual backups.
You also get a browser-based SSH terminal, while every site runs inside its own fully isolated container. SSH/SFTP, phpMyAdmin and multiple PHP versions are available, logs are refreshingly straightforward, and connecting domains is easy.
The Cockpit itself sums up the philosophy nicely: clear, intuitive and without unnecessary clutter.
I genuinely haven’t been this impressed by WordPress backend performance in a long time.
FlyingHost has the potential to become a new benchmark for what managed high-end WordPress hosting should feel like.
In my FlyingPress review (also here on Trustpilot) back in April 2024, I wrote:
“I will always vouch for Gijo and the FlyingWeb team.”
Now, in August 2026, I stand behind that statement even more strongly.
Gijo and team: thank you for everything you do. I will always be right there with you all.
PS: I was invited to the private trial and received credits for testing, but nobody asked me to write this review or influences anything on what I said. Everything above reflects my own experience and opinion and if you doubt that reach out.
17 August 2026
Unprompted review