solarfast.nl

Score over time

Every audit and re-audit counts: this is the average score per scan day.

Scan timeline

Pillar scores across recent scans. Methodology changes (different engine version) are noted on the point.

1. 8 August 2026 · Quick scan

   Engine unknown

   91Speed 100Security 84Mobile 100Accessibility 81

2. 1 August 2026 · Full audit

   Engine unknown

   92Speed 98Security 76Mobile 100Accessibility 92

3. 1 August 2026 · Full audit

   Engine unknown

   79Speed 62Security 76Mobile 100Accessibility 76

4. 1 August 2026 · Quick scan

   Engine unknown

   77Speed 62Security 79Mobile 100Accessibility 68

5. 31 July 2026 · Quick scan

   Engine unknown

   77Speed 62Security 79Mobile 100Accessibility 68

6. 9 July 2026 · Full audit

   94Speed 96Security 79Mobile 100Accessibility 100

7. 8 July 2026 · Full audit

   64Speed 30Security 79Mobile 100Accessibility 46

8. 8 July 2026 · Quick scan

   64Speed 31Security 79Mobile 100Accessibility 46

9. 8 July 2026 · Quick scan

   64Speed 31Security 79Mobile 100Accessibility 46

Full certification report

Part of the WebYes certification: beyond the four pillars we also audit SEO, structured data, content, links, privacy and AI findability. These extra categories do not count towards the certification score.

Findings

• ErrorAccessibilityAutomatically checked

  5 link(s) have no accessible name (no text, aria-label, or title).

  Add visible link text or aria-label to every <a> element so screen readers can announce the destination.

  How to fix it

  Some links have no readable name, usually icon links. Give them an aria-label or visually hidden text so a screen reader announces more than just 'link'.

  Read more in the knowledge base: WCAG guidelines →

• ErrorAccessibilityAutomatically checked

  1 focusable element(s) have aria-hidden="true", making them invisible to screen readers but still reachable via keyboard.

  Remove aria-hidden from focusable elements, or add tabindex="-1" to also remove them from the tab order.

  How to fix it

  Elements with aria-hidden="true" are still keyboard-focusable. Remove them from the tab order too (tabindex="-1") or hide them properly.

  Read more in the knowledge base: WCAG guidelines →

• WarningAccessibilityAutomatically checked

  7 image(s) with alt="" lack role="presentation" or aria-hidden="true".

  Mark decorative images explicitly: <img alt="" role="presentation"> or <img alt="" aria-hidden="true">.

  Read more in the knowledge base: WCAG guidelines →

• WarningSecurity

  CSP allows `'unsafe-inline'` without a nonce or hash — this effectively disables script-src protection against XSS.

  Generate a per-response nonce in your server-rendered pages and emit `script-src 'nonce-<nonce>' 'strict-dynamic'`. Inline `<script nonce='...'>` tags then load while attacker-injected ones don't.

  How to fix it

  Give inline scripts a nonce or hash in your CSP instead of allowing them via 'unsafe-inline'. Most frameworks (including Next.js) can generate per-request nonces.

  Read more in the knowledge base: Security headers →

• WarningContent

  Page has only 0 words (min 100).

  Thin pages risk being classified as low-value. Expand with original, useful content — lead each H2 with a self-contained 40-75 word answer, and add a visible FAQ/Q&A section covering common questions (no FAQPage schema needed; visible Q&A is what ranks and what AI Overviews cite). Or noindex if it's a utility page.

• WarningSpam signals

  Term "lees" appears unusually often (20×, 5% of words).

  Rewrite for natural language — repeated exact-match phrases can trigger spam classifiers.

• InfoSpeed

  Likely LCP image is missing `fetchpriority="high"`.

  Add `fetchpriority="high"` to the hero image (/_next/image?url=%2Fimages%2Frebrand%2Fcontact-hero.webp&w=1920&q=75) so the browser fetches it ahead of low-priority resources. Saves 100-300ms LCP on typical pages.

  How to fix it

  Prioritise your largest above-the-fold image with fetchpriority="high" or a preload link. The download then starts immediately instead of after the rest of the page.

  Read more in the knowledge base: Core Web Vitals →

• InfoSecurity

  Missing `Cross-Origin-Opener-Policy` + `Cross-Origin-Embedder-Policy`. Cross-origin isolation lets you use SharedArrayBuffer and high-resolution timers safely.

  Send `Cross-Origin-Opener-Policy: same-origin` and `Cross-Origin-Embedder-Policy: require-corp`. Note this requires every embedded resource to send `Cross-Origin-Resource-Policy`.

  How to fix it

  Add Cross-Origin-Opener-Policy: same-origin (and where possible Cross-Origin-Embedder-Policy). This isolates your site from windows opened by other origins.

  Read more in the knowledge base: Security headers →

• InfoOn-page SEO

  Title is slightly over the recommended length (64 chars, max 60).

  Borderline — Google usually still renders this in full. Trim only if the most important keywords sit past the visible cutoff.

• InfoOn-page SEO

  Meta description is slightly over the recommended length (180 chars, max 160).

• InfoOn-page SEO

  Heading level jumps from h1 to h3, skipping h2.

• InfoLinks

  Page uses 3 generic anchor(s) like "click here" / "lees meer".

  Use descriptive anchors that summarise the destination for users and search engines.

• InfoContent

  Text-to-HTML ratio is 0.7% (target ≥ 2%).

  Very low ratios usually mean the hydration payload, inline RSC blob or a vendor script is bigger than the rendered prose. Inspect the largest scripts and externalise or split them.

• InfoTechnical

  Crawl stopped at the max-pages limit (15); 69 sitemap URLs were not visited but might still be reachable.

  Re-run with `--max-pages 2000` (or higher) before trusting orphan-from-sitemap counts.

• InfoTechnical

  No HTML sitemap link found on the homepage. Placing one in the footer is an industry best practice for UX and crawler/AI discovery.

  Add a link to a user-facing HTML sitemap (e.g. `/sitemap`, not `sitemap.xml`) inside the <footer>. An HTML sitemap acts as a structural overview for lost visitors and as a fallback discovery surface for search engines and AI crawlers.

• InfoQuality impression

  Homepage has no `<link rel="icon">` — browsers will request /favicon.ico which may 404.

  Add a custom favicon that reflects your brand. A missing favicon causes extra 404 log noise and looks unprofessional in browser tabs and bookmarks.

• InfoPrivacy

  1 phone-shaped string(s) appear in main content. Examples: 020 250 46 70.

  If the phone numbers are intentional public contact info, ignore this finding. If they're personal numbers (employees, customer testimonials), redact or replace with a routing alias.

More from the register

Other websites holding an active WebYes certification. Every report is public and audited on the same four pillars.