1.2 sec in total
54 ms
1 sec
111 ms
Click here to check amazing Maps Google content for Austria. Otherwise, check out these important facts you probably never knew about maps.google.at
Find local businesses, view maps and get driving directions in Google Maps.
Visit maps.google.atWe analyzed Maps.google.at page load time and found that the first response time was 54 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
maps.google.at performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value5.2 s
23/100
25%
Value3.9 s
83/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
54 ms
23 ms
63 ms
225 ms
74 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Maps.google.at, 57% (24 requests) were made to Google.at and 21% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.5 MB (72%)
2.1 MB
598.1 kB
In fact, the total size of Maps.google.at main page is 2.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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 545.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 545.4 kB or 74% of the original size.
Potential reduce by 2.9 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 20 (59%)
34
14
The browser has sent 34 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 21 to 1 for JavaScripts and as a result speed up the page load time.
maps.google.at
54 ms
maps
23 ms
@
63 ms
@
225 ms
common.js
74 ms
logging_serialization.js
86 ms
util.js
78 ms
onion.js
89 ms
marker.js
67 ms
layers.js
66 ms
poly.js
66 ms
desktop_ui.js
85 ms
printing.js
85 ms
ViewportInfoService.GetViewportInfo
410 ms
stats.js
58 ms
controls.js
81 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
355 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
397 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
540 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
542 ms
controls_common.js
49 ms
desktop_controls.js
79 ms
closure_ui.js
80 ms
cards.js
78 ms
desktop_cards_ui.js
264 ms
transparent.png
310 ms
desktop_spritesheet.png
319 ms
googlelogo_color_74x24dp.png
138 ms
googlelogo_62x24_with_2_stroke_color_66x26dp.png
138 ms
ViewportInfoService.GetViewportInfo
282 ms
kh
343 ms
mapcnt6.png
277 ms
sv5.png
273 ms
searchbox_library.js
105 ms
searchbox.js
106 ms
desktop_searchbox_ui.js
106 ms
tmapctrl.png
183 ms
cb_scout5.png
184 ms
tmapctrl4.png
183 ms
ic_directions_quantum.png
175 ms
@
234 ms
spinner_color.gif
38 ms
maps.google.at 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.at 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.at 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.at 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.at 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.at
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: