Experience of Migrating a 20k+ Products WooCommerce Website
I migrated one of our fairly sized Woo websites with over 23k+ products to FlyingHost. To give full context and transparency, I had been using FlyingPress with the website for over 2 years and FlyingCDN since September 2025. The site was hosted on a Dedicated CPU Optimised DigitalOcean Droplet and still had performance issues, especially on checkout/cart pages. The Database and PHP workers were also fairly optimised, and Redis Cache was also active. The website is connected to multiple inventory management tools and Shipping platforms via APIs.
I was contemplating trying out xCloud or even a radical migration to Shopify for better performance. When the beta of Flying Host was announced, I decided to give it a try and contacted Gijo (FlyingWeb Founder). At that time, the servers were only available in the US and EU. Since we are based out of India, I preferred a server in India and within 3-4 days I was informed that the India location was also live, and I decided to do join the beta program.
Over the last 3 months or so, there have been a few pointers that I have liked about FlyingHost and their team, which have made me continue with them for a foreseeable future.
1. Migration and Support Team: The migration happened at 2 AM IST, and the team was active and assisted along the way. It took a couple of hours for a website of our size, and after a bit of data sanitisation checks, by 6 in the morning the site was live. Our setup had the blog and learning platform hosted on a separate server and served as a subfolder using a reverse proxy. It was an absolute must, and Gijo and his team delivered the custom Nginx function in the FlyingHost Panel in a couple of days
2. Pricing and Speed: Since the site was already on a beefy server, I did save decent dollars while getting better performance. Since FlyingCDN was already active on the website, the additional bandwidth costs are similar, so I won’t be counting that, but basic server costs are quite a saving. For larger websites with loads of images, the bandwidth costs may add up, so keep that in mind. I have tested it with EWWW EasyIO CDN, so I assume for other CDN providers it should work for image offloading. This method has its own pros and cons, and you can make a measured call based on that.
3. Works Brilliantly with FlyingPress. Single cache clearing clears all cache - Object, full page, as well as CDN. Less need for manual interventions
4. Uncached Pages like Cart / Checkout / My Account and even WordPress Admin are blazingly fast.
5. During the beta, the team added PatchStack for Security and a FlyingPress License. Better security, and I freed a license too .
6. Support responsiveness. The team is very responsive in case you see unwanted bots/services hitting your server. They quickly identify and patch/throttle them as needed. The average response time has been in minutes on weekdays via chat.
7. Performance Metrics: PageSpeed metrics have improved drastically. TTFB on Mobile is under 0.8s. LCP improved from under 4600ms to under 1360ms
There are a couple of points where FlyingHost may improve in their future releases
1. O2O with Cloudflare. I hate to ping the FlyingHost team for every IP whitelisting or to block a specific bot. This would ease out managing rules and traffic for everyone. This is a good-to-have.
2. Database Management - To be honest, FlyingHost does have phpMyAdmin built in. For almost 99% of users and use cases, that works fine. But when it comes to large databases, web-based tools aren’t cut out for that. They lag and time out. Detailed use cases have been shared with the team, and hopefully they will work something out for the remaining 1% of users like me. Again, not a showstopper.
Overall, I have been extremely happy with FlyingHost, and am glad I took part in the beta of an extremely new platform. To be honest, I was expecting some speed improvements since the website was already using two of FlyingWeb’s flagship products, but the improvements have been drastic. Congratulations to Gijo and his team for this, and thank you for building this.

Svar från Flyinghost







