Services

One audit. Three dimensions of frontend health.

Every audit is done by hand, by me. Automated tools are a good starting point, but they only catch part of the problem. You can pick one focused audit, or get all three together in a single report.

01 / Accessibility

Remove barriers before they become blockers.

I go through your most important pages and user flows and check them against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Most of the work is manual. I use your site the same way people with disabilities do, with a keyboard, a screen reader, and the browser zoomed way in.

You'll get a clear list of what's getting in people's way, who it affects, and how to fix it. The goal is to make accessibility part of how your team builds things, not a last-minute scramble before launch.

What I review

  • Keyboard behavior: logical tab order, no keyboard traps, operable menus, dialogs, and custom widgets.
  • Focus management: visible focus indicators, focus not obscured by sticky UI, and correct focus after route changes and modals.
  • Semantics and structure: landmarks, headings, lists, tables, and accessible names for links, buttons, and controls.
  • Forms: labels, instructions, error identification, error recovery, and redundant-entry requirements.
  • Color and contrast: text, icons, focus rings, and states that rely on color alone.
  • Assistive technology: spot-checks with screen readers and zoom/reflow at 400%.
  • WCAG 2.2 additions: target size, dragging movements, consistent help, and accessible authentication.
02 / Performance

Find what makes the experience feel slow.

I look at your Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) using real user data and my own testing.

Sometimes tracking down performance problems feels like searching for a needle in a haystack. I'll find the needle, and I'll rank every fix by how much your users will actually notice it, so your team isn't spending weeks on things nobody will feel.

What I review

  • Core Web Vitals: root causes behind Largest Contentful Paint: how long it takes for the biggest image or block of text on the screen to show up. Good is 2.5 seconds or less., Interaction to Next Paint: how quickly the page visibly responds when someone clicks, taps, or types. Good is 200 milliseconds or less., and Cumulative Layout Shift: how much the content jumps around while the page loads. Good is a score of 0.1 or less., with field data where available.
  • Rendering path: render-blocking resources, critical CSS, server response, and caching.
  • JavaScript: bundle size, long tasks, hydration cost, third-party scripts, and main-thread contention.
  • Images and media: formats, sizing, responsive sources, lazy loading, and LCP image priority.
  • Fonts: loading strategy, subsetting, fallback metrics, and layout shift from font swaps.
  • Network: request waterfalls, preconnects, compression, and CDN usage.
03 / Responsiveness

Make every breakpoint feel intentional.

Most sites look fine at the few screen sizes they were designed for. But real people are using split-screen laptops, big phones turned sideways, tablets, and browsers zoomed in to read more easily.

I test across all of those, including the weird in-between sizes automated tools don't really check, and show you exactly where things break and why.

What I review

  • Navigation: menus, sticky headers, and off-canvas patterns at every size.
  • Forms: input types, mobile keyboards, autofill, and error visibility on small screens.
  • Layouts: overflow, wrapping, grid and flex edge cases, and content reflow.
  • Touch targets: size, spacing, and gesture alternatives.
  • Content behavior: long words, translated strings, tables, media, and embedded content.
  • Orientation and zoom: landscape, text resizing, and browser zoom.

Deliverables

The report is built to be acted on.

You won't get a 200-page PDF full of scanner warnings. You'll get a focused report that your leadership can understand and your developers can start working on the same day.

  • Executive summary
    A short overview for decision-makers.
  • Evidence for every finding
    Severity, screenshots, and steps to reproduce.
  • Prioritized developer backlog
    Ready to drop right into your issue tracker.
  • Code-specific recommendations
    Actual fixes, not vague advice.
  • Quick wins and larger fixes
    Split up so it's easy to plan your sprints.
  • Personal walkthrough
    We'll go through the findings together and I'll answer any questions.

How it works

A simple three-step engagement

  1. Scope

    Send me your URL, the user flows that matter most, and what your business cares about. We'll agree on the pages and a fixed price before I start anything.

  2. Audit

    I go through the pages we agreed on and write up what I find, with evidence and a recommended fix for each issue.

  3. Act

    Your team gets a practical backlog and a walkthrough of everything I found. If you want, I can also stick around and help with the fixes.

Fixed scope and price agreed before work begins

Transparent starting prices

Accessibility Audit

from $1,500

Focused WCAG 2.2 AA review of agreed pages and journeys.

Request a proposal for an Accessibility Audit

Performance Audit

from $1,000

Core Web Vitals diagnosis with a prioritized improvement plan.

Request a proposal for a Performance Audit

Available add-ons

Remediation
I can work alongside your team to fix the issues, or hand over changes that are ready to merge.
Re-testing
I'll check that the fixes actually solved the problems and didn't break anything else.
Monthly monitoring
Regular check-ins so new problems get caught before your users run into them.

Final scope depends on site size and complexity.

Start with your URL.

Send me your site, your goals, and anything you already know is broken. I'll get back to you with a recommendation and a fixed-price proposal.

Get a proposal

Typical turnaround: about two weeks after scope and access are confirmed.