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
/maps/api/js?key=AIzaSyAM1xoacjOIxEUyfQfxbJ1zY0KmxbPDJE4&...	1800.0 s	103.1 KiB
wikimapia.org/js/mobile-index.min.js?660	0.0 ms	37.8 KiB
ssl.google-analytics.com/ga.js	7200.0 s	17.4 KiB
wikimapia.org/js/mobclient.min.js?660	0.0 ms	6.8 KiB
i14.wikimapia.org/?x=518&y=351&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	34.2 KiB
i3.wikimapia.org/?x=519&y=352&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	34.0 KiB
i7.wikimapia.org/?x=519&y=353&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	27.7 KiB
i15.wikimapia.org/?x=519&y=351&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	26.4 KiB
i13.wikimapia.org/?x=517&y=351&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	25.6 KiB
i1.wikimapia.org/?x=517&y=352&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	25.4 KiB
wikimapia.org/css/mobile.css?660	0.0 ms	4.3 KiB
i6.wikimapia.org/?x=518&y=353&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	23.4 KiB
i5.wikimapia.org/?x=517&y=353&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	18.6 KiB
i11.wikimapia.org/?x=519&y=350&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	17.6 KiB
i10.wikimapia.org/?x=518&y=350&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	16.9 KiB
i9.wikimapia.org/?x=517&y=350&zoom=10&r=0&type=hybrid&lng=2	345600.0 s	10.5 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	60 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	35 ms

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

nodeLabel: div > div > div > img

path: 0,HTML,1,BODY,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,4,DIV,0,DIV,10,DIV,1,IMG

selector: div > div > div > img

snippet: <img draggable="false" alt="" role="presentation" src="https://maps.googleapis.com/maps/vt?pb=!1m5!1m4!1i10!2i518!3i351!4i256!2m1…" style="width: 256px; height: 256px; user-select: none; border: 0px; padding: 0px;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/maps/api/js?key=AIzaSyAM1xoacjOIxEUyfQfxbJ1zY0KmxbPDJE4&...	103.1 KiB	1.6 s
ssl.google-analytics.com/ga.js	17.4 KiB
wikimapia.org/js/mobile-index.min.js?660	37.8 KiB	778 ms
wikimapia.org/css/mobile.css?660	4.3 KiB	178 ms

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
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i518!3i352!4i256!2m1!1e1!2m3!1...	238.9 KiB	206.2 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i518!3i350!4i256!2m1!1e1!2m3!1...	231.9 KiB	199.2 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i517!3i350!4i256!2m1!1e1!2m3!1...	231.7 KiB	199.0 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i518!3i353!4i256!2m1!1e1!2m3!1...	230.9 KiB	198.2 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i517!3i351!4i256!2m1!1e1!2m3!1...	229.7 KiB	197.1 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i519!3i352!4i256!2m1!1e1!2m3!1...	226.7 KiB	194.0 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i517!3i352!4i256!2m1!1e1!2m3!1...	226.3 KiB	193.6 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i518!3i351!4i256!2m1!1e1!2m3!1...	226.0 KiB	193.4 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i519!3i353!4i256!2m1!1e1!2m3!1...	225.0 KiB	192.3 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i519!3i351!4i256!2m1!1e1!2m3!1...	221.3 KiB	188.6 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i517!3i353!4i256!2m1!1e1!2m3!1...	221.3 KiB	188.6 KiB
div > div > div > img `div > div > div > img`	/maps/vt?pb=!1m5!1m4!1i10!2i519!3i350!4i256!2m1!1e1!2m3!1...	217.7 KiB	185.1 KiB
div > div > div > img `div > div > div > img`	i14.wikimapia.org/?x=518&y=351&zoom=10&r=0&type=hybrid&lng=2	33.6 KiB	22.9 KiB
div > div > div > img `div > div > div > img`	i3.wikimapia.org/?x=519&y=352&zoom=10&r=0&type=hybrid&lng=2	33.4 KiB	22.8 KiB
div > div > div > img `div > div > div > img`	i7.wikimapia.org/?x=519&y=353&zoom=10&r=0&type=hybrid&lng=2	27.1 KiB	16.4 KiB
div > div > div > img `div > div > div > img`	i15.wikimapia.org/?x=519&y=351&zoom=10&r=0&type=hybrid&lng=2	25.9 KiB	15.2 KiB
div > div > div > img `div > div > div > img`	i13.wikimapia.org/?x=517&y=351&zoom=10&r=0&type=hybrid&lng=2	25.1 KiB	14.4 KiB
div > div > div > img `div > div > div > img`	i1.wikimapia.org/?x=517&y=352&zoom=10&r=0&type=hybrid&lng=2	24.8 KiB	14.1 KiB
div > div > div > img `div > div > div > img`	i6.wikimapia.org/?x=518&y=353&zoom=10&r=0&type=hybrid&lng=2	22.8 KiB	12.2 KiB
div > div > div > img `div > div > div > img`	i5.wikimapia.org/?x=517&y=353&zoom=10&r=0&type=hybrid&lng=2	18.1 KiB	7.4 KiB
div > div > div > img `div > div > div > img`	i11.wikimapia.org/?x=519&y=350&zoom=10&r=0&type=hybrid&lng=2	17.0 KiB	6.3 KiB
div > div > div > img `div > div > div > img`	i10.wikimapia.org/?x=518&y=350&zoom=10&r=0&type=hybrid&lng=2	16.3 KiB	5.7 KiB

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
wikimapia.org/m/	http/1.1
wikimapia.org/css/mobile.css?660	http/1.1
wikimapia.org/js/mobile-index.min.js?660	http/1.1
wikimapia.org/img/mobile/logo.png	http/1.1
wikimapia.org/js/mobclient.min.js?660	http/1.1
wikimapia.org/img/000.png	http/1.1
wikimapia.org/img/menu/menu-spt.png	http/1.1
wikimapia.org/img/mobile/icons/positioning-icon480.png	http/1.1
wikimapia.org/img/mobile/icons/search480.png	http/1.1
wikimapia.org/img/mobile/icons/places-icon480.png	http/1.1
wikimapia.org/m/favicon.ico	http/1.1
wikimapia.org/img/mobile/icons/plus-icon480.png	http/1.1
wikimapia.org/img/mobile/icons/minus-icon480.png	http/1.1
wikimapia.org/img/mobile/icons/loader-small.gif	http/1.1
wikimapia.org/img/mobile/icons/position-marker@2x.png?3	http/1.1

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.0 s

URL	Time Spent
wikimapia.org/	833 ms
wikimapia.org/	178 ms
wikimapia.org/m/	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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 650 ms 96.1 KiB

URL	Transfer Size	Est Savings
/maps/api/js?key=AIzaSyAM1xoacjOIxEUyfQfxbJ1zY0KmxbPDJE4&...	102.7 KiB	46.5 KiB
wikimapia.org/js/mobile-index.min.js?660	37.6 KiB	27.9 KiB
maps.googleapis.com/maps-api-v3/api/js/64/9c/util.js	69.7 KiB	21.7 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.

Category	Time Spent
Script Evaluation	975 ms
Other	594 ms
Style & Layout	234 ms
Script Parsing & Compilation	111 ms
Rendering	91 ms
Parse HTML & CSS	27 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/maps/vt?pb=!1m5!1m4!1i10!2i518!3i352!4i256!2m1!1e1!2m3!1...	239.0 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i518!3i350!4i256!2m1!1e1!2m3!1...	231.9 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i517!3i350!4i256!2m1!1e1!2m3!1...	231.8 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i518!3i353!4i256!2m1!1e1!2m3!1...	230.9 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i517!3i351!4i256!2m1!1e1!2m3!1...	229.8 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i519!3i352!4i256!2m1!1e1!2m3!1...	226.7 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i517!3i352!4i256!2m1!1e1!2m3!1...	226.3 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i518!3i351!4i256!2m1!1e1!2m3!1...	226.1 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i519!3i353!4i256!2m1!1e1!2m3!1...	225.0 KiB
/maps/vt?pb=!1m5!1m4!1i10!2i519!3i351!4i256!2m1!1e1!2m3!1...	221.4 KiB

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

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●JavaScript execution time 0.9 s

●Avoid long main-thread tasks 5 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 460 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 70 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#top-bar > div.wrapper > img#logo `body > div#top-bar > div.wrapper > img#logo`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#zoom-control > a#zoom-in-button `body > div#zoom-control > a#zoom-in-button`
body > div#zoom-control > a#zoom-out-button `body > div#zoom-control > a#zoom-out-button`
body > a#position-button `body > a#position-button`
body > div#top-bar > div.wrapper > a#places-button `body > div#top-bar > div.wrapper > a#places-button`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Buttons have an accessible name

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

○Heading elements appear in a sequentially-descending order

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

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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
i2.wikimapia.org/?x=518&y=352&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i1.wikimapia.org/?x=517&y=352&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i13.wikimapia.org/?x=517&y=351&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i14.wikimapia.org/?x=518&y=351&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i15.wikimapia.org/?x=519&y=351&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i3.wikimapia.org/?x=519&y=352&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i7.wikimapia.org/?x=519&y=353&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i6.wikimapia.org/?x=518&y=353&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i5.wikimapia.org/?x=517&y=353&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i9.wikimapia.org/?x=517&y=350&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i10.wikimapia.org/?x=518&y=350&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS
i11.wikimapia.org/?x=519&y=350&zoom=10&r=0&type=hybrid&lng=2	Automatically upgraded to HTTPS

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source
wikimapia.org/js/mobclient.min.js?660
wikimapia.org/js/mobclient.min.js?660

User Experience

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
div > div > div > img `div > div > div > img`	i1.wikimapia.org/?x=517&y=352&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i10.wikimapia.org/?x=518&y=350&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i11.wikimapia.org/?x=519&y=350&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i13.wikimapia.org/?x=517&y=351&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i14.wikimapia.org/?x=518&y=351&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i15.wikimapia.org/?x=519&y=351&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i2.wikimapia.org/?x=518&y=352&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i3.wikimapia.org/?x=519&y=352&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i5.wikimapia.org/?x=517&y=353&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i6.wikimapia.org/?x=518&y=353&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i7.wikimapia.org/?x=519&y=353&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	i9.wikimapia.org/?x=517&y=350&zoom=10&r=0&type=hybrid&lng=2	256 x 256	256 x 256	384 x 384
div > div > div > img `div > div > div > img`	maps.gstatic.com/mapfiles/transparent.png	37 x 37	1 x 1	56 x 56

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
/maps/api/js?key=AIzaSyAM1xoacjOIxEUyfQfxbJ1zY0KmxbPDJE4&... line 218, col 422	`Google Maps JavaScript API error: BillingNotEnabledMapError https://developers.google.com/maps/documentation/javascript/error-messages#billing-not-enabled-map-error`
/maps/api/js?key=AIzaSyAM1xoacjOIxEUyfQfxbJ1zY0KmxbPDJE4&... line 315, col 376	`The library panoramio is unknown. Please see https://developers.google.com/maps/documentation/javascript/libraries`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
Cookie

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Properly defines charset

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#top-bar > div.wrapper > img#logo `body > div#top-bar > div.wrapper > img#logo`

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

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`