Services
Website testing services
Qaveridia offers eight testing services for websites. Each can be booked on its own, and the pre-launch QA review combines them into one scoped pass before go-live. Every engagement ends with written findings and evidence for each defect; retest rounds are listed in the written quote.
Each service below covers one strand of website quality. The strands overlap at the edges, which is deliberate: a form that fails only in Safari is both a functional defect and a browser defect, and it appears once in the report with both facts recorded. You can pick the strands that match your risk, or let the pre-launch review cover them all.
- Functional testingForms, logins, bookings and checkout steps, tested end to end with evidence.
- Cross-browser testingChrome, Edge, Firefox and Safari, chosen from your own visitor data.
- Responsive testingPhones, tablets and wide screens, with zoom, rotation and touch.
- Accessibility checksA WCAG 2.2 sample within QA: keyboard, labels, contrast, zoom.
- Security checksHTTPS, response headers, exposed files and update hygiene, checked from outside.
- Search metadata checksTitles, descriptions, canonicals, redirects and structured data.
- Performance checksCore Web Vitals, page weight, images, scripts and caching.
- Pre-launch QA reviewEvery strand of testing in one scoped pass, with one report.
How to choose
Start from what would hurt most if it broke. For a site that exists to generate enquiries, that is the contact and quote forms, so functional testing comes first. For a shop, it is the route from product page to payment confirmation. For a public-facing service with a broad audience, accessibility and device coverage carry more weight. For a site moving to a new domain or platform, search metadata and redirects can decide whether visitors find it at all.
If you are unsure, the pre-launch QA review is the safe default for a new site or redesign. For an existing site after an update, a narrower combination can be enough: functional testing of the flows that changed, plus a browser and device pass on the affected templates.
| Question you are asking | Service that answers it |
|---|---|
| Do our forms and flows work end to end? | Functional testing |
| Does the site behave the same in every major browser? | Cross-browser testing |
| Does it work on phones, tablets and wide screens? | Responsive and device testing |
| Can people using a keyboard or zoom use it? | Accessibility checks within QA |
| Have we left anything exposed or misconfigured? | Security configuration checks |
| Will search engines see the right pages and addresses? | Search metadata checks |
| Are the main templates fast enough? | Performance checks |
| Is the whole release ready to go live? | Pre-launch QA review |
What every engagement includes
Whatever the scope, the same working rules apply.
- Written scope. Pages, flows, browsers, devices and dates are agreed in writing before testing starts, along with what is out of scope.
- Visible test cases. For functional work, you see the test cases before we run them.
- Evidence on every defect. Each finding records the page, browser, device, steps, expected and actual result, severity, and a screenshot or recording.
- Retesting as quoted. The quote says how many retest rounds are included; scope changes are agreed in writing before work resumes.
- Plain reporting. Findings are written for the person who has to decide, with technical detail underneath for the person who has to fix.
- Honest limits. Each report says what was not tested. A clean result means nothing in scope failed while we were testing, and we never present it as more than that.
Who we test for
Qaveridia works with organisations in Ireland and across the EU that have a website to launch or maintain: small and medium businesses, charities, membership bodies, professional practices, and the agencies and freelancers who build for them. We test websites as visitors meet them, so the platform matters less than the flows: WordPress, other content management systems, hosted builders and custom builds are all in scope.
An agency can bring us in to give a client a second view before handover. An owner can bring us in to have someone other than the builder check the work. Both arrangements work the same way. The findings go to whoever needs them, in the format they need.
What we do not offer
We do not build or fix websites as part of a testing engagement. We do not run penetration tests, issue accessibility conformance certificates, perform load testing, or test native mobile apps. If one of those is what you need, we will tell you plainly and suggest you look for a specialist in that area, rather than stretching a QA review to fit.
Testing after launch
Testing does not stop at go-live. Updates to the CMS, themes, plugins, hosting and third-party services all change a site after launch, and any of them can break something that used to work. For sites that change regularly, a short regression round after updates, using the test cases written for launch, keeps the gains from the original review. We quote these rounds individually or as a regular arrangement, and the guide to testing after CMS and plugin updates explains the routine if you prefer to run it yourself.
Next steps
Read how the QA process works in detail, see how we quote and price testing work, or look at the sample reports to see what you would receive. When you are ready, send a brief with your launch date and the flows that matter most.
Not sure which strands your release needs?
Describe what is launching or changing. Our free reply by email, with no obligation, says which of these strands, if any, would help.
- Written scope
- Fixed quote before any deposit
- Plain-language findings