Skip to content
https://duurzaam.woensdrecht.nl

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

77

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

Performance issues directly impact user engagement and conversion rates.

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.12796023790240202] map[node:map[boundingRect:map[bottom:1307 height:1056 left:0 right:1350 top:251 width:1350] lhId:page-4-MAIN nodeLabel:Home Ondernemen Energie Afval Mobiliteit Klimaatadaptatie Lees voor Uitleg woor… path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN selector:div > div#content > div.rUUhCG_contentWrapper > main#skip-links-content snippet:<main id="skip-links-content" class="cascada rUUhCG_contentContainer content-wrapper" style="scroll-margin: 5rem;"> type:node] score:0.08753113956746345 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://cuatro.sim-cdn.nl/assets/2.14.0/iconFonts/fontawesome6/webfonts/fa-solid-900.woff2]] map[cause:Web font extra:map[type:url value:https://cuatro.sim-cdn.nl/assets/2.14.0/iconFonts/opengemeenten/fonts/OpenGemeenten.woff2]] map[cause:Web font extra:map[type:url value:https://cuatro.sim-cdn.nl/assets/2.14.0/iconFonts/fontawesome6/webfonts/fa-brands-400.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:1765 height:1602 left:0 right:1350 top:163 width:1350] lhId:page-6-DIV nodeLabel:Terug naar Woensdrecht.nl Open toegankelijkheidsmenu Home Ondernemen Energie Af… path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV selector:body > div#__next > div#Qwixzq_wrapper > div snippet:<div> type:node] score:0.03679623062779091 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://cdn.jsdelivr.net/fontsource/fonts/poppins@5.3.0/latin-400-normal.woff2]] map[cause:Web font extra:map[type:url value:https://cdn.jsdelivr.net/fontsource/fonts/poppins@5.3.0/latin-700-normal.woff2]] map[cause:Web font extra:map[type:url value:https://cdn.jsdelivr.net/fontsource/fonts/poppins@5.3.0/latin-300-normal.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:1307 height:488 left:0 right:1350 top:819 width:1350] lhId:page-8-DIV nodeLabel:Uitgelicht Nationaal Isolatieprogramma (NIP) Zelf aan de slag Afval scheiden en… path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN,2,DIV selector:div#content > div.rUUhCG_contentWrapper > main#skip-links-content > div#toc-headings-scope snippet:<div id="toc-headings-scope" class="paragraphs ZH39Tq_grid"> type:node] score:0.003617021276595745 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:811 height:16 left:187 right:205 top:795 width:18] lhId:page-11-IMG nodeLabel:div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-tts > img path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,BUTTON,0,IMG selector:div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-tts > img snippet:<img alt="" src="data:image/svg+xml;utf8,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000…"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:819 height:32 left:464 right:606 top:787 width:143] lhId:page-9-BUTTON nodeLabel:Simpele tekst path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,BUTTON selector:div.lJsovG_tolkieButtons > div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-summary snippet:<button id="tolkie-separate-summary" class="tolkie-separate-btn" tabindex="0" type="button"> type:node] score:1.584643055190731e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:811 height:16 left:187 right:205 top:795 width:18] lhId:page-11-IMG nodeLabel:div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-tts > img path:1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,BUTTON,0,IMG selector:div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-tts > img snippet:<img alt="" src="data:image/svg+xml;utf8,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000…"> type:node]] map[cause:Web font extra:map[type:url value:https://app.tolkie.nl/fonts/atkinson-hyperlegible-next-latin-700-normal.woff2]]] type:subitems]]]

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
div.wVBtDW_colouredToptasks > div.JTuiDW_colouredToptasksDesignImage > picture > img div.wVBtDW_colouredToptasks > div.JTuiDW_colouredToptasksDesignImage > picture > img
/duurzaamwdrecht11c83f/uploads/styles/large_5x2_2560x1024...1.7 MiB1.6 MiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/duurzaamwdrecht11c83f/uploads/styles/teaser_16_9__6/medi...107.5 KiB98.0 KiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/duurzaamwdrecht11c83f/uploads/styles/teaser_16_9__6/medi...59.9 KiB50.4 KiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/duurzaamwdrecht11c83f/uploads/styles/teaser_16_9__6/medi...39.7 KiB31.2 KiB

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: div.wVBtDW_colouredToptasks > div.JTuiDW_colouredToptasksDesignImage > picture > img
path: 1,HTML,1,BODY,0,DIV,0,DIV,4,DIV,0,DIV,1,DIV,0,MAIN,1,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG
selector: div.wVBtDW_colouredToptasks > div.JTuiDW_colouredToptasksDesignImage > picture > img
snippet: <img src="https://cuatro.sim-cdn.nl/duurzaamwdrecht11c83f/uploads/styles/large_5x2_2…" alt="" width="2560" height="1024">

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

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Home Ondernemen Energie Afval Mobiliteit Klimaatadaptatie Lees voor Uitleg woor… div > div#content > div.rUUhCG_contentWrapper > main#skip-links-content
0.088
Terug naar Woensdrecht.nl Open toegankelijkheidsmenu Home Ondernemen Energie Af… body > div#__next > div#Qwixzq_wrapper > div
0.037
Uitgelicht Nationaal Isolatieprogramma (NIP) Zelf aan de slag Afval scheiden en… div#content > div.rUUhCG_contentWrapper > main#skip-links-content > div#toc-headings-scope
0.004
Simpele tekst div.lJsovG_tolkieButtons > div.tolkie-buttons-afterbegin > div#tolkie-separate-container > button#tolkie-separate-summary
0.000

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Document request latency
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 4 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.7 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 140 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 70 ms
○INP breakdown
○Avoid non-composited animations
97

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
We zijn op dit moment druk bezig met een aantal zaken op te ruimen en opnieuw t… div#Qwixzq_wrapper > section.SJqSlW_calamityMessage > div.content-wrapper > p

These are opportunities to improve the legibility of your content.

○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>`
●`[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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○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.
○`<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.
○Elements with visible text labels have matching accessible names.
○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.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●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
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

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

Send Feedback