Skip to content
https://www.middelburg.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.

75

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.28886896588521144] map[node:map[boundingRect:map[bottom:2437 height:2050 left:0 right:1350 top:387 width:1350] lhId:page-8-DIV nodeLabel:Zodra er zoekresultaten zijn, gebruik de omhoog/omlaag toetsen om te navigeren … path:1,HTML,1,BODY,0,DIV,0,DIV,5,DIV selector:body > div#__next > div#Qwixzq_wrapper > div snippet:<div> type:node] score:0.2867361111111111 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:561 height:89 left:175 right:275 top:472 width:100] lhId:page-10-IMG nodeLabel:Logo gemeente Middelburg path:1,HTML,1,BODY,0,DIV,0,DIV,5,DIV,0,DIV,0,HEADER,0,DIV,1,DIV,0,DIV,0,DIV,0,A,0,PICTURE,0,IMG selector:div._94zGka_logoWrapper > a.active > picture > img.logo-img snippet:<img class="logo-img" width="153" height="136" src="https://cuatro.sim-cdn.nl/middelburg/uploads/2020-12/mb-01_oranje.svg?cb=U…" alt="Logo gemeente Middelburg"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:446 height:50 left:650 right:1103 top:396 width:453] lhId:page-4-DIV nodeLabel:Contact Inloggen mijn gemeente path:1,HTML,1,BODY,0,DIV,0,DIV,5,DIV,0,DIV,0,HEADER,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV selector:div.usl1zG_row > div.usl1zG_container > div._8dB19W_elementGroup > div.uDSJMa_quickLinks snippet:<div class="uDSJMa_quickLinks"> type:node] score:0.002132854774100342 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2203 height:133 left:866 right:1066 top:2070 width:200] lhId:page-9-IMG nodeLabel:Logo Europese Unie path:1,HTML,1,BODY,0,DIV,0,DIV,5,DIV,0,DIV,1,DIV,1,FOOTER,0,DIV,0,DIV,2,DIV,3,ARTICLE,0,ARTICLE,0,DIV,0,IMG selector:article.embedded-entity > article.media > div.field > img.image-style-wysiwyg-medium snippet:<img loading="lazy" src="https://cuatro.sim-cdn.nl/middelburg/uploads/styles/wysiwyg_medium/media/v…" width="200" height="133" alt="Logo Europese Unie" class="image-style-wysiwyg-medium HzBUIq_imageBorderRadius"> type:node]]] type:subitems]]]

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:55.84 source:map[type:text value:[unattributed]]]]

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
/middelburg/uploads/styles/large_5x2_2560x1024/media/Omsl...403.1 KiB284.4 KiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/middelburg/uploads/styles/teaser_16_9__6/media/Werkzaamh...80.4 KiB71.0 KiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/middelburg/uploads/styles/teaser_16_9__6/media/snoepgoed...54.7 KiB45.3 KiB
li.item > div.item-image > picture > img li.item > div.item-image > picture > img
/middelburg/uploads/styles/teaser_16_9__6/media/All of a ...48.3 KiB38.9 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,5,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/middelburg/uploads/styles/large_5x2_2560x1024/me…" 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.

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.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 36.8 KiB
URLTransfer SizeEst Savings
/script/13486/webReader/r/r2997/ReadSpeaker.Styles-Button...39.5 KiB36.8 KiB

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

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
Zodra er zoekresultaten zijn, gebruik de omhoog/omlaag toetsen om te navigeren … body > div#__next > div#Qwixzq_wrapper > div
0.287
Contact Inloggen mijn gemeente div.usl1zG_row > div.usl1zG_container > div._8dB19W_elementGroup > div.uDSJMa_quickLinks
0.002
●Time to Interactive 1.9 s
●Max Potential First Input Delay 80 ms
●Document request latency
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,064 KiB
●User Timing marks and measures 4 user timings
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 1 long task 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 150 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 80 ms
○INP breakdown
○Avoid non-composited animations
96

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
Cookie-instellingen aanpassen div.LEqDma_columnsWrapper > div.LEqDma_columns > div > button.KWL_kG_openCookieModalButton

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
●`[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
●Form elements have associated labels
●`[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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
96

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.

Description
ReferenceError: vrz_live_incident is not defined at <anonymous>:1:25 at <anonymous>:1:53 at insertNode (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:63:103) at moveNodes (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:65:250) at Object.fire (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:70:145) at h._doFire (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:35:728) at h.fire (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:35:873) at https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:32:868 at Object.setUp (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:71:117) at f.setUp (https://middelburg.logging.simanalytics.nl/js/container_UsuXOjCG.js:32:441)
●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 issues in the `Issues` panel in Chrome Devtools
●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
100

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.

○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback