Technical website audit
For a website or web app that feels slow, shaky or invisible, when you want to know why before paying anyone to fix it.
A technical website audit is a one-off check of the speed, security, accessibility and SEO of a website or web app, ending in a prioritised list of fixes. Vyorde does it in 1 to 2 weeks, changes nothing on the live site while testing, and writes the list so that any developer can work from it.
- Typical timeline
- 1 to 2 weeks. The exact dates are in your quote.
- Quote
- A written quote after a short, free call
What you get
Speed
Where the page loses time, measured on a mid-range phone, not on our laptops.
Security
Outdated software, exposed admin pages, weak settings and who still has access.
Accessibility
Whether people using a keyboard or a screen reader can get through it. If you sell to people in the EU, we also check it against the European Accessibility Act.
SEO
What stops Google from reading and indexing your pages properly.
A prioritised list
Every problem, how much it matters and roughly how hard it is to fix. Worst first.
A call to go through it
We walk you through the list and answer questions. Your own developers are welcome.
How it goes
You give us access.
Read-only where possible. We don't change anything on a live site during an audit.
We test and read.
The site itself, the code if you share it, and how it behaves on real devices.
We write it down.
In plain words, with the fix next to each problem.
We talk it through.
Then you decide who fixes what. It doesn't have to be us.
Every project follows the same five steps. See the full process.
What's not included
- Fixing what we find. Each item on the list comes with a rough size, and the work gets its own quote if you want us to do it.
- A penetration test. We look for the common, visible security gaps, not a full simulated attack.
- A legal opinion or a certificate on accessibility. That is a job for a lawyer.
- Ongoing search work such as keyword research and content plans. That is the SEO service.
Before you start
- The address of the site or app, and a test login if it has accounts
- Read-only access to hosting, analytics and Search Console, where you have them
- The code repository, if you are able to share it
- What made you ask: the complaint, the number or the page that worries you
- Who would do the fixing afterwards, if you already know
You don't need all of it for the first call.
Questions about the Technical Audit
Do we have to hire you to fix things afterwards?
No. The list is written so any competent developer can work from it. That includes your own team.
Is this a legal accessibility certificate?
No. It tells you where you stand and what to fix. If you need a formal legal opinion, that's a job for a lawyer.
Will you promise we'll rank higher after the fixes?
No, because nobody can. We fix what's holding the site back, and Google decides the rest.
What do you need from us?
The address, and read-only access where you can give it: hosting, analytics, Search Console and the code if you are happy to share it. If access is limited, we audit what is visible from outside and say what we couldn't check.
Who does the audit?
The people who design and build here. They would also do the fixes if you ask us to, so the list is written by someone who knows what each fix involves.
How is this different from your SEO service?
The audit is a one-off look at the whole site: speed, security, accessibility and whatever blocks search engines. The SEO service is the work that follows: structure, keyword research, on-page changes and a content plan.
What does it cost?
It depends on the size of the site and how much access we get. You get a written quote after a short, free call, before anything starts.
More questions are answered on the FAQ page.
From Insights
The other two packages
- 02MVP BuildTypically 6 to 12 weeks
- 03Fractional CTOTypically 2 to 3 weeks to get up to speed, then month to month
Last updated