What website QA costs in Ireland, and what drives the price

There is no standard price for website testing, because there is no standard website. A five-page site with one form and a shop with accounts, discounts and three delivery methods both need testing, but the second needs several times more of it. This guide explains what drives the cost, so you can read a quote critically, and shows what Irish providers publish.

What drives the cost

The number of flows and rules

Testing time follows the things visitors can do, not the number of pages. A hundred pages of articles built from one template are quick to test once the template is checked. A booking flow with date rules, capacity limits and confirmation emails takes time, because each rule needs cases where it is met and broken. When comparing quotes, ask how many flows each one covers.

Browser and device combinations

Every combination in the test matrix multiplies part of the work. Testing key flows on four desktop browsers and two phones takes more time than testing on one browser. A sensible matrix, chosen from your analytics, keeps this in proportion. Be wary of quotes that promise "all browsers and devices", which no tester can deliver.

Strands of testing

Functional testing, accessibility checks, security configuration checks, search metadata checks and performance checks are separate activities, each with its own time. A quote for "QA" should say which strands it includes.

Retest rounds

The first pass finds defects; the retest confirms the fixes. A quote with no retest leaves you to check fixes yourself or pay for a second engagement. Ask how many retest rounds are included and what an extra round costs.

Reporting and evidence

A defect list with screenshots and a written summary takes longer than a quick email, and is worth more, because it can be acted on and filed. Ask to see a sample report before you buy.

Timing

A launch date that leaves two days for testing and fixing is harder to work with than one that leaves two weeks. A provider may charge more for short notice. Even where none is charged, a squeezed timetable means less testing in the time available.

What Irish providers publish

Not every testing provider publishes prices. One that does is HST, a Dublin software development and QA firm, which lists these figures on its software testing page, read on 4 November 2026. They are a commercial source, given here as published, with the provider's ranges written out in words:

These figures describe software testing engagements, such as an embedded tester or an automation build, rather than a short review of a small website. They are useful as an outer marker: a focused pre-launch review of a small site involves days of testing rather than weeks, so it should cost a fraction of these engagements. They are one provider's prices and should not be read as a market average.

How day rates turn into a quote

A quote, whatever its format, comes down to days of testing multiplied by a day rate, plus time for planning, reporting and retesting. A simple way to sanity-check a quote:

This example is a planning illustration, not a quote for any real project; your own scope will move it up or down. Our own starting prices are on the pricing page.

Doing some testing in-house

Outside testing and in-house testing are not either-or. A practical split for a small organisation is to do the routine checks internally and buy outside testing for the parts that benefit most from fresh eyes and specialist tools. Things a site owner or staff member can do well without training:

• Check content, prices, contact details and opening hours against the source of truth.
• Send test enquiries from every form and confirm they arrive.
• Click through the site on their own phone and computer, noting anything odd.
• Work through the free QA checklist and record what was done.

Things that benefit from an outside tester: structured functional testing with written cases, testing across a matrix of browsers and devices, accessibility checks against WCAG 2.2, security configuration checks, and a neutral retest of fixes. Doing the first list internally can reduce the scope, and the price, of the second.

Budgeting for the year, not just launch

Launch is the most visible moment for testing, but not the only one. A site that changes every month needs a little testing every month: a regression round after updates, a form delivery check, a browser pass after a redesign of a key page. When planning a budget, set aside a modest amount for post-launch testing as well as the launch review. Small, regular rounds cost less than an emergency investigation after something has been broken for weeks.

VAT

A quote for testing should say whether VAT is added; ours are plus VAT where applicable, and the VAT treatment is stated on each quote. Revenue lists the Irish standard rate as 23 percent. Whether VAT is charged, and at what rate, depends on the supplier's registration and on where and to whom the service is supplied, so confirm the treatment with your accountant. When comparing quotes, check whether each is stated with or without VAT.

Fixed price or time and materials

Testing is sold in two ways, and each suits a different situation.

• A fixed price for a defined scope suits a launch or a redesign, where the pages, flows and browsers can be listed in advance. You know the cost before work starts. The risk is on the tester to estimate well, and any change of scope needs a written change to the price.
• Time and materials, where you pay for the days used, suits open-ended work such as regular regression testing after updates, or a site where the scope will keep moving. It is flexible but needs a cap or a regular check on days used.

Either way, the quote should make clear what happens when the work turns out larger or smaller than expected.

What cheap testing can cost

A low price is not always a saving. Testing that skips the retest leaves you to check fixes yourself. Testing on one browser misses the defects that appear only in another. A report without evidence produces arguments instead of fixes. When comparing quotes, compare what each one includes, not only the total, and ask what would be left untested at each price.

Questions to ask before you buy

• Which pages, flows, browsers and devices are in scope, in writing?
• Which strands of testing are included: functional, browser, device, accessibility, security, metadata, performance?
• How many retest rounds are included, and what does another cost?
• What does the report contain? Can we see a sample?
• Who fixes the defects? If it is the tester, how is the testing kept honest?
• Is the price fixed before work starts, and what happens if the scope changes?
• Is VAT included?

Where the money goes furthest

If budget is tight, spend it on functional testing of the flows that earn money or enquiries, and on a browser and device pass of the main templates. Defects there hit revenue and enquiries directly. Accessibility, security and metadata checks are quick to run by comparison, and a short version of each is better than none. A free QA checklist can cover the rest internally.

Sources

• Software Testing and QA Services Ireland, HST (commercial source)
• Current VAT rates, Revenue

Sources were read on 4 November 2026.