Website testing.

Have your website tested before it goes live, and again after every change. A good test looks at your site in three browsers and at five screen sizes, and checks accessibility, speed, forms and security. That way you find errors before a customer does.

5 min read
Updated 7 October 2026

One test run

example Ready to go live15 / 15 passed
360 px768 px1024 px1440 px1920 pxChromiumChrome, EdgeFirefoxFirefoxWebKitSafari, iPhone
Error found: in Safari on a 360 px phone, the button falls off screen.
This is what one run looks like: the same page in three browser engines at five screen widths, fifteen combinations. In this example the button falls off screen in Safari on a small phone. That error is fixed and tested again before the site goes live.

Why test a website?

A site that works in your browser can break on your customer's phone. You do not notice, because you usually look at your site on one device. Your visitors use Safari on an iPhone, Chrome on Android and Firefox on a laptop, each with a different screen width.

The most expensive errors are the silent ones. A contact form that no longer sends gives no error message: nothing comes in. You see fewer enquiries, but not why.

What gets tested?

At Ekkora, no site goes live until these eight checks pass. For each check you can see what is tested and what goes wrong if you skip it.

  1. BrowsersPlaywright

    Your site is opened in the three browser engines that run the web: Chromium (Chrome and Edge), Firefox and WebKit, the engine behind Safari.

    a menu that works in Chrome but does not open in Safari on an iPhone.

  2. Screen sizes360 to 1920 px

    Every page is viewed at five widths: a small phone (360 px), a tablet (768 px), a small laptop (1024 px), a laptop (1440 px) and a large screen (1920 px).

    a button that falls just off screen on a small phone.

  3. Accessibilityaxe-core, WCAG 2.2 AA

    Contrast, heading structure, labels and alt text are tested automatically against WCAG 2.2 level AA. We also check that everything works with the keyboard and that the site stays calm for people who prefer less motion.

    grey text that cannot be read on a phone screen in the sun.

  4. SpeedLighthouse

    Load time is measured on a simulated mobile connection, like a visitor opening your site on the go.

    a photo of several megabytes that makes the page wait for seconds on 4G.

  5. Links and formsPlaywright

    Every link is followed and every form is actually submitted, all the way to the confirmation.

    a quote form that has sent nothing for weeks without anyone noticing.

  6. Visual regressionpixel comparison

    After every change we take screenshots and compare them with the version you approved.

    an update that quietly shifts the layout of another page.

  7. Securityheaders

    We check HTTPS, HSTS and a Content Security Policy: the settings that protect visitors and their data.

    a browser that shows "Not secure" next to your domain name.

  8. FindabilitySEO scan

    Titles, descriptions, sitemap and structured data must be correct, so search engines and AI assistants can read your pages properly.

    a page that Google visits but does not include in the search results.

When should you test?

Not once, but at three moments. Browsers get updates too, so a site that works today is no guarantee for next month.

  • Before launchThe full test, on every page. The site only goes online once everything passes.
  • After a changeA new page, a WordPress or plugin update, a different form: test again before visitors notice.
  • Every monthA regular check catches what changed without any change on your side. At Ekkora this is part of maintenance.

Does your site have to be accessible?

For some businesses this has recently become a legal requirement. Since 28 June 2025 the rules of the European Accessibility Act apply in the Netherlands. The Dutch Authority for Consumers and Markets (ACM) supervises them.2

Who it applies to
Among others, webshops, booking platforms for hotels and tickets, ordering apps and sites where you take out a subscription.
Exemption
Micro-enterprises: fewer than 10 employees and an annual turnover of no more than €2 million.
Standard
Level AA of the WCAG guidelines. According to the ACM, WCAG 2.2 level AA will become the new standard during 2026.2 WCAG 2.2 has been the latest W3C version since October 2023.1

Does the exemption apply to you? An accessible site is still easier to use: for older visitors, for someone with one hand free, and for anyone looking at their phone outside in the sun.

Test it yourself or have it tested?

Free tools get you a long way. Lighthouse in Chrome already gives a good picture of speed and accessibility. What such tools do not do: view your site in three browser engines and five screen sizes at once, or actually submit your form. That takes automated tests, like the ones we build with Playwright.3

Start with our free website check. It runs six of the eight checks on your own site and gives you the result within half a minute, in plain language.

What does it cost?

With a website from Ekkora, the full test is included in the price. You get the test report at handover, and with maintenance the same test runs again every month.

Would you like an existing website tested? Book a 30-minute call. Afterwards you will know what it costs.

Questions

Is testing also needed for a small website?
Yes. A small site depends on a few pages and one form. If that form fails, you miss every enquiry.
My web developer says the site has already been tested. Is that right?
Ask for the test report. If it does not say which browsers, screen sizes and forms were tested, the site was probably only checked on the developer's own screen.
Can a test find every error?
No. A test finds what it tests for. That is why we run a fixed set of eight checks on every page, and add a test for every error we have ever found.

How does your site score now?

You can run six of our eight checks on your own website for free. You get the result within half a minute, in plain language.