1.5 sec in total
70 ms
1.3 sec
187 ms
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.ltWe 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.
maps.google.lt performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value5.2 s
24/100
25%
Value3.9 s
83/100
10%
Value720 ms
41/100
30%
Value0
100/100
15%
Value5.9 s
66/100
10%
70 ms
27 ms
87 ms
223 ms
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 size can be reduced by 1.7 MB (55%)
3.1 MB
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.
Potential reduce by 665.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.
Potential reduce by 23.4 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.
Potential reduce by 992.0 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.
Number of requests can be reduced by 22 (29%)
75
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.
maps.google.lt
70 ms
maps
27 ms
@
87 ms
@
223 ms
common.js
83 ms
logging_serialization.js
84 ms
util.js
81 ms
onion.js
60 ms
openhand_8_8.cur
408 ms
marker.js
43 ms
layers.js
61 ms
poly.js
61 ms
desktop_ui.js
95 ms
printing.js
100 ms
v1_8758f7bb.png
390 ms
rs=AA2YrTs33gabkwDr4JwYH8vF35mufGVgkg
332 ms
ViewportInfoService.GetViewportInfo
484 ms
stats.js
76 ms
controls.js
88 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
468 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
512 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
525 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
553 ms
controls_common.js
108 ms
desktop_controls.js
124 ms
closure_ui.js
115 ms
searchbox_library.js
107 ms
searchbox.js
106 ms
desktop_searchbox_ui.js
120 ms
cards.js
361 ms
desktop_cards_ui.js
362 ms
transparent.png
361 ms
mapcnt6.png
409 ms
sv5.png
407 ms
googlelogo_color_74x24dp.png
230 ms
googlelogo_62x24_with_2_stroke_color_66x26dp.png
229 ms
desktop_spritesheet.png
281 ms
ic_directions_quantum.png
200 ms
spinner_color.gif
200 ms
ViewportInfoService.GetViewportInfo
197 ms
kh
234 ms
cb=gapi.loaded_0
186 ms
tmapctrl.png
188 ms
cb_scout5.png
198 ms
tmapctrl4.png
188 ms
@
121 ms
vt
93 ms
vt
81 ms
vt
59 ms
vt
58 ms
vt
59 ms
vt
98 ms
vt
120 ms
vt
104 ms
vt
124 ms
vt
127 ms
vt
152 ms
vt
141 ms
vt
150 ms
vt
179 ms
vt
182 ms
vt
164 ms
vt
198 ms
vt
184 ms
vt
203 ms
vt
216 ms
vt
231 ms
vt
232 ms
vt
240 ms
vt
227 ms
vt
251 ms
vt
257 ms
vt
293 ms
vt
284 ms
vt
288 ms
vt
286 ms
vt
317 ms
vt
296 ms
vt
323 ms
vt
325 ms
vt
345 ms
vt
274 ms
vt
301 ms
maps.google.lt 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.lt 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.lt 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.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.
maps.google.lt
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: