Apex Options Request a quote

Insights, Security

What a website security check looks for, and 10 common issues on small business sites.

A website security check looks at your site from the outside, the way an attacker, a customer or a search engine sees it. Most of what it finds on small business sites is not exotic: it is software left out of date, information left on show and settings nobody switched on.

A website security check is a review of your site from the public internet. It does not try to break in. It looks at what anyone can see: encryption, the software the site reveals, pages that should not be reachable, how forms handle personal data and whether cookies load before consent. The output should be a short list of problems ranked by what to fix first.

It matters because small businesses are regular targets. The government's Cyber security breaches survey 2025/2026 found that 43% of UK businesses reported a cyber security breach or attack in the previous 12 months, including 42% of micro businesses and 46% of small businesses. The ten issues below are the ones worth checking on any small business site, in roughly the order they tend to matter.

Before anyone checks your site: permission

Only check a website you own or are authorised to test. Section 1 of the Computer Misuse Act 1990 makes it an offence to cause a computer to perform a function with intent to secure access to programs or data when that access is unauthorised. A reputable check is non-intrusive and starts with written confirmation that you own the site or have the owner's authority.

The 10 common issues

1. Out of date software, themes and plugins

Content management systems such as WordPress run on a core application plus themes and plugins, each updated separately. A plugin that has not been updated, or has been abandoned by its developer, is one of the most common ways into a small business site. The Cyber Essentials requirements published by the NCSC set a useful benchmark: updates that fix critical or high risk vulnerabilities should be applied within 14 days of release, and unsupported software should be removed.

2. Software versions on public display

Many sites announce exactly which version of their platform, theme or plugins they run, in page code, file names or readme files left on the server. That tells an attacker which known weaknesses to try.

3. HTTPS that is missing, partial or about to expire

Every page should load over HTTPS, and the plain HTTP address should redirect to it. A check looks for certificates close to expiry, pages that mix secure and insecure content, and forms that submit over an unencrypted connection. The ICO recommends using encryption when transmitting personal data over the internet, which includes the contact and enquiry forms on most business websites.

4. Missing security headers

Security headers are short instructions the server sends with every page, telling the browser how to behave. They include Strict-Transport-Security, which keeps visitors on HTTPS, a Content-Security-Policy, which limits where scripts can load from, and settings that stop the site being framed inside another page. Many hosting packages do not switch them on by default.

5. Admin login pages open to the world

The login page for a site's admin area is often at a well-known address. That is not a problem in itself, but it becomes one when the admin accounts use weak or reused passwords and no second step. The Cyber Essentials requirements say multi-factor authentication should always be used for administrative accounts and for accounts accessible from the internet. Limiting login attempts and removing old admin users closes most of the gap.

6. Public lists of user names

Some platforms publish author or user names through archive pages or public data feeds. Combined with an open login page, that gives an attacker half of every admin login. A check confirms whether user names can be listed and whether the public author names match the real login names.

7. Forgotten pages, files and test sites

Demo pages from a theme, placeholder text, old landing pages, backup copies of the site and staging or test versions on a subdomain are all common. They are often unmaintained, so they carry old software and sometimes real data. Anything not in use should be removed rather than hidden.

8. Forms that collect more than they need

Contact, quote and job application forms collect personal data. A check looks at what each form asks for, whether it says how the data will be used, where submissions are sent and whether uploaded files such as CVs can be reached by anyone with the link.

9. Cookies set before consent

Under regulation 6 of the Privacy and Electronic Communications Regulations, a site must give clear information about cookies and get consent, unless a cookie is strictly necessary for the service the visitor asked for. ICO guidance states that analytics cookies are not strictly necessary, and that setting a non-essential cookie before the visitor takes a positive action does not count as valid consent. A common finding is a cookie banner that appears correctly while tracking scripts have already loaded behind it.

10. No clear way to report a problem

If someone finds a weakness in your site, they need a way to tell you. The NCSC's Vulnerability Disclosure Toolkit recommends a security.txt file, defined in RFC 9116, published in the standard /.well-known/ location on each domain, naming a contact for security reports.

What a good report looks like

A useful report is short and ranked. Each finding should say what was found, why it matters, how to fix it and who is likely to be responsible: your web developer, your hosting provider or your internal team. Free automated scanners are a reasonable first look, but they tend to produce long lists of low priority warnings without context. The NCSC's own free Web Check service, which scanned internet-facing sites for misconfigurations and vulnerabilities, was retired on 31 March 2026, so organisations that relied on it need another way to review their sites.

How Apex helps

Apex Options offers a free website security check for UK organisations. It is non-intrusive, covers security basics, exposed information, outdated software, forms and data, quality and search, and comes back as a written report ranked by what to fix first. If you want help fixing what it finds, we quote in writing first, through our web design and development and cybersecurity and compliance services. We work nationwide and remotely, with on-site support in London, Liverpool, Manchester, Greater Manchester and Cheshire.

Sources

Questions

Questions.

Will a website security check slow down or break my site?

A non-intrusive check should not. It reads what the site already makes public, in the same way a browser or search engine does, and does not attempt to log in, guess passwords or exploit weaknesses.

How often should a small business check its website?

At least once a year and after any major change, such as a redesign, a new plugin or a change of hosting. Software updates need attention far more often: Cyber Essentials expects critical and high risk fixes within 14 days of release.

Do I need cookie consent for website analytics?

Under current ICO guidance, analytics cookies are not strictly necessary, so you need consent before setting them. The ICO's guidance is under review following the Data (Use and Access) Act 2025, so check the latest position before changing your banner.

Request a quote

Tell us what you need looked after.

Send a short brief and we will come back to you to talk it through, visit if needed, and confirm scope and pricing in writing.

info@apexoptions.co.uk0330 520 4110