Het keurmerkregister is open. Het keurmerkregister is open: controleer wie het WebYes-keurmerk draagt. Naar het register
Guides on speed, security, mobile and accessibility: the four pillars of the certification. Search a topic or browse the guides. Below the cards you will find how to use the hub.
12 articles

Core Web Vitals: LCP, INP and CLS and their thresholds
What do LCP, INP and CLS measure, which values are good and what changed with INP in 2024? Explained with thresholds and Google sources.

Digital accessibility: what is required for your website?
Who must be accessible (government, web shops), which WCAG version applies now and next, and how to measure and improve. With sources and checklist.

Testing website speed: how to measure load time properly
Test your website speed with lab and field data. Learn which tools to use, which values matter and how to make a slow site faster.

Website audit: what do you actually measure?
A website audit measures more than SEO. Learn what lab and field data do, where Lighthouse fits, and what WebYes does and does not certify.

Mobile-friendly website: requirements, target size and checklist
What a mobile-friendly website needs: viewport, readable text, tap targets of 24 or 44 pixels under WCAG 2.2 and how WebYes measures mobile.

SSL certificate: why your website needs HTTPS
An SSL certificate encrypts traffic between visitor and website. Read how HTTPS works, which certificate types exist and how to check your site.

Security headers: which ones does your website need?
Security headers protect visitors against eavesdropping, XSS and clickjacking. Find out which headers you need and how to set them up safely.

Content Security Policy: what does CSP do?
Content Security Policy (CSP) limits which scripts and resources your site may load. How CSP fights XSS, report-only vs enforce, and what WebYes checks.

What does the Internet.nl website test measure?
Independent website test for IPv6, DNSSEC and HTTPS. Learn what the score means and how it relates to WebYes.

WCAG 2.2: guidelines, levels and new criteria explained
What is WCAG 2.2, what is new compared to 2.1 and which version does the law require now? Levels A, AA, AAA, the six new A/AA criteria and how to test.

EAA: what the European Accessibility Act requires of your website
The EAA has applied to web shops since 28 June 2025. Which WCAG version, who is exempt, the duty to report to the ACM and how to start.

Accessibility statement: when required, what goes in it?
Government or web shop: when to publish an accessibility statement, what the ACM requires (also orally) and how it differs from the duty to report.
The WebYes knowledge base explains the terms that show up in the scan and the mark. Not a loose buzzword list, but guides that help you read a report: why LCP matters, what a security header does, when WCAG 2.2 AA applies, and how mobile-friendliness lands in the scorecard.
Each guide maps to at least one of the four pillars: speed, security, mobile and accessibility. Detail pages include definitions, working examples, FAQs and sources to primary documentation (W3C, web.dev, Digitoegankelijk, internet.nl).
Use the knowledge base before you optimise. First understand which pillar is holding you back, then change plugins or CDNs. That stops you spending days on cosmetic fixes while HTTPS or viewport still fails.
Search sits at the top. Type a term (for example CSP or Core Web Vitals) and cards filter live. Clear the query to return to the default layout: featured, guides and (where applicable) short terms.
Featured shows the guides that most often sit next to a first scan. Guides are longer explainers with steps and pitfalls. Terms are shorter definitions; that group fills as we publish term pages.
Each card links to a full SSR page with sources. The hub is the entry: choose the topic here, read the depth there. Internal links between guides (for example from speed testing to Core Web Vitals) live in those page texts.
The free scan scores the same four pillars as the mark. Average 80 or higher with no pillar below 60 and you qualify for the mark. The knowledge base turns those thresholds into plain language: what a security score of 58 means, or why mobile below 60 blocks the badge despite a high speed score.
Not all WCAG criteria can be assessed by a machine. That is also on the how-it-works page. Guides on WCAG, the European Accessibility Act and the accessibility statement explain where the machine stops and a human audit starts.
Security guides point to concrete headers (HSTS, CSP) and to internet.nl for Dutch internet standards. Speed guides stay close to Core Web Vitals (LCP, INP, CLS) as Google documents them, without promising lab scores equal field data.
Stay on the knowledge base when you need to grasp a term or a checklist before a redesign. Start the free scan when you want to know where your domain stands now. The scan does not replace the guides: it points at problems; the guides explain why those problems exist.
After a scan you typically open the guide for the weakest pillar. Security red from missing headers? Start with security headers and SSL. LCP too high? Read Core Web Vitals and website speed testing. That creates a short path from finding to fix.
For timely updates (product news, scan live, annual report) use the blog. The knowledge base stays evergreen: we revise guides when standards or our engine change, not to chase news.
Claims about standards link to primary sources. WCAG at the W3C, Web Vitals on web.dev, legal accessibility frames at Digitoegankelijk and ACM. WebYes product facts (six pages free, fifteen full, 80/60 thresholds, re-audit around thirty days) are product facts, not external citations.
We do not copy competitor copy and we do not fill a guide with generic AI padding. Each page should stand on its own for someone reading a report beside the guide.
Missing a term? Email [email protected] or use the contact form. New guides land here once they meet depth and source requirements.
Score under 80 or a pillar under 60? Open the guide for that pillar first, not every card at once. Note the top findings from the report (severity first) and search those terms in the hub search field.
When a fix clears a finding, rescan outside the sixty-minute dedupe window. If the score still sticks, read the how-it-works page on what the machine does not cover, especially accessibility. That stops endless tweaking on issues only a human audit can tick off.
For teams: share one guide URL per sprint item. The knowledge base is shared language between developer, marketer and owner, not a replacement for your issue tracker.
Is the knowledge base the same as the scan?
No. The scan measures your site. The knowledge base explains the metrics and duties behind that measurement. Use both: measure first, then read up.
Why do guides list sources at the bottom?
So you can verify claims at W3C, Google, Digitoegankelijk or internet.nl. A mark without traceable references is a sticker; the same rule applies to our explainers.
Do I need to read every guide before I scan?
No. Scan first if you want a quick read on where you stand. Then read the guide for the weakest pillar. The hub is searchable so you do not guess which page matters.
Do you update guides after engine updates?
Yes, when a check or threshold changes. Detail pages often show a substantive revision date. The hub always shows the current set of published guides.
How does this differ from the blog?
The blog is time-bound (launches, reports, product news). The knowledge base is evergreen explanation. Cross-links go both ways, but we do not repeat the same text one-to-one.