Old WordPress site problems: what to look for

Most old WordPress site problems are visible long before anyone logs into the dashboard. A theme that was fashionable in 2015, a contact form that still uses a captcha nobody has seen in years, a footer copyright date stuck two or three years in the past. For a freelance web designer, spotting these signs from the outside is a useful skill, because the site itself is telling you who might need a rebuild before you have exchanged a single word with the owner.

Why WordPress sites age differently to others

A WordPress site is really three layers stacked on top of each other: WordPress core, a theme, and a pile of plugins, each updated on its own schedule by a different developer. When an agency or freelancer builds the site and then moves on, nobody is left to keep those layers in step. Core might auto-update, but the theme and half the plugins often do not, and eventually one update breaks something that never gets fixed. The business owner notices the site still loads, decides that is good enough, and stops thinking about it entirely. That is usually the point where the gap between what the site could be and what it actually is starts to widen every month.

The visible signs, from the outside

A handful of things are checkable without any login at all. The design itself is often the giveaway: heavy drop shadows, a carousel of stock photography on the homepage, a layout that was built for a 1024-pixel screen and now sits awkwardly on a modern one. View source and you will frequently find an old page builder's signature markup, bloated with nested divs that add weight without adding anything a visitor can see. The site's behaviour on a phone is another tell: text that does not resize, a menu that overlaps the header, or a layout that technically responds but was clearly never tested by anyone on an actual handset. Broken plugin functionality shows up too, a booking widget that spins and never loads, a gallery plugin throwing a JavaScript error in the console, an old social sharing bar linking to a Google+ page that has not existed for years.

Page speed is usually the clearest single indicator. A site running a stack of unused plugins, an unoptimised theme and years of uncompressed image uploads tends to load slowly even on a decent connection, and that slowness compounds the other problems rather than sitting apart from them, as covered in why slow websites quietly lose local businesses work. An old WordPress build is one of the more common causes of that slowness, precisely because so much of it is running code nobody has reviewed in years.

What it means once you are actually in the dashboard

If you do get access, the picture usually confirms what the outside already suggested. A plugins page with a dozen items flagged for update, several marked as no longer tested against the current WordPress version, and at least one that has been abandoned by its developer altogether. A PHP version several releases behind current, which is not just a technical detail, it is often the actual reason certain plugins stopped working properly in the first place. User accounts nobody recognises, sometimes a sign the site has been compromised at some point without the owner ever noticing, since an outdated plugin with a known vulnerability is one of the more common ways a small business site gets quietly hijacked to serve spam links or malware to search engines rather than to the owner's actual visitors.

Reading the business impact, not just the technical debt

None of this matters to a business owner in technical terms, so the conversation works better framed around what it is actually costing them. A slow, dated site undersells a business that may otherwise be doing good work and charging fairly for it, and it quietly damages trust with a visitor deciding between two similar local options in the time it takes a page to load. A booking form that silently fails is a lost enquiry the owner never even hears about, because there is no error message telling either side it happened. And an unmaintained plugin is a live security risk sitting on a site the owner assumes is simply “fine because it's still up”. Framing the pitch around lost enquiries and risk, rather than version numbers, is usually what actually lands.

Turning it into an opening line, not a lecture

The mistake is leading with a list of technical faults, which reads as criticism rather than help. A better opening picks one concrete, visible thing, the booking form that does not submit, the menu that breaks on a phone, and offers to show the owner exactly what is happening and why. That one observation is usually enough to start a conversation, in the same spirit as the approach in cold email for web designers: one observation, one offer. Once a rebuild is agreed, it is also worth raising ongoing maintenance rather than leaving the new site to quietly age the same way the old one did, which is where a proper conversation about web design retainers fits naturally, since the whole reason you are having this conversation is a site nobody kept maintained.

Spotting an old, neglected WordPress site from the outside gets much faster once you are not relying on eyeballing every result by hand. Patchscout crawls and audits every business it finds for a trade and UK town, checking speed, mobile behaviour, SSL and the site builder or platform in use, and scores each one on how likely it is to actually need the work. Instead of clicking through twenty search results guessing which sites look tired, Patchscout flags the ones worth a closer look and drafts a personalised first email grounded in what it actually found. The three free searches on Patchscout are enough to see how many old, unmaintained WordPress sites are sitting in your own patch right now.