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
m.gdpr-info.eu/matomo.js	3600.0 s	22.4 KiB

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
General Data Protection Regulation (GDPR) `div.header-search-wrapper > div.ics-logo > a > img`	/wp-content/themes/twentyfifteen-child/img/logo-intersoft...	37.4 KiB	33.3 KiB

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.

URL	Transfer Size	Duration
gdpr-info.eu/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	30.9 KiB	150 ms
/wp-content/plugins/gd-rating-system/js/rating/events.min...	797 B
gdpr-info.eu/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.1 KiB
/wp-content/cache/min/1/wp-includes/js/thickbox/thickbox....	1.1 KiB
/wp-content/cache/min/1/wp-content/plugins/gd-rating-syst...	856 B
/wp-content/plugins/solidsales-search-plugin/assets/style...	203 B
/wp-content/plugins/gd-rating-system/css/methods/stars.mi...	1.2 KiB
/wp-content/plugins/gd-rating-system/css/rating/core.min....	1.1 KiB
/wp-content/plugins/gd-rating-system/css/rating/grid.min....	760 B
/wp-content/cache/min/1/wp-content/plugins/tablepress/css...	1.9 KiB
/wp-content/cache/min/1/wp-content/themes/twentyfifteen/c...	2.1 KiB
/wp-content/cache/min/1/wp-content/themes/twentyfifteen/g...	16.0 KiB	150 ms
/wp-content/cache/min/1/wp-includes/css/dashicons.min.css...	35.2 KiB	150 ms
/wp-content/cache/min/1/wp-content/themes/twentyfifteen-c...	17.9 KiB	150 ms
/wp-content/cache/min/1/wp-content/themes/twentyfifteen/s...	11.1 KiB	150 ms
gdpr-info.eu/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4	15.9 KiB
/wp-content/cache/min/1/wp-content/plugins/widget-logic/b...	313 B

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: 600 ms 92.4 KiB

URL	Transfer Size	Est Savings
/wp-content/cache/min/1/wp-includes/css/dashicons.min.css...	35.0 KiB	35.0 KiB
/wp-content/cache/min/1/wp-content/themes/twentyfifteen-c...	17.7 KiB	16.0 KiB
/wp-content/cache/min/1/wp-content/themes/twentyfifteen/g...	15.8 KiB	15.8 KiB
gdpr-info.eu/wp-includes/css/dist/block-library/style.min.css?ver=6.9.4	15.7 KiB	15.6 KiB
/wp-content/cache/min/1/wp-content/themes/twentyfifteen/s...	10.9 KiB	10.0 KiB

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 6 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 70 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 40 ms

●Avoid large layout shifts 1 layout shift found

○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
Follow us: `footer#colophon > div.sharing-and-rating > div.sharing > div.sharing-hint`
XING `div.sharing > ul > li > a`
LinkedIn `div.sharing > ul > li > a`
Rate us: `footer#colophon > div.sharing-and-rating > div.site-rating > div.rating-question`
Please wait... `div.site-rating > div.gdrts-shortcode-wrapper > div#gdrts-dynamic-id-1 > div.gdrts-rating-please-wait`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PDF `article#post-310 > div.entry-content > p > a`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
XING\| LinkedIn `footer#colophon > div.sharing-and-rating > div.sharing > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
DSGVO `div.header-row > div.header-content > div.language-selector > a.language-link`
1 `tbody.row-hover > tr.row-1 > td.column-3 > a`
2 `tbody.row-hover > tr.row-1 > td.column-3 > a`
3 `tbody.row-hover > tr.row-1 > td.column-3 > a`
4 `tbody.row-hover > tr.row-1 > td.column-3 > a`
5 `tbody.row-hover > tr.row-2 > td.column-3 > a`
6 `tbody.row-hover > tr.row-2 > td.column-3 > a`
7 `tbody.row-hover > tr.row-2 > td.column-3 > a`
8 `tbody.row-hover > tr.row-2 > td.column-3 > a`
9 `tbody.row-hover > tr.row-2 > td.column-3 > a`
10 `tbody.row-hover > tr.row-2 > td.column-3 > a`

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chapter 1 – 1 2 3 4 Chapter 2 – 5 6 7 8 9 10 11 Chapter 3 – 12 13 14… `main#main > article#post-310 > div.entry-content > table#tablepress-12`

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

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

●`[role]` values are valid

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○Form elements have associated labels

○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

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

○Elements with visible text labels have matching accessible names.

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.

Source	Description
gdpr-info.eu/wp-admin/admin-ajax.php?action=gdrts_live_handler	`Failed to load resource: the server responded with a status of 403 ()`

●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

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 destination	Link Text
/en/?utm_source=gdpr-info.eu&utm_medium=banner&utm_campai...	Learn 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`