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
www.lioc.nl/wp-content/uploads/2019/03/stolp-ei.png	0.0 ms	244.5 KiB
www.lioc.nl/wp-content/themes/lioc/images/stolp.png	0.0 ms	61.8 KiB
www.lioc.nl/wp-content/themes/lioc/style.css	0.0 ms	29.6 KiB
www.lioc.nl/wp-content/themes/lioc/images/bg.jpg	0.0 ms	26.0 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.lioc.nl/wp-content/themes/lioc/js/slick.js	0.0 ms	14.8 KiB
www.lioc.nl/wp-includes/css/dist/block-library/style.min.css	0.0 ms	11.5 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	21.3 KiB
www.lioc.nl/wp-content/themes/lioc/images/logo.png	0.0 ms	7.0 KiB
www.lioc.nl/wp-includes/js/dist/vendor/wp-polyfill.min.js	0.0 ms	7.0 KiB
www.lioc.nl/wp-content/themes/lioc/js/plugins.js	0.0 ms	6.8 KiB
www.lioc.nl/wp-content/themes/lioc/js/main.min.js	0.0 ms	4.7 KiB
www.lioc.nl/wp-content/plugins/contact-form-7/includes/js/index.js	0.0 ms	4.0 KiB
www.lioc.nl/wp-includes/js/dist/vendor/regenerator-runtime.min.js	0.0 ms	2.5 KiB
www.lioc.nl/wp-content/themes/lioc/images/icons/phone.png	0.0 ms	1.8 KiB
www.lioc.nl/wp-content/plugins/contact-form-7/modules/recaptcha/index.js	0.0 ms	923 B
/collect?v=2&fmt=js&pid=3141946&time=1792930175693&li_ads...	0.0 ms	633 B
/wp-content/plugins/sitepress-multilingual-cms/templates/...	0.0 ms	417 B
www.lioc.nl/wp-content/themes/lioc/images/icons/arrowup_white.png	0.0 ms	243 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB

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.6426649999999999] map[node:map[boundingRect:map[bottom:489 height:509 left:0 right:412 top:-20 width:412] lhId:page-3-DIV nodeLabel:• path:4,HTML,2,BODY,3,DIV,2,DIV,0,DIV,2,DIV selector:div.scrollFrame > div > div.home_banner > div.container snippet:<div class="container"> type:node] score:0.642369] map[node:map[boundingRect:map[bottom:206 height:32 left:30 right:382 top:173 width:352] lhId:page-1-H1 nodeLabel:Your idea in reliable hands path:4,HTML,2,BODY,3,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,A,0,DIV,0,H1 selector:div.row-fluid > a.banner_read_more > div.banner_tekst > h1 snippet:<h1> type:node] score:0.000296 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:809 height:52 left:15 right:115 top:757 width:100] lhId:page-8-IMG nodeLabel:Lioc logo path:4,HTML,2,BODY,3,DIV,0,HEADER,0,DIV,0,DIV,0,A,0,IMG selector:div.whitebar_home > div.container > a > img.logo snippet:<img class="logo" src="https://www.lioc.nl/wp-content/themes/lioc/images/logo.png" alt="Lioc logo"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/opensans/v15/mem5YaGs126MiZpBA-UN_r8OUuhpKKSTjw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/oxygen/v8/2sDfZG1Wl4LcnbuKjk0mRUe0Aw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/opensans/v15/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/oxygen/v8/2sDcZG1Wl4LcnbuCNWgzaGW5Kb8VZA.woff2]]] type:subitems]]]

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:7191.621 label:Time to first byte subpart:timeToFirstByte] map[duration:471.379 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-P

nodeLabel: Your thoughts gain value when an idea turns into an intellectual property. Prot…

path: 4,HTML,2,BODY,3,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,A,0,DIV,2,P

selector: div.row-fluid > a.banner_read_more > div.banner_tekst > p

snippet: <p>

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
www.lioc.nl/wp-content/themes/lioc/style.css	29.6 KiB	671 ms
/wp-content/plugins/sitepress-multilingual-cms/templates/...	417 B
cdn.jsdelivr.net/npm/slick-carousel@1.8.1/slick/slick.css	999 B	752 ms

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
fonts.gstatic.com/s/opensans/v15/mem5YaGs126MiZpBA-UN_r8OUuhpKKSTjw.woff2	10 ms
fonts.gstatic.com/s/oxygen/v8/2sDfZG1Wl4LcnbuKjk0mRUe0Aw.woff2	10 ms
fonts.gstatic.com/s/opensans/v15/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2	10 ms
fonts.gstatic.com/s/oxygen/v8/2sDcZG1Wl4LcnbuCNWgzaGW5Kb8VZA.woff2	10 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	5.0 ms

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 6.5 s

URL	Time Spent
www.lioc.nl/en/	6.6 s

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.

Element	Layout shift score
• `div.scrollFrame > div > div.home_banner > div.container`	0.642
Your idea in reliable hands `div.row-fluid > a.banner_read_more > div.banner_tekst > h1`	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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 300 ms 279.7 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/NhfdZHzre16wrc2m6BxEdu7J/recaptcha__en.js	347.0 KiB	159.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WFRVJTR	135.7 KiB	67.6 KiB
code.jquery.com/ui/1.10.3/jquery-ui.min.js	59.0 KiB	53.1 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.gstatic.com/recaptcha/releases/NhfdZHzre16wrc2m6BxEdu7J/recaptcha__en.js	1.6 s	1.4 s	117 ms
www.lioc.nl/en/	621 ms	10 ms	4.9 ms
Unattributable	390 ms	15 ms	0.0 ms
www.googletagmanager.com/gtm.js?id=GTM-WFRVJTR	287 ms	211 ms	54 ms
snap.licdn.com/li.lms-analytics/insight.min.js	117 ms	86 ms	29 ms
ajax.googleapis.com/ajax/libs/jquery/1.8/jquery.min.js	94 ms	66 ms	13 ms
code.jquery.com/ui/1.10.3/jquery-ui.min.js	80 ms	45 ms	32 ms
www.google-analytics.com/analytics.js	69 ms	56 ms	7.2 ms

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.

Category	Time Spent
Script Evaluation	2.0 s
Other	603 ms
Style & Layout	363 ms
Script Parsing & Compilation	283 ms
Rendering	73 ms
Parse HTML & CSS	69 ms
Garbage Collection	50 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.1 KiB

URL	Transfer Size	Est Savings
www.lioc.nl/wp-content/themes/lioc/style.css	29.6 KiB	4.1 KiB

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 5.9 KiB

URL	Transfer Size	Est Savings
www.lioc.nl/wp-content/themes/lioc/js/slick.js	14.7 KiB	5.9 KiB

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 38.2 KiB

URL	Transfer Size	Est Savings
www.lioc.nl/wp-content/themes/lioc/style.css	29.6 KiB	26.8 KiB
www.lioc.nl/wp-includes/css/dist/block-library/style.min.css	11.4 KiB	11.4 KiB

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
Lioc logo `div.whitebar_home > div.container > a > img.logo`	www.lioc.nl/wp-content/themes/lioc/images/logo.png
phone `div.whitebar_home > div.container > a#phone > img`	www.lioc.nl/wp-content/themes/lioc/images/icons/phone.png

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

●Optimize DOM size

●Forced reflow

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 1,542 KiB

●Avoid long main-thread tasks 17 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 750 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

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
Protect your brand recognition `div.container > div.row-fluid > div.home_block > p`
MORE INFORMATION `div.home_block > div.home_block_bottom > a > p`
Protect your technological lead `div.container > div.row-fluid > div.home_block > p`
MORE INFORMATION `div.home_block > div.home_block_bottom > a > p`
+31(0) 40 303 21 48 `div.row-fluid > div.span3 > p > a`
Terms And Conditions `div.span8 > div.row-fluid > div.span3 > a`
Privacy Statement `div.span8 > div.row-fluid > div.span3 > a`

These are opportunities to improve the legibility of your content.

Names and labels

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.whitebar_home > div.container > div.main_menu > a#mobMenu `div.whitebar_home > div.container > div.main_menu > a#mobMenu`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

●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

●`<frame>` or `<iframe>` elements have a title

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[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

○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

○`<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.

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

○`<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.

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
phone `div.whitebar_home > div.container > a#phone > img`	www.lioc.nl/wp-content/themes/lioc/images/icons/phone.png	30 x 30	30 x 30	45 x 45

●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

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.lioc.nl/en/services/trademarks/	MORE INFORMATION
www.lioc.nl/en/services/patents/	MORE INFORMATION
www.lioc.nl/en/services/designs/	MORE INFORMATION

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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`