2 sec in total
85 ms
1.7 sec
281 ms
Visit maps.google.hu now to see the best up-to-date Maps Google content for Hungary and also check out these interesting facts you probably never knew about maps.google.hu
Find local businesses, view maps and get driving directions in Google Maps.
Visit maps.google.huWe analyzed Maps.google.hu page load time and found that the first response time was 85 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
maps.google.hu performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value5.2 s
23/100
25%
Value3.9 s
83/100
10%
Value1,240 ms
19/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
85 ms
33 ms
58 ms
212 ms
82 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Maps.google.hu, 78% (66 requests) were made to Google.hu and 12% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (823 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.6 MB (47%)
3.3 MB
1.7 MB
In fact, the total size of Maps.google.hu main page is 3.3 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. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 547.6 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 547.6 kB or 75% of the original size.
Potential reduce by 25.8 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.6 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.6 kB or 77% of the original size.
Number of requests can be reduced by 25 (32%)
77
52
The browser has sent 77 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.hu
85 ms
maps
33 ms
@
58 ms
@
212 ms
common.js
82 ms
logging_serialization.js
95 ms
util.js
112 ms
onion.js
110 ms
openhand_8_8.cur
719 ms
marker.js
114 ms
layers.js
113 ms
poly.js
111 ms
desktop_ui.js
112 ms
printing.js
113 ms
ViewportInfoService.GetViewportInfo
703 ms
stats.js
107 ms
controls.js
102 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
508 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
693 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
795 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
823 ms
controls_common.js
99 ms
desktop_controls.js
99 ms
closure_ui.js
172 ms
searchbox_library.js
284 ms
searchbox.js
285 ms
desktop_searchbox_ui.js
285 ms
cards.js
285 ms
desktop_cards_ui.js
501 ms
transparent.png
628 ms
mapcnt6.png
618 ms
sv5.png
621 ms
desktop_spritesheet.png
500 ms
googlelogo_color_74x24dp.png
287 ms
googlelogo_62x24_with_2_stroke_color_66x26dp.png
288 ms
ViewportInfoService.GetViewportInfo
264 ms
kh
324 ms
tmapctrl.png
271 ms
cb_scout5.png
298 ms
tmapctrl4.png
294 ms
ic_directions_quantum.png
143 ms
spinner_color.gif
143 ms
@47.15984,19.500732,7z
139 ms
vt
202 ms
vt
117 ms
vt
85 ms
vt
88 ms
vt
87 ms
vt
103 ms
vt
141 ms
vt
135 ms
vt
152 ms
vt
168 ms
vt
168 ms
vt
199 ms
vt
183 ms
vt
224 ms
vt
212 ms
vt
251 ms
vt
227 ms
vt
261 ms
vt
270 ms
vt
275 ms
vt
294 ms
vt
283 ms
vt
291 ms
vt
315 ms
vt
329 ms
vt
348 ms
vt
341 ms
vt
358 ms
vt
357 ms
vt
379 ms
vt
378 ms
vt
383 ms
vt
418 ms
vt
413 ms
vt
420 ms
vt
436 ms
vt
376 ms
vt
386 ms
vt
423 ms
vt
395 ms
vt
388 ms
vt
373 ms
maps.google.hu 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.hu 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.hu 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.hu 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.hu 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.hu
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: