Myth: WordPress is slow.

WordPress can support extreme speed, 1000-5000+ requests/second, sustained throughput, if...

1) The runtime LAMP Stack is tuned correctly, on an ongoing basis... meaning daily log analysis + retuning.

2) Code installed on site - Theme + Plugins - are all designed to scale.

Slowness occurs with hosting is used which isn't tuned for WordPress speed + themes/plugins are installed without vetting code for both PHP standards compliance + speed.

Almost every day I setup high speed WordPress sites for clients + speed problems only occur when one of the two guidelines above are violated.

So if anyone tells you WordPress is slow or you require some cruft technology to speed up WordPress, like NGINX or a CDN, you have a poser on your hands. Fire them + find someone who tools high speed WordPress sites + you'll be far better off than stacking cruft technology between your infrastructure + visitor browsers.
1
LVL 59

Comment

by:gr8gonzo
I would agree that themes and plugins are the two biggest culprits.

However, using a CDN can make a huge difference with ANY site, not just WordPress. It usually means faster downloads of Susie resources and a higher number of parallel downloads for faster overall rendering (most browsers have per-domain downloading limits) and a higher chance of the resources already being cached. Plus, it frees up the web service from having to serve up those static files.

Nginx and php-fpm can also make a dramatic impact on scalability. Using FPM can reduce the memory footprint of each web server worker and recycle PHP workers faster, leading to the ability to handle more requests per second. Nginx tends to have a lower per-child footprint but also sucks if you rely on htaccess files, since those are Apache-only.

In order of greatest to least opportunity for performance improvement, I'd say:
1. Themes and plugins (any custom code)
2. CDN usage.
3. Opcache/compiling.
4. PHP 7.
5. Non-shared hosting.
6. Tuned MySQL.
7. Tuned web server.
8. Tuned OS.

Of course, any one of these could have a critical misconfiguration that could cause a huge performance loss but that's not as common.
1
LVL 21

Comment

by:Lucas Bishop
Shared hosting = the most common detriment to page load
0
LVL 59

Comment

by:gr8gonzo
I'd generally disagree with that. It depends on the provider, but USUALLY a host isn't so under-powered that it is actually processing PHP at a slow speed. Bear in mind that a normal WordPress install's PHP will usually be processed in under a second. Even if you had a really underpowered or overloaded host, that might double at most (unless they're doing something REALLY wrong).

Plugins are usually where things go wrong. People install plugins that each slow down the page by 50 milliseconds here, or 250 milliseconds there, and it adds up when you install a dozen of them. Suddenly, you have 12 plugins that are cumulatively adding 4-5 seconds to the PHP processing time, even on a dedicated host. Themes CAN have similar impacts, although they're less likely to, since their impact is more on the static asset side (e.g. adding 15 images that have to be downloaded - even if the PHP code takes 1 second to process, it may take 5-10 seconds to download all the theme contents).

If you doubt the difference, use XDebug to generate a cachegrind on a shared host and a dedicated host and compare the differences.
0

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month