Over the years, WordPress has evolved more than I could’ve imagined, and with more plugins and functionality being added every single day, the demands for a good web host did too. And thus, the search began. After doing a few hours of research for cheap but reliable hosting, I came across multiple hosting providers that provided hosting for only WordPress and nothing else.
PCMag, PCMag.com and PC Magazine are among the federally registered trademarks of Ziff Davis, LLC and may not be used by third parties without explicit permission. The display of third-party trademarks and trade names on this site does not necessarily indicate any affiliation or the endorsement of PCMag. If you click an affiliate link and buy a product or service, we may be paid a fee by that merchant.
Support – Our support team is a shining beacon within the company. We maintain a truly world-class NPS score of 86 along with 3 back-to-back Gold Stevie awards for customer service to prove it (more on that here). The team offers their best every day in an effort to serve our customers’ professional growth, and it shows in the feedback we get from them. This mentality is very much in line with one of our core values – Customer Inspired.
WP Engine Enterprise Solution – Fast Performing Infrastructure, We provide a range of enterprise-grade web solutions from Amazon Web Services and Google Cloud Platform. Threat Detection & Blocking Let us dynamically detect and block malicious behavior with our proprietary system, making sure your site doesn’t suffer embarrassing hacks. Fully Managed Global CDN Load content faster with our global content delivery network (CDN), which routes local requests to the nearest server. Serviced Onboarding, For premium solutions, a dedicated technical and account management team ensures a smooth start and continued success on WP Engine.
I contacted WP Engine several times during testing—early morning and midday—to get a sense of its support team's effectiveness. I called to discover how to install new WodPress themes, and then used the web chat to contact a representative who would explain SSL certificates. The team answered both questions, and a few miscellaneous others, accurately and quickly, after short wait times.
Many things have changed since WHSR shifted out. Various new features were added as technology advances, the company is funded by a large group of investors including Automattic (the folks behind WordPress.com), and many bloggers and WP experts regard them as one of the best managed WordPress hosting (there were also some who go against them, more about that later).
Our actionable insights tools, like Page Performance and Content Performance are always a hit. Overall however, our most popular tool would be Application Performance. It provides code-level visibility to help teams troubleshoot faster, optimize their WordPress experiences, and increase development agility. It gives development and IT operation teams the visibility they need to build and maintain great WordPress digital experiences.
That’s where managed WordPress hosting comes in. WP Engine takes care of (nearly) all speed concerns. They have customized servers with extremely aggressive caching and even more advanced “stack” than a typical web host. They also have trained support who will go into your WordPress install and identify the exact chokepoint to get your site moving.
When I checked out their websites, I found they had an amazing plethora of options and security just for WordPress which I could only dream of at the web hosts I had partnered up with earlier. There was a downside however, the price. I finally came along WPEngine and I decided to sign myself up with them, due to a promotional code which allowed the first 3 months to be hosted for only 4$ a month, instead of the usual 29$.
If you approach them with any issue, they blame it on the developer. This is so they can sell you developer services, getting your current developer fired. Imagine your coding a website for someone and someone comes in when you are not looking and puts a disallow on the site. You know the default is to only disallow the admin panel and you never created a robots.txt file, nor do you even have access to the robots.txt file from the sftp. As far as you are concerned it does not exist. You then get a call from your client screaming saying that they spoke with WPE who says it is a common mistake by a rookie developer. As far as I am concerned the only person responsible for the disallow is the person who puts it there. You cant force code and not take responsibility. What other code has been forced that the developer will get blamed for?
By default, sites hosted at WP Engine with page that ends in a number, (e.g. example.com/page/1) or in a query arg, (e.g. example.com/mypage/?myproduct=name), will be redirected to the page before the number or query arg sequence begins (site.com/page, site.com/category, site.com/mypage/).* This setting, known as “Redirect Bots”, is a major SEO issue as it will limit Google bots to discover content on your site and impact website PageRank flow through your site.
From an overall infrastructure standpoint, we have partnered with Amazon Web Services and Google Cloud Platform to provide customers with a range of enterprise-grade solutions that deliver lightning-fast, scalable, highly available and secure experiences. In addition, having high quality partners like these allows us to provide data centers in wide variety of locations – 18 in total. This global presence gives us the ability to serve more customers at a local level, where they see further performance and speed improvements as a result.
WPE is over-rated. They have a lot of issues that people not in the know are unaware of. The canonical name wpengine.c causes double indexing on google and DESTROYS SEO. If you try to point the name back to your domain you run into issues with looping. They also force a no index in robots.txt without alerting anyone of doing so. This disallow gets copied over to the live site causing your site to not be indexed by google. Again DESTROYING your SEO. They added this disallow to solve the problem of double indexing, which does not work anyway because google still indexes it (the correct way is to use htaccess). So in the end the site winds up not being indexed and gets points against it from google.