Free WebYes scan live: four pillars tested

The free WebYes website scan is live, in beta. Enter a web address on the homepage and within a few minutes you see how the site scores on the four pillars of the keurmerk: speed, security, mobile and accessibility. You do not need an account and you do not have to leave an email address. The report shows per finding what goes wrong and which direction you should take to fix it.

This post explains what the scan does, which limits apply in beta, how the four pillars connect to our knowledge base, and when a site qualifies for badge, profile page and re-audit. In short: from the first free check to a public keurmerk you can explain to clients and colleagues.

What the scan measures

The scan visits up to six pages of the submitted domain and tests them on measurable checks per pillar. Each pillar gets a score from 0 to 100; the average is the total score. That average alone is not enough for the keurmerk. For the WebYes keurmerk: average at least 80, and each pillar separately at least 60. A site that excels on three pillars but stays below 60 on one therefore fails the assessment. That is intentional. A keurmerk that leans on one weak pillar says little about the experience of your visitors.

More important than the number itself: the report ties every finding to a fix direction. You do not only see that something is missing, but also where to start. For deeper reading on the techniques behind the pillars we point to the knowledge base. There you find evergreen explainers on metrics, headers, certificates and accessibility criteria, so you can continue deliberately after the scan.

What beta means in practice

We deliberately call the scan beta. The engine underneath is the same audit engine we have been using for professional SEO and security audits. The translation into four pillar scores is still evolving. Score thresholds may shift slightly over the coming months and more checks will be added. What you see today is a serious measurement, not a toy tool, but not a frozen standard forever either.

Practically, the free scan works without an account. If you scan the same domain again within sixty minutes, we show the existing result instead of crawling the site again. That dedupe window keeps the scan fast and prevents a site from being visited more often than needed. The limit of six pages per scan stays: enough for the homepage, a few landing pages and a contact or product page, not meant as a full crawl of hundreds of URLs.

Speed and mobile: what visitors notice

For the speed pillar we look at loading performance and the Core Web Vitals, among other things. Google describes LCP, INP and CLS as the core metrics for how fast and stable a page feels. In the knowledge base we explain those metrics and how to interpret them yourself. If you also want a step-by-step plan to measure yourself, testing website speed is the logical next step. There you find how lab measurements relate to field data and where to cut first when LCP or CLS disappoint.

The mobile pillar tests viewport, font sizes and tap targets, among other things. Many sites that look fine on desktop fail here as soon as buttons are too small or sticky elements take half the screen. Our guide to a mobile-friendly website covers those patterns concretely. Speed and mobile often go together: heavy images and too much JavaScript hit phone users hardest. Teams that tackle both pillars at once usually win faster than teams that treat them as separate projects.

Security: HTTPS and headers

For security we check the SSL certificate, the HTTP-to-HTTPS redirect, and the presence of important security headers, among other things. A padlock alone is not enough. If HSTS is missing, or Content-Security-Policy is too loose or turned off entirely, you see that in the report. MDN and similar documentation describe what those headers do; our knowledge base translates that into what WebYes measures and how you fix it.

For a broader check on modern internet standards you can also use the Internet.nl website test alongside WebYes. It looks at TLS configuration and DNSSEC, among other things, and is a useful independent reference. WebYes stays focused on diagnosis within the four pillars plus fix direction in the report. Internet.nl remains useful when you want to verify more deeply whether your server stack follows current standards.

Accessibility, keurmerk and public register

The accessibility pillar tests machine-checkable criteria from WCAG 2.2 AA. Think alt texts, contrast, labels and focusable controls: things a crawler can flag without a full manual audit. Digital accessibility is broader than those automatic checks alone. In digital accessibility we explain how WCAG, statements and legal frameworks connect, and why a green score on automatic rules is not a substitute for a human review when that is required or desired.

The free scan is the first step. The paid keurmerk adds an embeddable badge, a public profile page and a re-audit cadence. Active paid orders are reassessed roughly every thirty days, so a badge does not sit still while the site declines. The public register lists only real paid, active orders, with an honest status such as certified, remediation in progress or assessment in progress. No fabricated counters, no sticker social proof. You can therefore show the register as an overview of sites that actually participate.

From free scan to full audit: what you get next

The free beta scan stays deliberately limited to six pages and lab measurements. That is enough to see whether HTTPS, viewport, Core Web Vitals signals and basic a11y fails push you under the pillar floor of 60. It is not meant as a full site crawl of hundreds of URLs. A paid keurmerk adds a full audit of up to fifteen pages, sitemap-led where possible, plus badge, public profile and periodic re-audit.

Use that step-up deliberately. Fix blockers from the free scan first, only re-scan within the sixty-minute dedupe window when you are ready, then choose the full audit when you want deeper templates (checkout, account, landing variants) included. That stops you paying for a wider sample while the homepage still fails on HSTS or contrast.

Also read how we assess in how we certify if you want to explain thresholds and the register to a client or colleague. The knowledge base remains the place for evergreen detail per pillar; this post stays the product announcement of the free scan.