What we test
| Area | What we check |
|---|---|
| Devices | Real iPhone and Android phones, tablets and desktops |
| Browsers | Chrome, Safari, Edge and Firefox |
| Speed | Lighthouse and Core Web Vitals on mobile |
| Accessibility | Keyboard use, screen reader, contrast and labels |
| Forms | Every form, its errors, its emails and its CRM record |
| Tracking | Each key event fires once and only once |
| SEO | Titles, descriptions, headings, redirects and indexing settings |
| Content | Spelling, prices, hours, phone numbers and links |
Automated tools plus people
Lighthouse, built into Chrome, audits performance, accessibility, best practices and SEO in one run. It catches many technical issues quickly. Automated tools miss problems a person sees right away, like a confusing menu, a wrong price or a form that works but feels long. We use both.
Test with real tasks
The best test asks someone to do what customers do.
- Find a specific service and its price.
- Call the business from a phone.
- Request a quote through the form.
- Book an appointment, if the site offers booking.
- Find the address and directions.
If any task takes too long or fails, we fix it before launch.
Good example. Before launch, a team submits every form on three phones and checks that each lead reaches the CRM with its source. It finds and fixes a booking email that went to spam.
Bad example. A team launches after checking the homepage on one laptop. The contact form on phones fails for two weeks before anyone notices.
Read the website launch checklist. Our web design team runs this testing on every site before launch day.