623 ms in total
113 ms
378 ms
132 ms
Visit maps.google.li now to see the best up-to-date Maps Google content for Liechtenstein and also check out these interesting facts you probably never knew about maps.google.li
Find local businesses, view maps and get driving directions in Google Maps.
Visit maps.google.liWe analyzed Maps.google.li page load time and found that the first response time was 113 ms and then it took 510 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
maps.google.li performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value4.8 s
30/100
25%
Value3.1 s
93/100
10%
Value360 ms
72/100
30%
Value0
100/100
15%
Value5.6 s
70/100
10%
113 ms
36 ms
50 ms
58 ms
20 ms
Our browser made a total of 7 requests to load all elements on the main page. We found that 29% of them (2 requests) were addressed to the original Maps.google.li, 43% (3 requests) were made to Google.li and 14% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (113 ms) belongs to the original domain Maps.google.li.
Page size can be reduced by 32.4 kB (64%)
50.4 kB
18.0 kB
In fact, the total size of Maps.google.li main page is 50.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. CSS take 43.6 kB which makes up the majority of the site volume.
Potential reduce by 1.2 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.2 kB or 58% of the original size.
Potential reduce by 0 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Maps Google images are well optimized though.
Potential reduce by 31.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Maps.google.li needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 72% of the original size.
We found no issues to fix!
4
4
The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maps Google. According to our analytics all requests are already optimized.
maps.google.li
113 ms
maps
36 ms
@
50 ms
css
58 ms
maia.css
20 ms
google_logo_41.png
19 ms
google_logo_41.png
34 ms
maps.google.li accessibility score
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
maps.google.li best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
maps.google.li SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.google.li can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Maps.google.li main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
maps.google.li
Open Graph description is not detected on the main page of Maps Google. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: