Web quality
I audit and fix the technical SEO, loading speed and accessibility of existing websites. I measure before and after the fix, so the difference is visible.
Who it is for
Website owners who want to know where their site stands on speed, accessibility and search-friendliness. The audit can be ordered on its own.
What I check and fix
- Technical SEO
- Titles and descriptions, canonical and hreflang, structured data, sitemap, robots.txt, internal links.
- Loading speed
- Core Web Vitals, image optimisation, self-hosted fonts, dropping unnecessary JavaScript.
- Accessibility
- WCAG 2.2 AA: contrast, keyboard use, focus, forms, screen readers.
- Data minimisation
- Finding and replacing third-party scripts, fonts and cookies.
Audit and fixing are separate
- What the audit gives you: a short summary, the issues ranked by severity and impact, measured values with the test environment, and suggested fixes.
- Fixing can be ordered separately. The audit does not need access to the code.
- Lighthouse is a measuring tool, not a full guarantee of quality or accessibility, so I also test by hand. A score of 100 is not a general promise, not for client projects either.
What I measure, and the threshold
These are the thresholds this site is checked against too, before every release.
| Area | What I check | Tool | Threshold |
|---|---|---|---|
| SEO | title, description, canonical, hreflang, H1, JSON-LD, sitemap, internal links | own audit | 0 issues |
| Speed | Lighthouse performance on mobile and desktop | Lighthouse | 100 |
| Accessibility | WCAG 2.2 AA in light and dark theme, keyboard, 320 px wide view | axe, Playwright, NVDA | 0 issues |
| Privacy | requests to third parties, cookies, localStorage | own audit | 0 |
What you get at the end
- A list of the issues found, in order of importance, each with the reason.
- Measured values before and after the fixes.
- The fixes in the code, or an exact description if someone else applies them.
- Where possible, an automated check so the issue does not come back.
How it goes
- 1. Measure. Automated and manual audit: what is slow, what is not accessible, what search engines miss.
- 2. Order. What affects the most visitors comes first. For every fix I write down why it matters.
- 3. Fix. Standard solutions that still work after the next update.
- 4. Re-measure. Where possible I automate the check, so the result stays.
Tools
Lighthouse, PageSpeed Insights, axe-core, Playwright, Google Search Console, NVDA
Frequently asked questions
What is WCAG 2.2 AA?
The international guideline for web accessibility. Level AA is the level expected in practice: enough contrast, full keyboard use, visible focus, clear form errors, and a structure a screen reader can make sense of.
Do you need access to the code?
Not for the audit, that works on the public site. For the fixes yes, or I give the developer an exact description.
Is one Lighthouse run enough?
No. Lighthouse is a good starting point, but it cannot see part of the accessibility issues, such as a logical focus order or what a screen reader announces. I check those by hand too.
Related work
levikaldor.hu: Lighthouse 100, WCAG 2.2 AA, no third parties
Ask for an audit
Want to know where your site stands? Give me its address and I will see what can be checked.
Put the project together step by step, with an informative estimate