When a company website has been running for a few years, start the audit with the PHP version, updates, backups and access. Design and content? Later. In November 2026, with the 2027 budget on the table, a review like this quickly shows whether ongoing care for your current site is enough or whether it’s time to think about a new one. Below is a checklist ordered from the highest risk down. Each item has a check you can do yourself in a few minutes and a warning sign that means you should call your web developer.
Table of contents
Company website audit at a glance: a checklist ordered by risk
First come the things that can lead to a hack or to losing the site. Last come the things that only make it less effective. The table is for a quick run-through (a cheat sheet of sorts), and you’ll find the details below.
| Item | How to check | Warning sign |
|---|---|---|
| PHP version | Hosting panel, Site Health | Unsupported version |
| Updates | WordPress dashboard | Abandoned plugins, theme with no updates |
| Backups and access | Hosting panel, list of administrators | No off-server backup, unknown administrator |
| HTTPS and forms | Padlock in the browser, test submission | Warnings, message doesn’t arrive |
| Cookies | Browser developer tools | Tags load before consent |
| Accessibility | Keyboard navigation | You can’t reach the form |
| Speed | Core Web Vitals report | URLs that need improvement |
| Content | Review of subpages | Outdated details and offer |
| Search Console | Indexing report | No access, many errors |
Are your PHP version and plugins still supported?
PHP version on your hosting
Unsupported PHP no longer gets security fixes. That’s why I start here. According to the table of supported PHP versions, PHP 8.2 gets security fixes until 31 December 2026, PHP 8.3 until 31 December 2027, PHP 8.4 until 31 December 2028 and PHP 8.5 until 31 December 2029. Older releases are already out of support. So a site running on PHP 8.2 needs a version change before the end of the year. You can check the version in your hosting panel or in WordPress: Tools > Site Health.
Don’t make the switch on the live site. Have your developer do it, testing everything first on a copy of the site, known as staging. Old plugins and themes have a habit of simply breaking after a switch like this.
WordPress, theme and plugin updates
In the dashboard you’ll see when the core, theme and plugins were last updated. For each plugin, check whether the author is still developing it. A theme bought years ago on some marketplace and never touched since? That’s a real risk, not a theoretical one. The warning sign is a plugin abandoned by its author or a theme that can’t be updated.
Backups, passwords and the domain: who really controls the site?
Two classics of an old website: a backup nobody has ever restored anything from, and access details that stayed with a former developer. Answer a few questions honestly:
- Where are the backups stored, and is at least one of them off the website’s server?
- Has anyone ever restored the site from them? We explain how to test a backup without any risk.
- Who knows the passwords to the WordPress admin, the hosting and the domain registrar?
- Is the domain registered to the company?
- Who has the administrator role in WordPress?
Call your developer if there’s no off-server backup, if the list includes an administrator nobody recognises, or if the domain belongs to a private person outside the company. That last case is more common than you might think.
HTTPS, forms and cookie consent: does the site work and collect data as described?
Three things: a valid certificate, a working form and a banner that actually holds back tracking until consent is given. Click the padlock in your browser, check the certificate’s expiry date and make sure there are no mixed content warnings. Then send a test submission through the form. Did it arrive? And how much spam lands in the inbox?
Also compare the data the form collects with what the privacy policy says. The two often drift apart after years of adding fields. For cookies, use the developer tools to check whether analytics and advertising tags load only after the consent button is clicked. Messages not arriving, or tags firing too early? You need a developer.
Accessibility and speed: how does an older website cope on a phone?
Accessibility
Check accessibility regardless of the regulations, because it affects everyone who visits the site. The Polish Act on the accessibility of certain products and services has applied since 28 June 2025 and covers, among other things, e-commerce services. For a simple business card website, your obligations depend on what the company sells online. A quick test: go through the site using only the Tab key, judge the text contrast and see whether images have alt text. Can’t reach the form without a mouse? Exactly.
Speed
You can assess speed in the Core Web Vitals report in Search Console. According to the Web Vitals documentation, a good result is LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1, measured at the 75th percentile of visits. If the report flags URLs as needing improvement, you’ll want a developer and our article on how to improve Core Web Vitals on WordPress.
Content, company details and Search Console: what has gone out of date without you noticing?
After a few years, even basic company details go out of date. And nobody notices, because nobody looks. Review the address, phone number, opening hours, prices, team members, services you no longer offer and old posts with dates. In Search Console, check whether the property is connected at all, who has access to it and whether there are indexing errors or excluded pages. You need a developer if there are many errors, if you have no access to the account, or if your offer simply no longer fits the site’s structure.
When should you replace your company website, and when is a review and ongoing care enough?
If the problems revolve around updates, backups and minor bugs, a review plus ongoing WordPress technical maintenance is enough. A new website is a different story. These signs point towards one:
- a theme with no updates that can’t run on a supported PHP version,
- a site that works poorly on phones,
- a company offer that has changed so much that the current structure no longer reflects it.
If you’re going for a new site, plan a redesign without losing traffic, which means keeping URLs and setting up redirects from old subpages. Without that, it’s easy to lose what the old site has built up in Google over the years.
A company website audit is the most sensible starting point for your 2027 budget. You see right away what’s urgent now and what can wait. Want the review to cover search visibility too? Order an SEO audit of your company website and use it to decide what to do next.
Frequently asked questions
How often should you review a website?
A full review once a year is plenty, ideally before budget planning. Updates and backups are an ongoing matter. If you take care of them, the annual check won’t bring any surprises.
Can I review my website myself?
Yes, you can do the checks from the list above yourself. All you need is access to the admin panel and a browser. But it’s better to outsource the PHP version change and updates on a live site. A developer will test them on a copy first.
What is more urgent in 2027: a new website or updating the company website?
Security comes first: a supported PHP version, up-to-date plugins, tested backups. Decide on a redesign only after the review results are in. Then you’ll know whether the current site can still be maintained.







