Skip to content
Audit Complete

Results for https://xs4all.nl

Visit site
NL · EUR (€) · Estimated Applicable regulations: AVG · ePrivacy Directive · EAA Dev cost: €85/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 21, 2026 21:06 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C79

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon ELB · 120 peers
You 79
·
Avg 70
+9 above average
0 50 100
Better than 98% of Amazon ELB sites See full Amazon ELB benchmark →
Google Search Console · 2306 peers
You 79
·
Avg 73
+6 above average
0 50 100
Better than 92% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
5

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › 404 Error Page
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fxs4all.nl)](https://beavercheck.com/results/d0f00987-f0bc-4c8a-bbb6-9d5f188b30e4)
<a href="https://beavercheck.com/results/d0f00987-f0bc-4c8a-bbb6-9d5f188b30e4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fxs4all.nl" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fxs4all.nl

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

5 warning

5 barrier(s) likely increasing bounce by ~12%.

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€383 investment → €0.03/month returns + EUR 20,500,000 risk avoided

Payback period: > 2 years First-year ROI: -100%

Investment

€383

4h · 5 findings

Monthly returns

€0.03 /mo

~€0.31 / year

  • Bandwidth savings €0.03

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • AVG EUR 20,000,000
  • EAA EUR 500,000

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€383

4.5 developer hours at €85/hr

Based on Netherlands rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€1,708,333 / month at risk

~€20,500,000 / year if left unfixed

Compliance Risk

€20,500,000

AVGEAA
  • Privacy Policy not detected
    AVG: EUR 10,000 – EUR 20,000,000
  • No <main> landmark found
    EAA: EUR 1,000 – EUR 500,000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000

+3 more

Bandwidth Waste

€0.03 /mo

344.1 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~34 KB per page load
    Saves €0.03/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.85 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.00 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.85 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.00 s

Detailed Report

Audit breakdown by category with detailed findings.

98

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: header p53 side-right karima w2000
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,SECTION,0,DIV,0,IMG
selector: div.cms-open > section.masthead > div.masthead__image-wrapper > img.xs-image-lazy-loading
snippet: <img alt="header p53 side-right karima w2000" data-sizes="100vw" class="xs-image-lazy-loading masthead__image image--loaded masthead__image--loaded" rel="preload" srcset="/assets/images/header-karima-992px.webp 992w,/assets/images/header-karima-…" sizes="100vw" src="https://www.xs4all.nl/assets/images/header-karima-992px.webp">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
header-willemijn.jpg div.col-12 > div.image > div.image-wrapper > img.xs-image-lazy-loading
www.xs4all.nl/assets/images/header-willemijn-992px.webp
xs4all-kpn-samen_189x82.svg div.col-12 > div.image > div.image-wrapper > img.xs-image-lazy-loading
www.xs4all.nl/assets/images/xs4all-kpn.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 788 ms
URLTime Spent
xs4all.nl/788 ms
www.xs4all.nl/0.0 ms
Time to Interactive 2.0 s
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 112 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.3 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 0 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bestel bij KPN div.row > div.col-12 > span.button-wrapper > a.button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Waarmee kunnen wij u helpen? div.row > div.col-12 > div.text > h5
Vragen? div.main-footer__combined > div.main-footer__questions > div.main-footer__question > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MENU body > header#xs4all-main-header > div.main-header__wrapper > button.main-header__navigation-toggle
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!doctype html>Syntax not understood
2<html lang='nl'>Syntax not understood
3<head>Syntax not understood
4 <title>XS4ALL - First Class Internet</title>Syntax not understood
5 <meta charset="utf-8">Syntax not understood
6 <meta http-equiv="Content-Security-Policy" content="img-src 'self' https://www.xs4all.nl;">Unknown directive
7 <meta name="viewport" content="width=device-width, initial-scale=1">Syntax not understood
8 <meta name="description" content="XS4ALL First Class Internets, Televisie en Bellen. Voor veilig en betrouwbaar internet. Al jaren bekroond voor de allerbeste service.">Syntax not understood
9 <meta name="keywords" content="XS4ALL, Internet, Televisie, Bellen, service, veiligheid, privacy">Syntax not understood
10 <meta name="theme-color" content="#FFC300">Syntax not understood
11 <meta name="msapplication-TileColor" content="#2A2A20">Syntax not understood
12 <meta name="msapplication-TileImage" content="https://www.xs4all.nl/apple-touch-icon-144x144.png">Unknown directive
13 <meta name="fb:app_id" content="49320816941">Unknown directive
14 <meta property="og:image" content="/assets/images/logo-xs4all.svg">Unknown directive
15 <meta property="og:site_name" content="XS4ALL Klantenservice">Unknown directive
16 <meta property="og:locale" content="nl_NL">Unknown directive
17 <meta property="og:description" content="XS4ALL First Class Internets, Televisie en Bellen. Voor veilig en betrouwbaar internet. Al jaren bekroond voor de allerbeste service.">Unknown directive
18 <meta property="og:title" content="XS4ALL - First Class Internet">Unknown directive
19 <meta property="og:type" content="website">Unknown directive
20 <meta property="og:url" content="https://www.xs4all.nl/">Unknown directive
21 <link rel="shortcut icon" href="/favicon.ico">Syntax not understood
22 <link rel="icon" type="image/x-icon" href="/favicon.ico">Syntax not understood
23 <link rel="apple-touch-icon" sizes="57x57" href="/apple-touch-icon-57x57.png">Syntax not understood
24 <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png">Syntax not understood
25 <link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72x72.png">Syntax not understood
26 <link rel="apple-touch-icon" sizes="144x144" href="/apple-touch-icon-144x144.png">Syntax not understood
27 <link rel="apple-touch-icon" sizes="60x60" href="/apple-touch-icon-60x60.png">Syntax not understood
28 <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png">Syntax not understood
29 <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png">Syntax not understood
30 <link rel="apple-touch-icon" sizes="152x152" href="/apple-touch-icon-152x152.png">Syntax not understood
31 <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon-180x180.png">Syntax not understood
32 <link rel="icon" type="image/png" sizes="192x192" href="/favicon-192x192.png">Syntax not understood
33 <link rel="icon" type="image/png" sizes="160x160" href="/favicon-160x160.png">Syntax not understood
34 <link rel="icon" type="image/png" sizes="96x96" href="/favicon-96x96.png">Syntax not understood
35 <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">Syntax not understood
36 <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">Syntax not understood
37 <link href="/app.css" rel="stylesheet">Syntax not understood
38 <link href="/content.css" rel="stylesheet">Syntax not understood
39 <link href="/main-header.css" rel="stylesheet">Syntax not understood
40 <link href="/main-footer.css" rel="stylesheet">Syntax not understood
41</head>Syntax not understood
42<body>Syntax not understood
43 <header id="xs4all-main-header" class="main-header">Syntax not understood
44 <div class="main-header__wrapper">Syntax not understood
45 <div class="main-header__page-overlay"></div>Syntax not understood
46 <nav aria-label="XS4ALL" class="main-header__navigation">Syntax not understood
47 <ul class="main-header__navigation-list">Syntax not understood
48 <li class="main-header__navigation-item main-header__navigation-item--with-dropdown">Syntax not understood
49 <a data-toggle-button="" data-target="dropdown-Pakketten" href="#" class="main-header__navigation-link main-header__navigation-link--with-dropdown">Syntax not understood
50 PakkettenSyntax not understood
51 <svg class="icon icon--chevron-down" xmlns="http://www.w3.org/2000/svg" viewbox="0 0 10 10">Unknown directive
52 <path d="M9.71,3.36,5,8.06.29,3.36,1.71,1.94,5,5.24l3.29-3.3Z" class="white"></path>Syntax not understood
53 </svg>Syntax not understood
54 </a>Syntax not understood
55 <ul data-collapsed="true" id="dropdown-Pakketten" class="main-header__dropdown">Syntax not understood
56 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Overzicht</a></li>Unknown directive
57 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet</a></li>Unknown directive
58 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet &amp; Televisie</a></li>Unknown directive
59 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet/?actie=wifi&bellen=ja&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet &amp; Bellen</a></li>Unknown directive
60 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Alles-in-1</a></li>Unknown directive
61 <li class="main-header__navigation-item"><a href="https://www.kpn.com/zakelijk/kpn-een-mkb/shop/internet?campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Ondernemers</a></li>Unknown directive
62 </ul>Syntax not understood
63 </li>Syntax not understood
64 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Shop</a></li>Unknown directive
65 <li class="main-header__navigation-item"><a href="https://www.kpn.com/service/xs4all.htm" class="main-header__navigation-link">Service</a></li>Unknown directive
66 <li class="main-header__navigation-item main-header__navigation-item--secondary">Syntax not understood
67 <a href="https://webmail.xs4all.nl/?org=website/" class="main-header__navigation-link main-header__navigation-link--secondary">Webmail</a>Unknown directive
68 </li>Syntax not understood
69 <li class="main-header__navigation-item main-header__navigation-item--secondary">Syntax not understood
70 <a href="https://inloggen.kpn.com/#/overzicht" class="main-header__navigation-link main-header__navigation-link--secondary">Mijn KPN</a>Unknown directive
71 </li>Syntax not understood
72 </ul>Syntax not understood
73 </nav>Syntax not understood
74 <button type="button" data-toggle-navbar="" aria-label="Toggle navigation" aria-expanded="false" class="main-header__navigation-toggle">Syntax not understood
75 <i class="icon icon--hamburger">Syntax not understood
76 <span></span>Syntax not understood
77 <span></span>Syntax not understood
78 <span></span>Syntax not understood
79 </i>Syntax not understood
80 <span class="main-header__navigation-toggle-text">Syntax not understood
81 MENUSyntax not understood
82 </span>Syntax not understood
83 </button>Syntax not understood
84 <a href="/" class="main-header__logo">Syntax not understood
85 <img src="/assets/images/xs4all-emblem-yellow.svg" alt="XS4ALL Logo" width="111" height="39">Syntax not understood
86 </a>Syntax not understood
87 </div>Syntax not understood
88</header>Syntax not understood
90 <div class="content-wrapper content-wrapper--homepage">Syntax not understood
91 <div class="cms-open">Syntax not understood
92 <section data-ats-id="masthead-7wNUOk0MO6OcQuGv8I2MRG" class="masthead masthead--7wNUOk0MO6OcQuGv8I2MRG masthead--with-buttons masthead--with-arrow masthead--next-section-yellow masthead--medium masthead--black section--black">Syntax not understood
93 <div class="masthead__image-wrapper">Syntax not understood
94 <imgSyntax not understood
95 alt="header p53 side-right karima w2000"Syntax not understood
96 data-sizes="100vw"Syntax not understood
97 class="xs-image-lazy-loading masthead__image image--loaded masthead__image--loaded"Syntax not understood
98 rel="preload"Syntax not understood
99 srcset="/assets/images/header-karima-992px.webp 992w,/assets/images/header-karima-1280px.webp 1280w,/assets/images/header-karima-1600px.webp 1600w,/assets/images/header-karima-2000px.webp 2000w"Syntax not understood
100 sizes="100vw"Syntax not understood
101 src="/assets/images/header-karima.jpg"Syntax not understood
102 >Syntax not understood
103 </div>Syntax not understood
104 <div class="masthead__shadow"></div>Syntax not understood
105 <div class="container masthead__container">Syntax not understood
106 <div class="masthead__content">Syntax not understood
107 <h1 class="masthead__title">Syntax not understood
108 XS4ALL en KPNSyntax not understood
109 </h1>Syntax not understood
110 <h2 class="masthead__subtitle">Syntax not understood
111 Al meer dan 25 jaar de beste serviceSyntax not understood
112 </h2>Syntax not understood
113 <ul class="masthead__buttons list list--no-list-style">Syntax not understood
114 <li class="masthead__button">Syntax not understood
115 <span class="button-wrapper">Syntax not understood
116 <aSyntax not understood
117 aria-label="Bestel nu"Syntax not understood
118 href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN"Unknown directive
119 title="Bestel nu"Syntax not understood
120 class="button btn btn-primary"Syntax not understood
121 >Syntax not understood
122 Bestel nuSyntax not understood
123 </a>Syntax not understood
124 </span>Syntax not understood
125 </li>Syntax not understood
126 <li class="masthead__button">Syntax not understood
127 <span class="button-wrapper">Syntax not understood
128 <a aria-label="Ik ben klant" data-ats-id="button-ik-ben-al-klant" href="https://www.kpn.com/service/xs4all.htm" title="Ik ben klant" class="button btn btn-ghost-white">Unknown directive
129 Ik ben klantSyntax not understood
130 </a>Syntax not understood
131 </span>Syntax not understood
132 </li>Syntax not understood
133 </ul>Syntax not understood
134 </div>Syntax not understood
135 </div>Syntax not understood
136 </section>Syntax not understood
137 <section data-ats-id="section-columns-1iM8AMD67gRI5TIthk6c2p" class="section--yellow section--section-two-columns-provider-beste-service section--two-columns">Syntax not understood
138 <div class="container">Syntax not understood
139 <div class="row">Syntax not understood
140 <div class="col-12 col-md-8">Syntax not understood
141 <div class="text component component--block">Syntax not understood
142 <h2>Klant van XS4ALL?</h2>Syntax not understood
143 <h5>Waarmee kunnen wij u helpen?</h5>Syntax not understood
144 <p>Syntax not understood
145 E-mail instellen op uw nieuwe telefoon of een probleem met WiFi oplossen?&nbsp;We helpen&nbsp;u verder en zorgen voor een duurzame oplossing.Syntax not understood
146 </p>Syntax not understood
147 </div>Syntax not understood
148 <span class="button-wrapper component component--block">Syntax not understood
149 <aSyntax not understood
150 aria-label="Antwoord op uw vraag"Syntax not understood
151 data-ats-id="button-antwoord-op-uw-vraag"Syntax not understood
152 href="https://www.kpn.com/service/xs4all.htm"Unknown directive
153 title="Antwoord op uw vraag"Syntax not understood
154 class="button btn btn-primary"Syntax not understood
155 >Syntax not understood
156 Antwoord op uw vraagSyntax not understood
157 </a>Syntax not understood
158 </span>Syntax not understood
159 </div>Syntax not understood
160 <div class="col-12 col-md-4">Syntax not understood
161 <div class="image component component--block">Syntax not understood
162 <div class="image-wrapper">Syntax not understood
163 <imgSyntax not understood
164 alt="header-willemijn.jpg"Syntax not understood
165 data-sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
166 class="xs-image-lazy-loading image--loaded"Syntax not understood
167 srcset="/assets/images/header-willemijn-576px.webp 576w,/assets/images/header-willemijn-768px.webp 768w,/assets/images/header-willemijn-992px.webp 992w,/assets/images/header-willemijn-1200px.webp 1200w,/assets/images/header-willemijn-1600px.webp 1600w,/assets/images/header-willemijn-2000px.webp 2000w"Syntax not understood
168 sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
169 src="/assets/images/header-willemijn.jpg"Syntax not understood
170 >Syntax not understood
171 </div>Syntax not understood
172 </div>Syntax not understood
173 </div>Syntax not understood
174 </div>Syntax not understood
175 </div>Syntax not understood
176 </section>Syntax not understood
177 <section data-ats-id="section-columns-WEVzc0VmGz0UHd7hrklMC" class="section--black section--section-two-columns-xs4all-en-kpn-samen section--two-columns">Syntax not understood
178 <div class="container">Syntax not understood
179 <div class="row">Syntax not understood
180 <div class="col-12 col-md-4">Syntax not understood
181 <div class="image image--svg component component--block">Syntax not understood
182 <div class="image-wrapper">Syntax not understood
183 <imgSyntax not understood
184 alt="xs4all-kpn-samen_189x82.svg"Syntax not understood
185 data-sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
186 class="xs-image-lazy-loading image--loaded"Syntax not understood
187 sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
188 src="/assets/images/xs4all-kpn.svg"Syntax not understood
189 >Syntax not understood
190 </div>Syntax not understood
191 </div>Syntax not understood
192 </div>Syntax not understood
193 <div class="col-12 col-md-8">Syntax not understood
194 <div class="text component component--block">Syntax not understood
195 <h6>XS4ALL en KPN</h6>Syntax not understood
196 <p>Syntax not understood
197 Alles over de samenwerking tussen XS4ALL en KPN. Lees <a href="https://www.kpn.com/service/xs4all-overzicht.htm">hier</a> meer over de samenwerking.Unknown directive
198 </p>Syntax not understood
199 </div>Syntax not understood
200 </div>Syntax not understood
201 </div>Syntax not understood
202 </div>Syntax not understood
203 </section>Syntax not understood
204 <section data-ats-id="section-columns-TxlIxSYzg6BrTTUxMdxuK" class="section--white section--intro-home-stop-sales-20-dec section--one-column">Syntax not understood
205 <div class="container">Syntax not understood
206 <div class="row">Syntax not understood
207 <div class="col-12">Syntax not understood
208 <div class="text component component--block">Syntax not understood
209 <h2>Nieuwe abonnementen verkrijgbaar via KPN</h2>Syntax not understood
210 <p>Syntax not understood
211 Vanaf nu bieden we onze diensten aan via KPN. Bent u klant van XS4ALL? Dan kunt u gebruikSyntax not understood
212 blijven maken van onze diensten. Precies zoals u gewend bent.Syntax not understood
213 </p>Syntax not understood
214 </div>Syntax not understood
215 <span class="button-wrapper component component--block">Syntax not understood
216 <aSyntax not understood
217 aria-label="Bestel bij KPN "Syntax not understood
218 data-ats-id="button-bestel-bij-kpn"Syntax not understood
219 href="https://www.kpn.com/shop/internet-tv/internet-tv"Unknown directive
220 title="Bestel bij KPN "Syntax not understood
221 class="button btn btn-success"Syntax not understood
222 >Syntax not understood
223 Bestel bij KPNSyntax not understood
224 </a>Syntax not understood
225 </span>Syntax not understood
226 </div>Syntax not understood
227 </div>Syntax not understood
228 </div>Syntax not understood
229 </section>Syntax not understood
230 <section data-ats-id="section-columns-4WCdwam82v4lAWMaqFpFR2" class="section--yellow section--divider section--actueel-blog-en-contact section--three-columns">Syntax not understood
231 <div class="container">Syntax not understood
232 <div class="row">Syntax not understood
233 <div class="col-12 col-md-4">Syntax not understood
234 <div class="text component component--block">Syntax not understood
235 <h3>Werken bij XS4ALL</h3>Syntax not understood
236 <p>Syntax not understood
237 Heb jij een hart voor technologie en innovatie? Dan is een baan bij XS4ALL echt iets voor jou. Bekijk de vacatures bij <a href="https://www.randstad.nl/werknemers/vacatures/topwerkgevers/xs4all" rel="noreferrer noopener" target="_blank">Randstad Uitzendbureau</a> en bij <a href="https://www.youngcapital.nl/vacatures?utf8=%E2%9C%93&search%5Bzipcode_eq%5D=&search%5Bkeywords_scope%5D=xs4all&saved_job_search%5Bemail%5D=" rel="noreferrer noopener" target="_blank">YoungCapital</a>Unknown directive
238 </p>Syntax not understood
239 </div>Syntax not understood
240 </div>Syntax not understood
241 <div class="col-12 col-md-4">Syntax not understood
242 <span class="button-wrapper component component--block">Syntax not understood
243 <aSyntax not understood
244 aria-label="Ga naar het XS4ALL Blog"Syntax not understood
245 data-ats-id="button-ga-naar-het-xs4all-blog"Syntax not understood
246 href="https://www.kpn.com/beleef/xs4all.htm" target="_blank"Unknown directive
247 title="Ga naar het XS4ALL Blog"Syntax not understood
248 class="button btn btn-primary"Syntax not understood
249 >Syntax not understood
250 Ga naar het XS4ALL BlogSyntax not understood
251 </a>Syntax not understood
252 </span>Syntax not understood
253 </div>Syntax not understood
254 <div class="col-12 col-md-4">Syntax not understood
255 <div class="text component component--block">Syntax not understood
256 <h3>Vragen mag altijd</h3>Syntax not understood
257 <h4>Klantenservice</h4>Syntax not understood
258 <p>Syntax not understood
259 Heeft u vragen? Neem dan contact met op via telefoonnummer 020 398 76 66. We zijn iedere werkdag bereikbaar tussen 08.00 - 20.00 uur en op zaterdag tussen 10.00 - 17.00 uur.Syntax not understood
260 </p>Syntax not understood
261 </div>Syntax not understood
262 </div>Syntax not understood
263 </div>Syntax not understood
264 </div>Syntax not understood
265 </section>Syntax not understood
266 </div>Syntax not understood
267</div>Syntax not understood
269 <footer id="xs4all-main-footer" class="main-footer">Syntax not understood
270 <div class="main-footer__wrapper">Syntax not understood
271 <div class="main-footer__combined-wrapper">Syntax not understood
272 <div class="main-footer__combined">Syntax not understood
273 <div class="main-footer__social">Syntax not understood
274 <ul>Syntax not understood
275 <li>Syntax not understood
276 <a href="https://www.facebook.com/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-fb">Unknown directive
277 <span>Syntax not understood
278 Ons webcareteam <br>Syntax not understood
279 staat voor u klaarSyntax not understood
280 </span>Syntax not understood
281 </a>Syntax not understood
282 </li>Syntax not understood
283 <li>Syntax not understood
284 <a href="https://twitter.com/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-twitter">Unknown directive
285 <span>Syntax not understood
286 Ook via Twitter<br>Syntax not understood
287 helpen we u graagSyntax not understood
288 </span>Syntax not understood
289 </a>Syntax not understood
290 </li>Syntax not understood
291 <li>Syntax not understood
292 <a href="https://www.youtube.com/user/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-youtube">Unknown directive
293 <span>Syntax not understood
294 Tips bekijken op<br>Syntax not understood
295 ons YouTube-kanaalSyntax not understood
296 </span>Syntax not understood
297 </a>Syntax not understood
298 </li>Syntax not understood
299 <li>Syntax not understood
300 <a href="https://www.kpn.com/beleef/xs4all.htm" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-blog">Unknown directive
301 <span>Syntax not understood
302 Meer info<br>Syntax not understood
303 op onze blogSyntax not understood
304 </span>Syntax not understood
305 </a>Syntax not understood
306 </li>Syntax not understood
307 </ul>Syntax not understood
308 </div>Syntax not understood
309 <div class="main-footer__questions">Syntax not understood
310 <div class="main-footer__question">Syntax not understood
311 <h6>Vragen?</h6>Syntax not understood
312 Bekijk de <a href="https://www.kpn.com/service/xs4all.htm">veelgestelde vragen</a> of neem <a href="https://www.kpn.com/service/xs4all.htm">contact</a> met ons opUnknown directive
313 </div>Syntax not understood
314 <div class="main-footer__question">Syntax not understood
315 <h6>Storing en onderhoud</h6>Syntax not understood
316 Bekijk de <a href="https://www.kpn.com/service/storingen.htm">actuele storingen</a>Unknown directive
317 </div>Syntax not understood
318 </div>Syntax not understood
319 </div>Syntax not understood
320 </div>Syntax not understood
321 <div class="main-footer__other">Syntax not understood
322 <a href="https://www.xs4all.nl" class="main-footer__logo">Unknown directive
323 <img src="/assets/images/xs4all-emblem-yellow.svg" alt="XS4ALL Logo" width="87" height="31">Syntax not understood
324 </a>Syntax not understood
325 <ul>Syntax not understood
326 <li><a href="https://www.kpn.com/algemeen/alle-voorwaarden.htm" title="link.name">Algemene voorwaarden</a></li>Unknown directive
327 <li><a href="https://www.kpn.com/algemeen/missie-en-privacy-statement.htm" title="link.name">Privacy Statement</a></li>Unknown directive
328 <li><a href="https://www.kpn.com/algemeen/cookies.htm" title="link.name">Cookies</a></li>Unknown directive
329 <li><a href="https://www.overons.kpn/nl/het-bedrijf/onze-merken/xs4all" title="link.name">Over ons</a></li>Unknown directive
330 </ul>Syntax not understood
331 </div>Syntax not understood
332 </div>Syntax not understood
333</footer>Syntax not understood
335 <script type="text/javascript" src="/main-footer.js"></script>Syntax not understood
336 <script type="text/javascript" src="/main-header.js"></script>Syntax not understood
337</body>Syntax not understood
338</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
91
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

529 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

569 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

529 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

569 ms

Detailed Report

Audit breakdown by category with detailed findings.

100

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: header p53 side-right karima w2000
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,SECTION,0,DIV,0,IMG
selector: div.cms-open > section.masthead > div.masthead__image-wrapper > img.xs-image-lazy-loading
snippet: <img alt="header p53 side-right karima w2000" data-sizes="100vw" class="xs-image-lazy-loading masthead__image image--loaded masthead__image--loaded" rel="preload" srcset="/assets/images/header-karima-992px.webp 992w,/assets/images/header-karima-…" sizes="100vw" src="https://www.xs4all.nl/assets/images/header-karima-1600px.webp">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
header-willemijn.jpg div.col-12 > div.image > div.image-wrapper > img.xs-image-lazy-loading
www.xs4all.nl/assets/images/header-willemijn-1600px.webp31.2 KiB19.1 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
header-willemijn.jpg div.col-12 > div.image > div.image-wrapper > img.xs-image-lazy-loading
www.xs4all.nl/assets/images/header-willemijn-1600px.webp
xs4all-kpn-samen_189x82.svg div.col-12 > div.image > div.image-wrapper > img.xs-image-lazy-loading
www.xs4all.nl/assets/images/xs4all-kpn.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 240 ms
URLTime Spent
xs4all.nl/240 ms
www.xs4all.nl/0.0 ms
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Time to Interactive 0.6 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Reduce unused JavaScript
Avoids enormous network payloads Total size was 135 KiB
Minimizes main-thread work 0.1 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 0 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 10 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
JavaScript execution time
Avoid long main-thread tasks
Avoid non-composited animations
91

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bestel bij KPN div.row > div.col-12 > span.button-wrapper > a.button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Waarmee kunnen wij u helpen? div.row > div.col-12 > div.text > h5
Vragen? div.main-footer__combined > div.main-footer__questions > div.main-footer__question > h6

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
Detected JavaScript libraries
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!doctype html>Syntax not understood
2<html lang='nl'>Syntax not understood
3<head>Syntax not understood
4 <title>XS4ALL - First Class Internet</title>Syntax not understood
5 <meta charset="utf-8">Syntax not understood
6 <meta http-equiv="Content-Security-Policy" content="img-src 'self' https://www.xs4all.nl;">Unknown directive
7 <meta name="viewport" content="width=device-width, initial-scale=1">Syntax not understood
8 <meta name="description" content="XS4ALL First Class Internets, Televisie en Bellen. Voor veilig en betrouwbaar internet. Al jaren bekroond voor de allerbeste service.">Syntax not understood
9 <meta name="keywords" content="XS4ALL, Internet, Televisie, Bellen, service, veiligheid, privacy">Syntax not understood
10 <meta name="theme-color" content="#FFC300">Syntax not understood
11 <meta name="msapplication-TileColor" content="#2A2A20">Syntax not understood
12 <meta name="msapplication-TileImage" content="https://www.xs4all.nl/apple-touch-icon-144x144.png">Unknown directive
13 <meta name="fb:app_id" content="49320816941">Unknown directive
14 <meta property="og:image" content="/assets/images/logo-xs4all.svg">Unknown directive
15 <meta property="og:site_name" content="XS4ALL Klantenservice">Unknown directive
16 <meta property="og:locale" content="nl_NL">Unknown directive
17 <meta property="og:description" content="XS4ALL First Class Internets, Televisie en Bellen. Voor veilig en betrouwbaar internet. Al jaren bekroond voor de allerbeste service.">Unknown directive
18 <meta property="og:title" content="XS4ALL - First Class Internet">Unknown directive
19 <meta property="og:type" content="website">Unknown directive
20 <meta property="og:url" content="https://www.xs4all.nl/">Unknown directive
21 <link rel="shortcut icon" href="/favicon.ico">Syntax not understood
22 <link rel="icon" type="image/x-icon" href="/favicon.ico">Syntax not understood
23 <link rel="apple-touch-icon" sizes="57x57" href="/apple-touch-icon-57x57.png">Syntax not understood
24 <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114x114.png">Syntax not understood
25 <link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-72x72.png">Syntax not understood
26 <link rel="apple-touch-icon" sizes="144x144" href="/apple-touch-icon-144x144.png">Syntax not understood
27 <link rel="apple-touch-icon" sizes="60x60" href="/apple-touch-icon-60x60.png">Syntax not understood
28 <link rel="apple-touch-icon" sizes="120x120" href="/apple-touch-icon-120x120.png">Syntax not understood
29 <link rel="apple-touch-icon" sizes="76x76" href="/apple-touch-icon-76x76.png">Syntax not understood
30 <link rel="apple-touch-icon" sizes="152x152" href="/apple-touch-icon-152x152.png">Syntax not understood
31 <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon-180x180.png">Syntax not understood
32 <link rel="icon" type="image/png" sizes="192x192" href="/favicon-192x192.png">Syntax not understood
33 <link rel="icon" type="image/png" sizes="160x160" href="/favicon-160x160.png">Syntax not understood
34 <link rel="icon" type="image/png" sizes="96x96" href="/favicon-96x96.png">Syntax not understood
35 <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">Syntax not understood
36 <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">Syntax not understood
37 <link href="/app.css" rel="stylesheet">Syntax not understood
38 <link href="/content.css" rel="stylesheet">Syntax not understood
39 <link href="/main-header.css" rel="stylesheet">Syntax not understood
40 <link href="/main-footer.css" rel="stylesheet">Syntax not understood
41</head>Syntax not understood
42<body>Syntax not understood
43 <header id="xs4all-main-header" class="main-header">Syntax not understood
44 <div class="main-header__wrapper">Syntax not understood
45 <div class="main-header__page-overlay"></div>Syntax not understood
46 <nav aria-label="XS4ALL" class="main-header__navigation">Syntax not understood
47 <ul class="main-header__navigation-list">Syntax not understood
48 <li class="main-header__navigation-item main-header__navigation-item--with-dropdown">Syntax not understood
49 <a data-toggle-button="" data-target="dropdown-Pakketten" href="#" class="main-header__navigation-link main-header__navigation-link--with-dropdown">Syntax not understood
50 PakkettenSyntax not understood
51 <svg class="icon icon--chevron-down" xmlns="http://www.w3.org/2000/svg" viewbox="0 0 10 10">Unknown directive
52 <path d="M9.71,3.36,5,8.06.29,3.36,1.71,1.94,5,5.24l3.29-3.3Z" class="white"></path>Syntax not understood
53 </svg>Syntax not understood
54 </a>Syntax not understood
55 <ul data-collapsed="true" id="dropdown-Pakketten" class="main-header__dropdown">Syntax not understood
56 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Overzicht</a></li>Unknown directive
57 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet</a></li>Unknown directive
58 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet &amp; Televisie</a></li>Unknown directive
59 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet/?actie=wifi&bellen=ja&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Internet &amp; Bellen</a></li>Unknown directive
60 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Alles-in-1</a></li>Unknown directive
61 <li class="main-header__navigation-item"><a href="https://www.kpn.com/zakelijk/kpn-een-mkb/shop/internet?campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Ondernemers</a></li>Unknown directive
62 </ul>Syntax not understood
63 </li>Syntax not understood
64 <li class="main-header__navigation-item"><a href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN" class="main-header__navigation-link">Shop</a></li>Unknown directive
65 <li class="main-header__navigation-item"><a href="https://www.kpn.com/service/xs4all.htm" class="main-header__navigation-link">Service</a></li>Unknown directive
66 <li class="main-header__navigation-item main-header__navigation-item--secondary">Syntax not understood
67 <a href="https://webmail.xs4all.nl/?org=website/" class="main-header__navigation-link main-header__navigation-link--secondary">Webmail</a>Unknown directive
68 </li>Syntax not understood
69 <li class="main-header__navigation-item main-header__navigation-item--secondary">Syntax not understood
70 <a href="https://inloggen.kpn.com/#/overzicht" class="main-header__navigation-link main-header__navigation-link--secondary">Mijn KPN</a>Unknown directive
71 </li>Syntax not understood
72 </ul>Syntax not understood
73 </nav>Syntax not understood
74 <button type="button" data-toggle-navbar="" aria-label="Toggle navigation" aria-expanded="false" class="main-header__navigation-toggle">Syntax not understood
75 <i class="icon icon--hamburger">Syntax not understood
76 <span></span>Syntax not understood
77 <span></span>Syntax not understood
78 <span></span>Syntax not understood
79 </i>Syntax not understood
80 <span class="main-header__navigation-toggle-text">Syntax not understood
81 MENUSyntax not understood
82 </span>Syntax not understood
83 </button>Syntax not understood
84 <a href="/" class="main-header__logo">Syntax not understood
85 <img src="/assets/images/xs4all-emblem-yellow.svg" alt="XS4ALL Logo" width="111" height="39">Syntax not understood
86 </a>Syntax not understood
87 </div>Syntax not understood
88</header>Syntax not understood
90 <div class="content-wrapper content-wrapper--homepage">Syntax not understood
91 <div class="cms-open">Syntax not understood
92 <section data-ats-id="masthead-7wNUOk0MO6OcQuGv8I2MRG" class="masthead masthead--7wNUOk0MO6OcQuGv8I2MRG masthead--with-buttons masthead--with-arrow masthead--next-section-yellow masthead--medium masthead--black section--black">Syntax not understood
93 <div class="masthead__image-wrapper">Syntax not understood
94 <imgSyntax not understood
95 alt="header p53 side-right karima w2000"Syntax not understood
96 data-sizes="100vw"Syntax not understood
97 class="xs-image-lazy-loading masthead__image image--loaded masthead__image--loaded"Syntax not understood
98 rel="preload"Syntax not understood
99 srcset="/assets/images/header-karima-992px.webp 992w,/assets/images/header-karima-1280px.webp 1280w,/assets/images/header-karima-1600px.webp 1600w,/assets/images/header-karima-2000px.webp 2000w"Syntax not understood
100 sizes="100vw"Syntax not understood
101 src="/assets/images/header-karima.jpg"Syntax not understood
102 >Syntax not understood
103 </div>Syntax not understood
104 <div class="masthead__shadow"></div>Syntax not understood
105 <div class="container masthead__container">Syntax not understood
106 <div class="masthead__content">Syntax not understood
107 <h1 class="masthead__title">Syntax not understood
108 XS4ALL en KPNSyntax not understood
109 </h1>Syntax not understood
110 <h2 class="masthead__subtitle">Syntax not understood
111 Al meer dan 25 jaar de beste serviceSyntax not understood
112 </h2>Syntax not understood
113 <ul class="masthead__buttons list list--no-list-style">Syntax not understood
114 <li class="masthead__button">Syntax not understood
115 <span class="button-wrapper">Syntax not understood
116 <aSyntax not understood
117 aria-label="Bestel nu"Syntax not understood
118 href="https://www.kpn.com/shop/internet-tv/internet-tv/?actie=wifi&product=techdesk&campaignid=tp:b=kpn:mk=cm:c=XS4ALLHussel:s=XS4ALL+over+Hussel:cd=Meer+over+KPN+Hussel:d=18112020:st=acq:e=button:f1=Meer+over+KPN"Unknown directive
119 title="Bestel nu"Syntax not understood
120 class="button btn btn-primary"Syntax not understood
121 >Syntax not understood
122 Bestel nuSyntax not understood
123 </a>Syntax not understood
124 </span>Syntax not understood
125 </li>Syntax not understood
126 <li class="masthead__button">Syntax not understood
127 <span class="button-wrapper">Syntax not understood
128 <a aria-label="Ik ben klant" data-ats-id="button-ik-ben-al-klant" href="https://www.kpn.com/service/xs4all.htm" title="Ik ben klant" class="button btn btn-ghost-white">Unknown directive
129 Ik ben klantSyntax not understood
130 </a>Syntax not understood
131 </span>Syntax not understood
132 </li>Syntax not understood
133 </ul>Syntax not understood
134 </div>Syntax not understood
135 </div>Syntax not understood
136 </section>Syntax not understood
137 <section data-ats-id="section-columns-1iM8AMD67gRI5TIthk6c2p" class="section--yellow section--section-two-columns-provider-beste-service section--two-columns">Syntax not understood
138 <div class="container">Syntax not understood
139 <div class="row">Syntax not understood
140 <div class="col-12 col-md-8">Syntax not understood
141 <div class="text component component--block">Syntax not understood
142 <h2>Klant van XS4ALL?</h2>Syntax not understood
143 <h5>Waarmee kunnen wij u helpen?</h5>Syntax not understood
144 <p>Syntax not understood
145 E-mail instellen op uw nieuwe telefoon of een probleem met WiFi oplossen?&nbsp;We helpen&nbsp;u verder en zorgen voor een duurzame oplossing.Syntax not understood
146 </p>Syntax not understood
147 </div>Syntax not understood
148 <span class="button-wrapper component component--block">Syntax not understood
149 <aSyntax not understood
150 aria-label="Antwoord op uw vraag"Syntax not understood
151 data-ats-id="button-antwoord-op-uw-vraag"Syntax not understood
152 href="https://www.kpn.com/service/xs4all.htm"Unknown directive
153 title="Antwoord op uw vraag"Syntax not understood
154 class="button btn btn-primary"Syntax not understood
155 >Syntax not understood
156 Antwoord op uw vraagSyntax not understood
157 </a>Syntax not understood
158 </span>Syntax not understood
159 </div>Syntax not understood
160 <div class="col-12 col-md-4">Syntax not understood
161 <div class="image component component--block">Syntax not understood
162 <div class="image-wrapper">Syntax not understood
163 <imgSyntax not understood
164 alt="header-willemijn.jpg"Syntax not understood
165 data-sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
166 class="xs-image-lazy-loading image--loaded"Syntax not understood
167 srcset="/assets/images/header-willemijn-576px.webp 576w,/assets/images/header-willemijn-768px.webp 768w,/assets/images/header-willemijn-992px.webp 992w,/assets/images/header-willemijn-1200px.webp 1200w,/assets/images/header-willemijn-1600px.webp 1600w,/assets/images/header-willemijn-2000px.webp 2000w"Syntax not understood
168 sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
169 src="/assets/images/header-willemijn.jpg"Syntax not understood
170 >Syntax not understood
171 </div>Syntax not understood
172 </div>Syntax not understood
173 </div>Syntax not understood
174 </div>Syntax not understood
175 </div>Syntax not understood
176 </section>Syntax not understood
177 <section data-ats-id="section-columns-WEVzc0VmGz0UHd7hrklMC" class="section--black section--section-two-columns-xs4all-en-kpn-samen section--two-columns">Syntax not understood
178 <div class="container">Syntax not understood
179 <div class="row">Syntax not understood
180 <div class="col-12 col-md-4">Syntax not understood
181 <div class="image image--svg component component--block">Syntax not understood
182 <div class="image-wrapper">Syntax not understood
183 <imgSyntax not understood
184 alt="xs4all-kpn-samen_189x82.svg"Syntax not understood
185 data-sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
186 class="xs-image-lazy-loading image--loaded"Syntax not understood
187 sizes="(max-width: 576px) 510px,(max-width: 768px) 690px,(max-width: 992px) 930px,(max-width: 1200px) 1110px,(max-width: 1600px) 1600px,(max-width: 2000px) 2000px,"Unknown directive
188 src="/assets/images/xs4all-kpn.svg"Syntax not understood
189 >Syntax not understood
190 </div>Syntax not understood
191 </div>Syntax not understood
192 </div>Syntax not understood
193 <div class="col-12 col-md-8">Syntax not understood
194 <div class="text component component--block">Syntax not understood
195 <h6>XS4ALL en KPN</h6>Syntax not understood
196 <p>Syntax not understood
197 Alles over de samenwerking tussen XS4ALL en KPN. Lees <a href="https://www.kpn.com/service/xs4all-overzicht.htm">hier</a> meer over de samenwerking.Unknown directive
198 </p>Syntax not understood
199 </div>Syntax not understood
200 </div>Syntax not understood
201 </div>Syntax not understood
202 </div>Syntax not understood
203 </section>Syntax not understood
204 <section data-ats-id="section-columns-TxlIxSYzg6BrTTUxMdxuK" class="section--white section--intro-home-stop-sales-20-dec section--one-column">Syntax not understood
205 <div class="container">Syntax not understood
206 <div class="row">Syntax not understood
207 <div class="col-12">Syntax not understood
208 <div class="text component component--block">Syntax not understood
209 <h2>Nieuwe abonnementen verkrijgbaar via KPN</h2>Syntax not understood
210 <p>Syntax not understood
211 Vanaf nu bieden we onze diensten aan via KPN. Bent u klant van XS4ALL? Dan kunt u gebruikSyntax not understood
212 blijven maken van onze diensten. Precies zoals u gewend bent.Syntax not understood
213 </p>Syntax not understood
214 </div>Syntax not understood
215 <span class="button-wrapper component component--block">Syntax not understood
216 <aSyntax not understood
217 aria-label="Bestel bij KPN "Syntax not understood
218 data-ats-id="button-bestel-bij-kpn"Syntax not understood
219 href="https://www.kpn.com/shop/internet-tv/internet-tv"Unknown directive
220 title="Bestel bij KPN "Syntax not understood
221 class="button btn btn-success"Syntax not understood
222 >Syntax not understood
223 Bestel bij KPNSyntax not understood
224 </a>Syntax not understood
225 </span>Syntax not understood
226 </div>Syntax not understood
227 </div>Syntax not understood
228 </div>Syntax not understood
229 </section>Syntax not understood
230 <section data-ats-id="section-columns-4WCdwam82v4lAWMaqFpFR2" class="section--yellow section--divider section--actueel-blog-en-contact section--three-columns">Syntax not understood
231 <div class="container">Syntax not understood
232 <div class="row">Syntax not understood
233 <div class="col-12 col-md-4">Syntax not understood
234 <div class="text component component--block">Syntax not understood
235 <h3>Werken bij XS4ALL</h3>Syntax not understood
236 <p>Syntax not understood
237 Heb jij een hart voor technologie en innovatie? Dan is een baan bij XS4ALL echt iets voor jou. Bekijk de vacatures bij <a href="https://www.randstad.nl/werknemers/vacatures/topwerkgevers/xs4all" rel="noreferrer noopener" target="_blank">Randstad Uitzendbureau</a> en bij <a href="https://www.youngcapital.nl/vacatures?utf8=%E2%9C%93&search%5Bzipcode_eq%5D=&search%5Bkeywords_scope%5D=xs4all&saved_job_search%5Bemail%5D=" rel="noreferrer noopener" target="_blank">YoungCapital</a>Unknown directive
238 </p>Syntax not understood
239 </div>Syntax not understood
240 </div>Syntax not understood
241 <div class="col-12 col-md-4">Syntax not understood
242 <span class="button-wrapper component component--block">Syntax not understood
243 <aSyntax not understood
244 aria-label="Ga naar het XS4ALL Blog"Syntax not understood
245 data-ats-id="button-ga-naar-het-xs4all-blog"Syntax not understood
246 href="https://www.kpn.com/beleef/xs4all.htm" target="_blank"Unknown directive
247 title="Ga naar het XS4ALL Blog"Syntax not understood
248 class="button btn btn-primary"Syntax not understood
249 >Syntax not understood
250 Ga naar het XS4ALL BlogSyntax not understood
251 </a>Syntax not understood
252 </span>Syntax not understood
253 </div>Syntax not understood
254 <div class="col-12 col-md-4">Syntax not understood
255 <div class="text component component--block">Syntax not understood
256 <h3>Vragen mag altijd</h3>Syntax not understood
257 <h4>Klantenservice</h4>Syntax not understood
258 <p>Syntax not understood
259 Heeft u vragen? Neem dan contact met op via telefoonnummer 020 398 76 66. We zijn iedere werkdag bereikbaar tussen 08.00 - 20.00 uur en op zaterdag tussen 10.00 - 17.00 uur.Syntax not understood
260 </p>Syntax not understood
261 </div>Syntax not understood
262 </div>Syntax not understood
263 </div>Syntax not understood
264 </div>Syntax not understood
265 </section>Syntax not understood
266 </div>Syntax not understood
267</div>Syntax not understood
269 <footer id="xs4all-main-footer" class="main-footer">Syntax not understood
270 <div class="main-footer__wrapper">Syntax not understood
271 <div class="main-footer__combined-wrapper">Syntax not understood
272 <div class="main-footer__combined">Syntax not understood
273 <div class="main-footer__social">Syntax not understood
274 <ul>Syntax not understood
275 <li>Syntax not understood
276 <a href="https://www.facebook.com/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-fb">Unknown directive
277 <span>Syntax not understood
278 Ons webcareteam <br>Syntax not understood
279 staat voor u klaarSyntax not understood
280 </span>Syntax not understood
281 </a>Syntax not understood
282 </li>Syntax not understood
283 <li>Syntax not understood
284 <a href="https://twitter.com/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-twitter">Unknown directive
285 <span>Syntax not understood
286 Ook via Twitter<br>Syntax not understood
287 helpen we u graagSyntax not understood
288 </span>Syntax not understood
289 </a>Syntax not understood
290 </li>Syntax not understood
291 <li>Syntax not understood
292 <a href="https://www.youtube.com/user/xs4all" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-youtube">Unknown directive
293 <span>Syntax not understood
294 Tips bekijken op<br>Syntax not understood
295 ons YouTube-kanaalSyntax not understood
296 </span>Syntax not understood
297 </a>Syntax not understood
298 </li>Syntax not understood
299 <li>Syntax not understood
300 <a href="https://www.kpn.com/beleef/xs4all.htm" target="_blank" rel="noreferrer noopener" class="main-footer__social-icon main-footer__social-icon-blog">Unknown directive
301 <span>Syntax not understood
302 Meer info<br>Syntax not understood
303 op onze blogSyntax not understood
304 </span>Syntax not understood
305 </a>Syntax not understood
306 </li>Syntax not understood
307 </ul>Syntax not understood
308 </div>Syntax not understood
309 <div class="main-footer__questions">Syntax not understood
310 <div class="main-footer__question">Syntax not understood
311 <h6>Vragen?</h6>Syntax not understood
312 Bekijk de <a href="https://www.kpn.com/service/xs4all.htm">veelgestelde vragen</a> of neem <a href="https://www.kpn.com/service/xs4all.htm">contact</a> met ons opUnknown directive
313 </div>Syntax not understood
314 <div class="main-footer__question">Syntax not understood
315 <h6>Storing en onderhoud</h6>Syntax not understood
316 Bekijk de <a href="https://www.kpn.com/service/storingen.htm">actuele storingen</a>Unknown directive
317 </div>Syntax not understood
318 </div>Syntax not understood
319 </div>Syntax not understood
320 </div>Syntax not understood
321 <div class="main-footer__other">Syntax not understood
322 <a href="https://www.xs4all.nl" class="main-footer__logo">Unknown directive
323 <img src="/assets/images/xs4all-emblem-yellow.svg" alt="XS4ALL Logo" width="87" height="31">Syntax not understood
324 </a>Syntax not understood
325 <ul>Syntax not understood
326 <li><a href="https://www.kpn.com/algemeen/alle-voorwaarden.htm" title="link.name">Algemene voorwaarden</a></li>Unknown directive
327 <li><a href="https://www.kpn.com/algemeen/missie-en-privacy-statement.htm" title="link.name">Privacy Statement</a></li>Unknown directive
328 <li><a href="https://www.kpn.com/algemeen/cookies.htm" title="link.name">Cookies</a></li>Unknown directive
329 <li><a href="https://www.overons.kpn/nl/het-bedrijf/onze-merken/xs4all" title="link.name">Over ons</a></li>Unknown directive
330 </ul>Syntax not understood
331 </div>Syntax not understood
332 </div>Syntax not understood
333</footer>Syntax not understood
335 <script type="text/javascript" src="/main-footer.js"></script>Syntax not understood
336 <script type="text/javascript" src="/main-header.js"></script>Syntax not understood
337</body>Syntax not understood
338</html>Syntax not understood

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback