Skip to content
https://matomo.org

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.

96

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.

RequestCache TTLTransfer Size
privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js3600.0 s30.4 KiB
web.cmp.usercentrics.eu/ui/loader.js3600.0 s15.3 KiB
cdn.matomo.cloud/demo-web.matomo.org/container_bugnCohE.js691200.0 s73.4 KiB
app.usercentrics.eu/session/1px.png?settingsId=wp_ioN8GED4t7y1800.0 s826 B

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.208 source:map[column:98815 line:1 type:source-location url:https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.208 source:map[column:97998 line:0 type:source-location url:https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js urlProvider:network]]]

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

URLTransfer Size
/wp-content/plugins/popup-maker/dist/packages/block-libra...0 B
matomo.org/wp-includes/js/hoverIntent.min.js?ver=1.10.23.5 KiB
matomo.org/wp-content/themes/website-child/assets/js/vendor/jquery.sticky.js4.2 KiB
matomo.org/wp-content/themes/website-child/assets/js/validator.min.js?ver=15.3 KiB
/wp-content/themes/website-child/assets/js/_main.js?ver=1...10.4 KiB
/wp-content/themes/website-child/assets/js/responsive-tab...4.3 KiB
/wp-content/plugins/elementor/assets/js/webpack.runtime.m...5.2 KiB
matomo.org/wp-content/themes/website-child/style.css?ver=176211126810.7 KiB
matomo.org/wp-content/themes/website-child/assets/js/video.js?ver=44.7 KiB
/wp-includes/css/dist/block-editor/style.min.css?ver=c3bd...18.9 KiB
matomo.org/wp-content/themes/website-child/assets/js/vendor/url_builder.js3.5 KiB
matomo.org/wp-includes/js/jquery/ui/core.min.js?ver=1.13.39.7 KiB
matomo.org/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=4.0.112.9 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/css/sw...7.3 KiB
matomo.org/wp-content/plugins/elementor/assets/css/frontend.min.css?ver=4.0.19.9 KiB
matomo.org/wp-content/uploads/maxmegamenu/style_en.css?ver=2a66b110.4 KiB
/wp-content/plugins/elementor-pro/assets/css/widget-testi...4.3 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper...41.4 KiB
/wp-includes/css/dist/components/style.min.css?ver=c3bd3e...16.6 KiB
matomo.org/wp-content/plugins/shortpixel-adaptive-images/assets/js/ai-2.0.min.js15.2 KiB
/wp-content/plugins/elementor/assets/js/frontend-modules....18.4 KiB
matomo.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.132.5 KiB
/wp-content/themes/website-child/assets/js/faq_filter.js?...3.2 KiB
/wp-content/themes/generatepress/assets/js/back-to-top.mi...3.2 KiB
matomo.org/wp-content/themes/generatepress/assets/js/menu.min.js?ver=3.6.14.6 KiB
/wp-content/themes/website-child/assets/js/faq.js?ver=c3b...3.9 KiB
matomo.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.17.5 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...3.1 KiB
/wp-content/plugins/elementor-pro/assets/css/widget-carou...3.4 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...3.1 KiB
/wp-content/plugins/elementor/assets/css/conditionals/e-s...3.6 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...15.1 KiB
/wp-content/plugins/elementor/assets/css/widget-image-box...3.2 KiB
/wp-content/plugins/elementor/assets/css/conditionals/sha...3.1 KiB
matomo.org/wp-content/tablepress-combined.min.css?ver=2205.2 KiB
/wp-content/themes/website-child/assets/img/sprites/sprit...4.3 KiB
/wp-content/plugins/elementor/assets/css/widget-image.min...2.9 KiB
/wp-content/plugins/elementor/assets/css/widget-spacer.mi...3.1 KiB
/wp-content/plugins/elementor/assets/lib/animations/style...2.9 KiB
/wp-content/themes/website-child/assets/css/global.css?ve...3.1 KiB
matomo.org/wp-content/themes/generatepress/assets/css/mobile.min.css?ver=3.6.13.9 KiB
/wp-content/themes/generatepress/assets/css/unsemantic-gr...4.9 KiB
/wp-content/plugins/elementor/assets/css/widget-heading.m...2.9 KiB
matomo.org/wp-content/themes/generatepress/assets/css/style.min.css?ver=3.6.17.8 KiB
/wp-content/themes/website-child/assets/css/help.css?ver=...4.5 KiB
/wp-content/plugins/sitepress-multilingual-cms/templates/...3.1 KiB
matomo.org/wp-includes/js/dist/i18n.min.js?ver=c26c3dc7bed3667933754.8 KiB
/wp-includes/css/dist/preferences/style.min.css?ver=c3bd3...3.2 KiB
matomo.org/wp-content/plugins/elementor-pro/assets/js/frontend.min.js?ver=4.0.18.9 KiB
matomo.org/wp-content/plugins/megamenu-pro/assets/public.js?ver=2.4.47.1 KiB
matomo.org/wp-content/plugins/megamenu/js/maxmegamenu.js?ver=3.8.19.0 KiB
matomo.org/wp-includes/js/dist/hooks.min.js?ver=dd5603f07f9220ed27f14.5 KiB
/wp-content/plugins/elementor-pro/assets/js/webpack-pro.r...5.4 KiB
/wp-content/plugins/elementor-pro/assets/js/elements-hand...12.9 KiB

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

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: 40 ms 42.1 KiB
URLTransfer SizeEst Savings
/wp-includes/css/dist/block-editor/style.min.css?ver=c3bd...16.1 KiB16.1 KiB
/wp-includes/css/dist/components/style.min.css?ver=c3bd3e...13.9 KiB13.8 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...12.3 KiB12.2 KiB

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 2.3 KiB
URLTransfer SizeEst Savings
matomo.org/wp-content/themes/website-child/style.css?ver=176211126810.7 KiB2.3 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.3 KiB
URLTransfer SizeEst Savings
/wp-content/themes/website-child/assets/js/_main.js?ver=1...7.6 KiB2.9 KiB
matomo.org/wp-content/plugins/megamenu/js/maxmegamenu.js?ver=3.8.16.4 KiB2.4 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: 0.0 ms 99.3 KiB
URLTransfer SizeEst Savings
cdn.matomo.cloud/demo-web.matomo.org/container_bugnCohE.js72.9 KiB42.3 KiB
web.cmp.usercentrics.eu/ui/v/3.116.0/WebSdk.lib.d00a93b7.js56.0 KiB35.3 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper...38.8 KiB21.6 KiB

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

●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 1.0 s
●Avoids enormous network payloads Total size was 898 KiB
●JavaScript execution time 0.5 s
●Minimizes main-thread work 1.5 s
●Avoid long main-thread tasks 1 long task found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 230 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 10 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid large layout shifts
91

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
TRY IT FOR FREE div#mega-menu-wrap-primary > ul#mega-menu-primary > li#mega-menu-item-40179 > a.mega-menu-link
21-day free Cloud trial. div.elementor-image-box-content > h3.elementor-image-box-title > span > a
TRY IT FOR FREE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
4.8 out of 5 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
GDPR div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
CCPA div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Take back control of your data now div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Get the guide div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Learn more div.elementor-element > div.elementor-widget-container > p > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Learn more div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
Read more testimonials div.elementor-element > div.elementor-widget-container > p > a
Read more div.elementor-widget-container > div.matomo-iso-widget > a.matomo-iso-widget__button > span
TRY IT FOR FREE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.elementor-swiper > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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.
○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
matomo.org/
Refused to apply style from 'https://matomo.org/wp-content/plugins/popup-maker/dist/packages/block-library-style.css/?ver=7424eb959f91acb8bbb2' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
●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
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

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 destinationLink Text
matomo.org/guide/installation-maintenance/import-google-analytics/Learn more
matomo.org/tracking-personal-data-with-matomo/Learn more
matomo.org/no-data-sampling/Learn more
matomo.org/free-software/Learn more
matomo.org/no-data-limitations-with-matomo/Learn more
matomo.org/product-features/Learn more
matomo.org/flexibility/Learn more
matomo.org/support-plans/Learn more
matomo.org/blog/2025/09/matomo-iso-27001-certification-2025/Read more

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

Send Feedback