Spain · Madrid Completed: Apr 22, 2026 23:31 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 69 / 100
Based on 8 categories, 0 sections
Room to improve — your 27.0s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 11.2 MB (5.4 MB transferred)
Performance issues directly impact user engagement and conversion rates.
2 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
4 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/a3ef24ee-8580-46ca-a183-1374f6260827)<a href="https://beavercheck.com/results/a3ef24ee-8580-46ca-a183-1374f6260827"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmapy.cz" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmapy.czThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 27.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~29%.
Page takes 27.0s to load
+12% bounceUsers abandon at ~3s — you're 24.5s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 606ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Viewport disables user zoom
+2% bounceVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
Fix: Remove user-scalable=no; drop maximum-scale if it's below 2
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
CZK 6,600 investment → CZK 32/month returns + EUR 120,500,000 risk avoided
CZK 6,600
6h · 5 findings
CZK 32 /mo
~CZK 382 / year
EUR 120,500,000
if kept compliant
CZK 1,100 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.0 developer hours at Kč1100/hr
Based on Czech Republic rates (Kč1100/hr)
Start here for the best return on investment
CZK 10,041,699 / month at risk
~CZK 120,500,382 / year if left unfixed
€120,500,000
+9 more
CZK 32 /mo
17113.8 MB/mo × 1.860 CZK/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
14.21 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
26.97 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
606 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
14.21 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
27.06 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| mapy.com/fonts/mapy.woff?7 | 35 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-68-43 | 177.2 KiB | 144.6 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-69-45 | 175.8 KiB | 143.2 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-69-44 | 174.8 KiB | 142.1 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-68-44 | 174.0 KiB | 141.3 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-69-43 | 168.8 KiB | 136.1 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-67-45 | 166.5 KiB | 133.8 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-67-44 | 166.5 KiB | 133.8 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-67-43 | 161.4 KiB | 128.7 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-67-42 | 156.8 KiB | 124.1 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-69-42 | 151.9 KiB | 119.2 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-68-45 | 148.7 KiB | 116.0 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-68-42 | 140.5 KiB | 107.8 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-69-46 | 113.8 KiB | 81.2 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-67-46 | 108.9 KiB | 76.2 KiB |
div.tiles > div#2-0-0.3534838168819474 > div > img div.tiles > div#2-0-0.3534838168819474 > div > img | tilecache.mapy.com/turist-en/retina/7-68-46 | 101.1 KiB | 68.4 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| h.seznam.cz/js/dot-small.js | 62.0 KiB | 737 ms |
| mapy.com/js/lang-en.2.80.90.js? | 52.8 KiB | 604 ms |
| mapy.com/css/main.2.80.90.css?s | 162.9 KiB | 1.8 s |
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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| mapy.cz/ | 875 ms |
| mapy.com/ | 857 ms |
| mapy.com/en/ | 0.0 ms |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mapy.com/css/main.2.80.90.css?s | 162.6 KiB | 160.3 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| mapy.com/js/userweb.2.80.90.js? | 1.3 MiB | 781.6 KiB |
| h.seznam.cz/js/cmp2/scmp-lite.js | 209.8 KiB | 100.4 KiB |
| api.mapy.cz/js/api/v5/smap-jak.js?v=5.6.18 | 141.8 KiB | 98.9 KiB |
| /js/cmp2/d_876/c_static_qA_A/kcHp2YdDtCDcb50YfGZQtVp/5785... | 74.5 KiB | 70.4 KiB |
| geo.seznam.cz/static/js/geo.js | 45.9 KiB | 33.1 KiB |
| c.seznam.cz/js/rc.js | 46.8 KiB | 31.2 KiB |
| ssp.seznam.cz/static/js/ssp.js | 45.0 KiB | 30.6 KiB |
| mapy.com/js/lang-en.2.80.90.js? | 52.5 KiB | 29.3 KiB |
| h.seznam.cz/js/dot-small.js | 61.7 KiB | 27.9 KiB |
| login.szn.cz/js/api/3/login.js | 39.9 KiB | 27.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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| mapy.com/js/userweb.2.80.90.js? | 1.7 s | 1.1 s | 344 ms |
| Unattributable | 607 ms | 42 ms | 0.0 ms |
| mapy.com/en/ | 345 ms | 14 ms | 3.7 ms |
| h.seznam.cz/js/cmp2/scmp-lite.js | 261 ms | 202 ms | 46 ms |
| h.seznam.cz/js/dot-small.js | 215 ms | 178 ms | 17 ms |
| /js/cmp2/d_876/c_static_qA_A/kcHp2YdDtCDcb50YfGZQtVp/5785... | 96 ms | 80 ms | 8.4 ms |
| api.mapy.cz/js/api/v5/smap-jak.js?v=5.6.18 | 83 ms | 32 ms | 41 ms |
| c.seznam.cz/js/rc.js | 57 ms | 40 ms | 17 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.9 s |
| Other | 874 ms |
| Script Parsing & Compilation | 579 ms |
| Style & Layout | 181 ms |
| Parse HTML & CSS | 92 ms |
| Rendering | 14 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| mapy.com/js/userweb.2.80.90.js? | 1.3 MiB |
| h.seznam.cz/js/cmp2/fonts/InterVariable.woff2 | 344.5 KiB |
| h.seznam.cz/js/cmp2/scmp-lite.js | 213.1 KiB |
| tilecache.mapy.com/turist-en/retina/7-68-43 | 177.9 KiB |
| tilecache.mapy.com/turist-en/retina/7-69-45 | 176.6 KiB |
| tilecache.mapy.com/turist-en/retina/7-69-44 | 175.5 KiB |
| tilecache.mapy.com/turist-en/retina/7-68-44 | 174.6 KiB |
| tilecache.mapy.com/turist-en/retina/7-69-43 | 169.5 KiB |
| tilecache.mapy.com/turist-en/retina/7-67-45 | 167.2 KiB |
| tilecache.mapy.com/turist-en/retina/7-67-44 | 167.1 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#mapycz > div#block-map > div#layout-bar > button.icon div#mapycz > div#block-map > div#layout-bar > button.icon |
div#mapycz > div#block-map > div#layout-bar > button.icon div#mapycz > div#block-map > div#layout-bar > button.icon |
div#mapycz > div#block-map > div#layout-bar > button.icon div#mapycz > div#block-map > div#layout-bar > button.icon |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Download Mapy.com body.lang-en > div.android-app-promotion > div > a.button |
Not now body.lang-en > div.android-app-promotion > div > button |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | mapy.com/js/userweb.2.80.90.js? line 1, col 3204853 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 400 (BAD REQUEST) | |
Failed to load resource: the server responded with a status of 400 (BAD REQUEST) |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.37 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.20 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
90 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.097
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.58 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.23 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| mapy.com/fonts/mapy.woff?7 | 40 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-66-45 | 53.7 KiB | 43.1 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-70-46 | 52.8 KiB | 42.1 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-69-45 | 52.1 KiB | 41.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-68-43 | 51.3 KiB | 40.6 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-66-43 | 51.1 KiB | 40.5 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-66-44 | 51.1 KiB | 40.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-69-44 | 50.6 KiB | 40.0 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-68-44 | 50.5 KiB | 39.9 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-67-44 | 49.8 KiB | 39.1 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-67-45 | 49.7 KiB | 39.0 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-69-43 | 49.7 KiB | 39.0 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-70-43 | 49.0 KiB | 38.3 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-67-43 | 48.9 KiB | 38.2 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-67-42 | 48.0 KiB | 37.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-69-42 | 47.1 KiB | 36.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-66-42 | 46.8 KiB | 36.1 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-68-42 | 46.3 KiB | 35.6 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-70-44 | 46.3 KiB | 35.6 KiB |
div#search > div#promohp > a.link-item > img div#search > div#promohp > a.link-item > img | mapy.com/img/promo/vyroci_en.jpg | 41.0 KiB | 34.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-68-45 | 45.1 KiB | 34.4 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-70-45 | 44.3 KiB | 33.6 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-66-46 | 43.1 KiB | 32.5 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-70-42 | 42.2 KiB | 31.6 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-69-46 | 34.6 KiB | 23.9 KiB |
div#map-controls > div.map-controls__middleToolbar > div.web2app > img.web2app__qr div#map-controls > div.map-controls__middleToolbar > div.web2app > img.web2app__qr | mapy.com/img/promo/af-qr.png | 23.7 KiB | 23.5 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-67-46 | 33.7 KiB | 23.1 KiB |
div.tiles > div#2-0-0.6416220948034516 > div > img div.tiles > div#2-0-0.6416220948034516 > div > img | tilecache.mapy.com/turist-en/7-68-46 | 31.7 KiB | 21.1 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| mapy.com/js/lang-en.2.80.90.js? | 52.8 KiB | |
| h.seznam.cz/js/dot-small.js | 62.0 KiB | 145 ms |
| mapy.com/css/main.2.80.90.css?s | 162.9 KiB | 245 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| mapy.cz/ | 290 ms |
| mapy.com/ | 307 ms |
| mapy.com/en/ | 0.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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| mapy.com/js/userweb.2.80.90.js? | 1.3 MiB | 781.6 KiB |
| h.seznam.cz/js/cmp2/scmp-lite.js | 209.7 KiB | 100.4 KiB |
| api.mapy.cz/js/api/v5/smap-jak.js?v=5.6.18 | 141.9 KiB | 98.9 KiB |
| /js/cmp2/d_876/c_static_qA_A/kcHp2YdDtCDcb50YfGZQtVp/5785... | 74.4 KiB | 70.4 KiB |
| geo.seznam.cz/static/js/geo.js | 45.9 KiB | 33.4 KiB |
| c.seznam.cz/js/rc.js | 46.8 KiB | 31.2 KiB |
| ssp.seznam.cz/static/js/ssp.js | 45.0 KiB | 30.6 KiB |
| mapy.com/js/lang-en.2.80.90.js? | 52.5 KiB | 29.3 KiB |
| h.seznam.cz/js/dot-small.js | 61.7 KiB | 28.2 KiB |
| login.szn.cz/js/api/3/login.js | 39.9 KiB | 27.1 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| mapy.com/css/main.2.80.90.css?s | 162.6 KiB | 159.0 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size |
|---|---|
| mapy.com/js/userweb.2.80.90.js? | 1.3 MiB |
| h.seznam.cz/js/cmp2/fonts/InterVariable.woff2 | 344.5 KiB |
| h.seznam.cz/js/cmp2/scmp-lite.js | 213.0 KiB |
| mapy.com/css/main.2.80.90.css?s | 162.9 KiB |
| api.mapy.cz/js/api/v5/smap-jak.js?v=5.6.18 | 142.0 KiB |
| /js/cmp2/d_876/c_static_qA_A/kcHp2YdDtCDcb50YfGZQtVp/5785... | 74.5 KiB |
| api.mapy.cz/img/api/logo.svg | 70.1 KiB |
| h.seznam.cz/js/dot-small.js | 62.0 KiB |
| /vychytavky?tags=1750&per_page=20&page=1&_fields=tags,id,... | 56.3 KiB |
| tilecache.mapy.com/turist-en/7-66-45 | 54.3 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img | api.mapy.com/poiimg/icon/292 |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img | api.mapy.com/poiimg/icon/133 |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img | api.mapy.com/poiimg/icon/49 |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img | api.mapy.com/poiimg/icon/28 |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#mapycz > div#scene > div#all-controls > button.map-controls__resizer div#mapycz > div#scene > div#all-controls > button.map-controls__resizer |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div#search > div#promohp > a.link-item > img div#search > div#promohp > a.link-item > img |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#layout-body > div#search > div#promohp > a.link-item div#layout-body > div#search > div#promohp > a.link-item |
div#layout-scroll > div.layout__footer > div.layout__footer__topContainer > a div#layout-scroll > div.layout__footer > div.layout__footer__topContainer > a |
div#map-controls > div.map-controls__middleToolbar > div.web2app > a div#map-controls > div.map-controls__middleToolbar > div.web2app > a |
div#map-controls > div.map-controls__middleToolbar > div.web2app > a div#map-controls > div.map-controls__middleToolbar > div.web2app > a |
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search div#layout-header > div#layout-bar > button.icon > span |
Route div#layout-header > div#layout-bar > button.icon > span |
Log in to
My Mapy div#layout-header > div#layout-bar > button.icon > span |
Log in to div#layout-bar > button.icon > span > i |
Categories div.main-panel > div.category > div.header > h3 |
More categories div.category > div.header > span.right-part > a |
Log in div#fixed-suggest > div.main-panel > div.login > a |
31. 3. 2026 div.layout__footer__bottomPart > div.layout__footer__tweak > p > span.date |
saved points and routes div.layout__footer__bottomPart > div.layout__footer__tweak > p > a |
Show all new features div.layout__footer > div.layout__footer__bottomPart > div.layout__footer__tweak > button.ui-linkbutton |
English div.layout__footer__topContainer > div.language-control2 > a.en > span |
Help div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Legend div.layout__footer > div.layout__footer__row > p.layout__footer__links > a.layout__footer__legend |
Mobile div.layout__footer > div.layout__footer__row > p.layout__footer__links > a.layout__footer__mobilePromo |
Advertising div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Terms and Licensing div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Problems and comments div.layout__footer > div.layout__footer__row > p.layout__footer__links > button.layout__footer__reportButton |
Personalization settings div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
For developers div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Help div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Legend div.layout__footer > div.layout__footer__row > p.layout__footer__links > a.layout__footer__legend |
Mobile div.layout__footer > div.layout__footer__row > p.layout__footer__links > a.layout__footer__mobilePromo |
Advertising div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Terms and Licensing div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
Problems and comments div.layout__footer > div.layout__footer__row > p.layout__footer__links > button.layout__footer__reportButton |
Personalization settings div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
For developers div.layout__footer > div.layout__footer__row > p.layout__footer__links > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | mapy.com/js/userweb.2.80.90.js? line 1, col 3204853 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 400 (BAD REQUEST) | |
Failed to load resource: the server responded with a status of 400 (BAD REQUEST) |
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div.content > a.category-item > span.img-holder > img div.content > a.category-item > span.img-holder > img |
div#search > div#promohp > a.link-item > img div#search > div#promohp > a.link-item > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback