Skip to content
https://dovendi.com

Lighthouse Mobile

· 0 checks — Mobile 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.

69

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.

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.

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
Dovendi Staal Logo Op Muur section.py-10 > div.container > div.image-masked > img
/img/22fa0e78-b8de-43d0-8b8c-e1cd7c674fef/dovendi-staal-l...697.1 KiB587.8 KiB
2cu 012thijmen div.container > div.relative > div.image-masked > img
/img/70e17330-de10-409b-a3bd-79c588aa0f23/2cu-012thijmen....363.4 KiB235.5 KiB
Foto Lianne Van Hoorn Sedo div.container > div.relative > div.image-masked > img
/img/4426b8a8-b24a-4ca2-810a-3440505089e8/foto-lianne-van...140.0 KiB39.1 KiB
div.text-logo-slider > div.swiper-wrapper > div.swiper-slide > img.object-contain div.text-logo-slider > div.swiper-wrapper > div.swiper-slide > img.object-contain
/storage/uploads/af4dbd90-c876-4627-b2bb-3072500fef5a/sed...7.7 KiB5.3 KiB
app logo div.px-6 > div.footer-head > a.app-logo > img
/storage/uploads/7442ae43-dd3e-46f6-855a-78a3c3fbf54a/log...5.4 KiB4.3 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: Dovendi Staal Logo Op Muur
path: 1,HTML,1,BODY,0,DIV,4,MAIN,0,SECTION,0,DIV,1,DIV,0,IMG
selector: section.py-10 > div.container > div.image-masked > img
snippet: <img src="https://dovendi.com/img/22fa0e78-b8de-43d0-8b8c-e1cd7c674fef/dovendi-staal…" alt="Dovendi Staal Logo Op Muur">

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.

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: 812 ms
URLTime Spent
dovendi.com/812 ms
dovendi.com/en0.0 ms

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.

Estimated savings: 490 ms 278.6 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.1 s
Other674 ms
Style & Layout360 ms
Script Parsing & Compilation128 ms
Rendering107 ms
Parse HTML & CSS40 ms

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
div.container > div.relative > div.absolute > img.max-h-[30px] div.container > div.relative > div.absolute > img.max-h-[30px]
/storage/uploads/64d6faf0-a0e0-49d0-b2cf-fe860086e873/2cu...
div.container > div.relative > div.absolute > img.max-h-[30px] div.container > div.relative > div.absolute > img.max-h-[30px]
/storage/uploads/af4dbd90-c876-4627-b2bb-3072500fef5a/sed...
app logo div.container > div.flex > a.app-logo > img
/storage/uploads/7442ae43-dd3e-46f6-855a-78a3c3fbf54a/log...
app logo div#mega-menu > header.flex > a.app-logo > img.w-[110px]
/storage/uploads/7442ae43-dd3e-46f6-855a-78a3c3fbf54a/log...
app logo div.px-6 > div.footer-head > a.app-logo > img
/storage/uploads/7442ae43-dd3e-46f6-855a-78a3c3fbf54a/log...
div#mega-menu > div.flex > a.flex > img.object-contain div#mega-menu > div.flex > a.flex > img.object-contain
div#mega-menu > div.flex > a.flex > img.object-contain div#mega-menu > div.flex > a.flex > img.object-contain
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/use...
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/use...
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/dis...
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/sto...
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/use...
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
/storage/uploads/b1248fff-acac-4f10-8b0a-7e5d8f149192/cir...
Keurmerk Feedback Company div.flex > div.certs > a > img
dovendi.com/keurmerk.png

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

●Max Potential First Input Delay 120 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,388 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 1.1 s
●Avoid long main-thread tasks 11 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 30 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 350 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
67

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.w-full > form#domain_form > button.absolute div.container > div.w-full > form#domain_form > button.absolute
div.container > div.w-full > form#search_form > button.absolute div.container > div.w-full > form#search_form > button.absolute

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide
div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide div.w-full > div.text-logo-slider > div.swiper-wrapper > a.swiper-slide

These are opportunities to improve the semantics of the controls in your application. This 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
Get to know us too! section.py-10 > div.container > div.w-full > a.inline-flex
Useful tips section.relative > div.container > a.p-4 > div.inline-flex
Our explanation section.relative > div.container > a.p-4 > div.inline-flex
Value of a name section.relative > div.container > a.p-4 > div.inline-flex
Find a cause section.relative > div.container > a.p-4 > div.inline-flex
All services section.text-usps > div.container > div.w-full > a.inline-flex
How it works section.py-12 > div.container > div.w-full > a.inline-flex
Partners overview section.py-10 > div.container > div.w-full > a.inline-flex

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
What makes a good domain name section.relative > div.container > a.p-4 > h3.text-[14px]

These are opportunities to improve keyboard navigation in your application.

○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-hidden="true"]` is not present on the document `<body>`
●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-hidden="true"]` elements do not contain focusable descendents
●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.
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
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.

SourceDescription
dovendi.com/en line 809, col 0
Error: <svg> attribute height: Expected length, "auto".
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
Failed to load resource: the server responded with a status of 503 ()
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
83

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.

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

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3
div.w-full > div.shadow-lg > div.bg-orange > img.w-3 div.w-full > div.shadow-lg > div.bg-orange > img.w-3

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
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback