Skip to content
https://www.gov.pl

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.

64

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
matomo.www.gov.pl/analytics/js/container_68lYTZ79.js0.0 ms40.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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:4.307 source:map[column:19 line:3363 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:9.249 source:map[column:17 line:1325 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:3.739 source:map[column:47 line:3709 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.551 source:map[column:50 line:4049 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.507 source:map[column:33 line:4134 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.747 source:map[column:68 line:4474 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:4.23 source:map[column:26 line:1355 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.586 source:map[column:44 line:4856 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.613 source:map[column:44 line:4884 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.515 source:map[column:32 line:4909 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.206 source:map[column:94 line:6937 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.103 source:map[column:20 line:6939 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:4.264 source:map[column:16 line:3191 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.204 source:map[column:27 line:3576 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.601 source:map[column:18 line:3774 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:3.679 source:map[column:19 line:4031 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.636 source:map[column:28 line:4531 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.707 source:map[column:19 line:4779 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:1.604 source:map[column:16 line:5468 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.412 source:map[column:25 line:5470 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.249 source:map[column:15 line:7064 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.652 source:map[column:18 line:7243 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:3.667 source:map[column:17 line:8168 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:0.164 source:map[column:26 line:8932 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]] map[reflowTime:2.783 source:map[column:28 line:9431 type:source-location url:https://www.gov.pl/scripts/polyfills/modernizr-custom.js urlProvider:network]]]

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:389.792 label:Time to first byte subpart:timeToFirstByte] map[duration:693.662 label:Resource load delay subpart:resourceLoadDelay] map[duration:259.482 label:Resource load duration subpart:resourceLoadDuration] map[duration:1224.569 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-SECTION
nodeLabel: Załatwiaj sprawy urzędowe przez internet, bezpiecznie i wygodnie! Wyszukaj Podp…
path: 1,HTML,1,BODY,3,MAIN,0,DIV,1,SECTION
selector: body#body > main > div > section.gov-services
snippet: <section class="gov-services blue-bar-row blue-bar-row--epolak">

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-SECTION
nodeLabel: Załatwiaj sprawy urzędowe przez internet, bezpiecznie i wygodnie! Wyszukaj Podp…
path: 1,HTML,1,BODY,3,MAIN,0,DIV,1,SECTION
selector: body#body > main > div > section.gov-services
snippet: <section class="gov-services blue-bar-row blue-bar-row--epolak">

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

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
- li > div > picture > img
www.gov.pl/photo/format/808797fb-a8bc-4fec-b539-5c852134221e/resolution/700x29542.8 KiB32.9 KiB

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

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 60.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 31.1 KiB
URLTransfer SizeEst Savings
www.gov.pl/css/main-31410bf7b3f.css32.4 KiB31.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: 970 ms 183.8 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
Other1.2 s
Script Evaluation769 ms
Style & Layout459 ms
Script Parsing & Compilation205 ms
Parse HTML & CSS113 ms
Rendering53 ms
Garbage Collection9.9 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
Godło Polski div.main-container > div#footer-links > a.logo > img
www.gov.pl/img/icons/godlo-12.svg
- li > div > picture > img
www.gov.pl/photo/format/808797fb-a8bc-4fec-b539-5c852134221e/resolution/700x295
Logo Funduszy Europejskich footer.footer > div.main-container > div.eu-logotypes > img.eu-funds-logo
www.gov.pl/img/icons/eu/fe-pc-left-pl.svg
Logo Unii Europejskiej body#body > header.govpl > nav#top-bar-nav > img.govpl__eu-logo
www.gov.pl/img/icons/eu/eu-center-pl.svg
Flaga Polski z napisem Rzeczypospolita Polska footer.footer > div.main-container > div.eu-logotypes > img.rp-logo
www.gov.pl/img/icons/eu/rp-left-pl.svg
Logo Unii Europejskiej footer.footer > div.main-container > div.eu-logotypes > img.eu-logo-left
www.gov.pl/img/icons/eu/eu-efrp-left-pl.svg

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

●Max Potential First Input Delay 100 ms
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 1,045 KiB
●JavaScript execution time 0.9 s
●Avoid long main-thread tasks 7 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 100 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 190 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
97

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
 Gdy domena nadawcy jest inna niż gov.pl div.main-container > div#services-citizens > div.alert > li
Dzwonić pod wskazany numer telefonu div.main-container > div#services-citizens > div.alert > li
Klikać w linki div.main-container > div#services-citizens > div.alert > li
Otwierać załączników div.main-container > div#services-citizens > div.alert > li

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

○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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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>`).
●No element has a `[tabindex]` value greater than 0
●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
○ARIA input fields 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 toggle fields have accessible names
○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 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.
○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.
77

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
ul > li > a > img ul > li > a > img
www.gov.pl/logo/98095230-8d69-4e20-88eb-b8898d4aef1170 x 150 (0.47)190 x 150 (1.27)
ul > li > a > img ul > li > a > img
www.gov.pl/logo/b41e841f-0ba1-42df-a7a8-7a4c424182f070 x 150 (0.47)150 x 150 (1.00)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
●Uses HTTPS
●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
●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
●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
○Use a strong HSTS policy
○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

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.

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 have descriptive text
●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