Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
f1-eu.readspeaker.com/script/10077/webReader/webReader.js?pids=wr	0.0 ms	28.5 KiB
/script/10077/webReader/r/r2997/ReadSpeaker.Styles-Button...	86400.0 s	39.9 KiB
siteimproveanalytics.com/js/siteanalyze_6006099.js	86400.0 s	17.3 KiB

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.

URL	Est Savings
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-S...	175 ms
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/OpenSans-...	140 ms
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-R...	140 ms

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.

	URL	Resource Size	Est Savings
article > div.news-image > picture > img.img-fluid `article > div.news-image > picture > img.img-fluid`	/fileadmin/_processed_/e/9/csm_gemeente-huis-eens-van-de-...	103.1 KiB	93.3 KiB
article > div.news-image > picture > img.img-fluid `article > div.news-image > picture > img.img-fluid`	/fileadmin/_processed_/0/4/csm_waadhoeke_Fotografie_welzi...	85.4 KiB	75.6 KiB
article > div.news-image > picture > img.img-fluid `article > div.news-image > picture > img.img-fluid`	www.waadhoeke.nl/fileadmin/_processed_/e/4/csm_jdr_8313_4c0d63a726.jpg	64.9 KiB	55.1 KiB

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.waadhoeke.nl/	http/1.1
/typo3temp/assets/css/7015c8c4ac5ff815b57530b221005fc6.cs...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Css/styles.css?...	http/1.1
/_assets/901b4514440eb8fbfc3e64864b8e4928/Css/liveresults...	http/1.1
/fileadmin/_processed_/c/4/csm_homepage-inwoners-1920x900...	http/1.1
www.waadhoeke.nl/_assets/809ced9c7c6a07f38af363e0ce924e5d/Images/logo.svg	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/paspoor...	http/1.1
www.waadhoeke.nl/fileadmin/user_upload/paspoort1.svg	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/rijbewi...	http/1.1
www.waadhoeke.nl/fileadmin/user_upload/rijbewijs2.svg	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/locatie...	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/locatie...	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/bladere...	http/1.1
/fileadmin/bestanden/Afbeeldingen/Iconen_toptaken/bladere...	http/1.1
/fileadmin/_processed_/0/4/csm_waadhoeke_Fotografie_welzi...	http/1.1
www.waadhoeke.nl/fileadmin/_processed_/e/4/csm_jdr_8313_4c0d63a726.jpg	http/1.1
/fileadmin/_processed_/e/9/csm_gemeente-huis-eens-van-de-...	http/1.1
www.waadhoeke.nl/fileadmin/user_upload/facebook.svg	http/1.1
www.waadhoeke.nl/fileadmin/user_upload/instagram.svg	http/1.1
www.waadhoeke.nl/fileadmin/bestanden/Afbeeldingen/Logo_s/linkedin.svg	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/gene...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/fanc...	http/1.1
/_assets/901b4514440eb8fbfc3e64864b8e4928/JavaScript/live...	http/1.1
www.waadhoeke.nl/_assets/901b4514440eb8fbfc3e64864b8e4928/Images/spinner.svg	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Images/iconVoic...	http/1.1
www.waadhoeke.nl/_assets/809ced9c7c6a07f38af363e0ce924e5d/Images/icon-search.svg	http/1.1
www.waadhoeke.nl/_assets/809ced9c7c6a07f38af363e0ce924e5d/Images/arrow-right.svg	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/OpenSans-...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-S...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/OpenSans-...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/OpenSans-...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-S...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-B...	http/1.1
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Fonts/Poppins-R...	http/1.1
www.waadhoeke.nl/_assets/809ced9c7c6a07f38af363e0ce924e5d/Icons/favicon.svg	http/1.1

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

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.

URL	Transfer Size	Duration
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Css/styles.css?...	382.0 KiB	2.7 s
meldingen.fryslanveilig.nl/public/widget-style.css	1.1 KiB	830 ms
/_assets/901b4514440eb8fbfc3e64864b8e4928/Css/liveresults...	1.4 KiB	507 ms
/typo3temp/assets/css/7015c8c4ac5ff815b57530b221005fc6.cs...	3.8 KiB	170 ms

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

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 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: 2.4 s 388.4 KiB

URL	Transfer Size	Est Savings
/_assets/809ced9c7c6a07f38af363e0ce924e5d/Css/styles.css?...	381.6 KiB	353.3 KiB
/script/10077/webReader/r/r2997/ReadSpeaker.Styles-Button...	39.5 KiB	35.1 KiB

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.

Estimated savings: 1.9 s 392.7 KiB

URL	Transfer Size	Est Savings
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	249.0 KiB	222.6 KiB
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	78.6 KiB	64.6 KiB
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	85.5 KiB	53.5 KiB
/_assets/809ced9c7c6a07f38af363e0ce924e5d/JavaScript/Cont...	66.7 KiB	52.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 7.0 KiB

URL	Transfer Size	Est Savings
/_assets/901b4514440eb8fbfc3e64864b8e4928/JavaScript/live...	32.8 KiB	7.0 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Avoids enormous network payloads Total size was 2,221 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 2 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 90 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 150 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Welzijn op Recept: samen werken aan welzijn in Waadhoeke 10 november 2026 Soms… `div.news-home-outer > div.news-home-container > div.news-home > ul.newslist`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Goeiemiddei, `div.search > div.greeting > div#c9324 > 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

●Input buttons have discernible text.

●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

●ARIA toggle fields have accessible names

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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 `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○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 type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

●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

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Meer resultaten `div.row > div.search > div.search-results-box > a.autocomplete-more`

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`