Six WordPress mistakes that slow and expose sites
Most WordPress trouble traces back to a few habits. WordPress's own documentation warns against each of them.
1. Keeping plugins you stopped using
The WordPress hardening guide says that if you are not using a specific plugin, you should delete it from the system. Deactivating it leaves the code on the server, where it still needs patching.
2. Installing themes and plugins from anywhere
The same guide tells owners not to get plugins or themes from untrusted sources. That includes free copies of paid plugins offered on download sites.
3. Updating the live site with no backup
The WordPress upgrade instructions start with a backup and tell you to verify that it is there and usable. They also warn that an old plugin that does not work with the new code may be the culprit when a site breaks. We test updates on a copy first.
4. Assuming every update is automatic
Automatic background updates cover minor maintenance and security releases. Existing installations do not move to a new major version unless someone enables that. Plugins and themes need an owner too, which is what a hosting and maintenance plan is for.
5. Picking a theme type by accident
WordPress describes a block theme as one that uses blocks for all parts of a site, including navigation menus, header, content and footer. Classic themes do not work with the Site Editor. Decide who will edit what before the build starts.
6. Judging speed by how it feels on office wifi
Google's Core Web Vitals set the marks: main content loads within 2.5 seconds, the page responds to a tap in 200 milliseconds or less, and layout shift stays at 0.1 or less. Our Core Web Vitals guide shows how to check yours.
