Website audit and action list
Do you know why your website is not delivering, or do you only sense that something is wrong?
I review your website technically, for performance and for content, and hand over a list of findings ranked by impact. Each item comes with the reason, the fix and an estimate of the work.
Most websites that land on my desk do not have one big problem. They have fifteen small ones that multiply each other: slow loading from unoptimised images, three plugins doing the same job, missing headings, a contact form that has been sending nowhere since spring, and pages Google does not know exist. Each one looks negligible on its own, yet together they decide whether a visitor stays and whether they reach your site from search at all.
The point of an audit is that you learn exactly what to fix and in which order, without having to commission a full rebuild first. You will not get a thirty-page dump from an automated tool that takes half a day to read and still leaves you guessing where to start. You get findings ranked by impact, written in plain language, with an hours estimate on every item. I can then do the fixes, or you hand the list to your own developer. Either is fine.
01
Technical review
I go through the site the way a browser and a search engine see it. I check error pages and broken links, redirect chains, indexability, robots.txt and the sitemap, canonical addresses, duplicate content, console errors, whether forms work and whether their e-mails are delivered. I pay particular attention to the things nobody watches until they fail: expiring certificates, indexing left blocked from the development phase, or a form that quietly stopped sending after a plugin update.
- Errors, broken links and redirects
- Indexability, sitemap and canonical addresses
- Forms and e-mail deliverability
- Console errors and server logs
02
Performance and Core Web Vitals
I measure speed under realistic conditions, not in a single test on a fast connection. I look at Core Web Vitals, meaning LCP, CLS and INP, and I look for their actual causes: unoptimised images without modern formats, blocking scripts, too many plugins, slow hosting, missing caching or fonts loaded from remote servers. For every finding I state how many seconds are realistically on the table, so you can weigh the benefit against the effort and avoid spending hours on optimisations with no measurable impact.
- LCP, CLS and INP measured on real pages
- Images, scripts, caching and hosting
- An estimated real gain for every finding
03
Security and updates
I check the versions of the core, themes and plugins, known vulnerabilities, abandoned extensions with no support, user accounts with more rights than they need, how backups are configured and whether they can actually be restored. On WordPress sites I regularly find plugins nobody has updated in years, or administrator accounts left behind by previous suppliers. Security findings are prioritised by how easily they can be exploited, not by how alarming they sound in an automated report.
- Vulnerable and abandoned plugins
- Accounts, permissions and supplier access
- Backups and verified restore
04
Content, structure and SEO
I look at heading structure, titles and descriptions, internal linking, menu depth, and whether the site answers the questions people actually type into search. A common finding is a site with ten service pages that differ by a single sentence, or the opposite: one page trying to cover five different queries at once. The review also covers mobile rendering, readability, and whether the contact details and the call to action sit where a visitor looks for them.
- Headings, titles, descriptions and internal links
- Query coverage and duplicate pages
- Mobile rendering and the path to contact
05
The output, the price and what comes next
You receive a document listing the findings ranked by impact and split into quick fixes, medium tasks and larger changes, with an hours estimate on each item. We go through the results together on a call, so you know what they mean rather than just that they are red. My rate is EUR 40 per hour including VAT and an audit normally takes 3 to 6 hours depending on the size of the site. If you decide to have me do the fixes, the audit hours are not charged again.
- A prioritised list with hours estimates
- A call to walk through the results together
- Rate of EUR 40 per hour including VAT
- An audit is roughly 3 to 6 hours
?
Common questions about website audits
How much does a website audit cost?
An audit normally takes 3 to 6 hours, i.e. EUR 120 to 240 including VAT at EUR 40 per hour. A larger site with a shop or hundreds of pages needs more time, which we agree on in advance.
How long does an audit take?
Usually three to five working days from getting access. If you need a faster answer to an acute problem, such as a traffic drop or a suspected compromise, I can look at it as a priority.
What do you need from me?
The address of the site, access to the admin and ideally to Google Search Console and analytics as well. An audit is possible without that data, but you lose part of the answers, and usually the most useful ones.
Do I have to order the fixes from you?
No. The output is written so any developer can pick it up and work from it. If you do have me do the fixes, you are not charged again for the hours spent on the audit.
Is an audit worth it for a brand new website?
It is, especially just before launch or shortly after. That is the cheapest moment to fix problems in structure, indexing and performance that would otherwise quietly hold your results down for months.
Want to know what to fix first?
Send me the address of your site and what bothers you about it most. I will come back with the scope of the audit and a date.
Order an audit