We checked679 local websites
One home page check on 679 small business websites, and the problems that came up most.
- 1 in 4run software with a known security flaw
- 42%load tracking with no consent tool
- 1 in 3leave their email open to spoofing
What we did
On 3 November 2026 we took every business website OpenStreetMap lists in and around twelve towns: Exeter, Honiton, Tiverton, Chard, Weymouth, Wells, Glastonbury, Shepton Mallet, Burnham-on-Sea, Minehead, Salisbury and Shaftesbury. We left out national chains, councils and schools, which left 872 local businesses and charities.
We ran the free Mendbird check on each one, once. 193 did not answer with a web page, often because the address no longer works. That left 679 sites: 321 that tell people about a business, 246 that sell online and 112 that take bookings.
The check only sees what anyone can see from outside: the home page, what the server says about itself, and the public records for the domain and email. We did not log in anywhere or try to break in.
Most sites have something worth fixing
421 of the 679 sites (62%) had at least one problem we would call major or worse. Only 48 had nothing more serious than the small extra settings most sites leave out. None had nothing at all.
That is not because local businesses are careless. Most of these sites were built well, then left alone for years while the software underneath them aged.
1. Software with known security flaws
166 sites (24%) show a version of WordPress, a plugin, a theme, jQuery or PHP with known security flaws. On 59 of them (9%), at least one of those flaws is one attackers are using right now.
- Plugins and themes were the most common, on 120 sites. Page builders, sliders and contact forms came up again and again.
- PHP, the language underneath most of these sites: 35 run a version that no longer gets security fixes at all, some as old as PHP 5.6 from 2014. Another 16 run PHP 8.2, which stops getting fixes on 31 December.
- WordPress itself: 29 sites. Twelve of them were only one version behind, but that one update fixed 18 flaws.
- Old jQuery, a script many older sites still load: 25 sites.
Half the sites (341) also announce which versions they run, which saves an attacker the trouble of finding out.
Ask your developer“Is everything on our site up to date, including plugins, the theme and PHP, and who keeps it that way?”
2. Tracking before anyone agrees
287 sites (42%) load analytics or advertising tags with no sign of a cookie consent tool, so the tracking starts before the visitor has had any say. Another 76 have a consent tool, but the tracking still seemed to start first. 281 set cookies the moment the page opens.
Advertising tags, such as Facebook's pixel or Google's advert tracking, always need a visitor's agreement first under UK rules. Since 2025, simple analytics used only to improve your own site can run without it, but only if you tell visitors and give them an easy way to say no, and the analytics company does not use the data for its own ends. The usual cause is a tag added by an agency or a plugin, with nobody checking whether it waits.
Ask your developer“Do our analytics and advert scripts wait until a visitor says yes?”
3. Email anyone can pretend to send
223 sites (33%) have no DMARC record for their email, and 54 have no SPF record. These are short public notes that tell other mail servers which emails really come from you.
Without them, a scammer can send an invoice that looks like it came from your address, and your own emails are more likely to land in spam.
Ask whoever runs your email“Do we have SPF, DKIM and DMARC set up, and is DMARC set to do more than just report?”
4. Pages that jump about
464 sites (68%) have pictures with no size set, so the page jumps as they arrive. On a phone that means a tap meant for one button lands on another.
114 home pages are heavy enough to be slow on mobile data, 51 servers are slow to start sending anything, and 22 sites are not set up for phones at all. There is more on this in why is my website slow.
Ask your developer“Can you set the size on our pictures and make the home page lighter on phones?”
5. Hard to use without a mouse or a screen
461 sites (68%) had at least one problem for people who use a screen reader or a keyboard. The most common was links with no words, usually icons for social media or a basket, on 352 sites. A screen reader can only read those out as “link”. 173 had pictures with no description, 109 had form boxes with no label and 109 had buttons with no words.
Ask your developer“Can you give every link, button, form box and picture words a screen reader can read out?”
6. Small settings most sites skip
Every server sends a few security settings with each page. Three in four sites (509) leave out the one that limits where scripts can come from, 441 let other sites show them inside a frame, and 348 do not tell browsers to always use the secure address. 35 do not move people from the insecure address to the secure one at all.
None of these is urgent on its own, and they take minutes to add. Our guide on checking your own site explains what they do.
And a few that could not wait
- Two domains had already run out and were days from being suspended, taking the site and email with them. Several more were due within the week. See do you really own your domain.
- 9 home pages tell Google not to show them, usually a setting left on from when the site was built.
- 3 addresses showed a parking page instead of the business's website.
Check your own site
Every number here came from the same free check you can run on your own site in about ten seconds. Check your site to see which of these apply to you, with the question to send your developer for each one.
On a Watch plan the check runs every morning, and you get an email when something changes or a new flaw is found in software your site runs.