Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

maps.google.lt

Google Maps

Page Load Speed

1.5 sec in total

First Response

70 ms

Resources Loaded

1.3 sec

Page Rendered

187 ms

maps.google.lt screenshot

About Website

Click here to check amazing Maps Google content for Lithuania. Otherwise, check out these important facts you probably never knew about maps.google.lt

Find local businesses, view maps and get driving directions in Google Maps.

Visit maps.google.lt

Key Findings

We analyzed Maps.google.lt page load time and found that the first response time was 70 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

maps.google.lt performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

maps.google.lt

70 ms

maps

27 ms

@

87 ms

@

223 ms

common.js

83 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Maps.google.lt, 73% (61 requests) were made to Google.lt and 12% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (55%)

Content Size

3.1 MB

After Optimization

1.4 MB

In fact, the total size of Maps.google.lt main page is 3.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 665.4 kB

  • Original 898.9 kB
  • After minification 898.8 kB
  • After compression 233.4 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 665.4 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 23.4 kB

  • Original 868.7 kB
  • After minification 845.3 kB

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.

JavaScript Optimization

-77%

Potential reduce by 992.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 292.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 992.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (29%)

Requests Now

75

After Optimization

53

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maps Google. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

maps.google.lt accessibility score

92

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

maps.google.lt best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

maps.google.lt SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.google.lt 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.lt 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.

Social Sharing Optimization

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: