Tools & Wizards About Us
googlemaps.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

googlemaps.com

Google Maps

Page Load Speed

1.8 sec in total

First Response

21 ms

Resources Loaded

1.6 sec

Page Rendered

187 ms

googlemaps.com screenshot

About Website

Click here to check amazing Google Maps content for United States. Otherwise, check out these important facts you probably never knew about googlemaps.com

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

Visit googlemaps.com

Key Findings

We analyzed Googlemaps.com page load time and found that the first response time was 21 ms and then it took 1.8 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.

Performance Metrics

googlemaps.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.1 s

86/100

10%

Network Requests Diagram

googlemaps.com

21 ms

maps.google.com

47 ms

maps

42 ms

@

65 ms

@

282 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Googlemaps.com, 74% (66 requests) were made to Google.com and 11% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (992 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Googlemaps.com main page is 2.9 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 671.6 kB

  • Original 904.3 kB
  • After minification 904.2 kB
  • After compression 232.7 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 671.6 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 24.3 kB

  • Original 717.0 kB
  • After minification 692.6 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. Google Maps images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 989.8 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 289.9 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 989.8 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

80

After Optimization

58

  • AJAX
  • Images
  • JavaScript

The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Google Maps. 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.

Network Requests Diagram

googlemaps.com

googlemaps.com

21 ms

maps.google.com

maps.google.com

47 ms

maps

maps

42 ms

@

@

65 ms

@

@

282 ms

common.js

common.js

120 ms

logging_serialization.js

logging_serialization.js

121 ms

util.js

util.js

165 ms

onion.js

onion.js

120 ms

openhand_8_8.cur

openhand_8_8.cur

912 ms

marker.js

marker.js

166 ms

layers.js

layers.js

166 ms

poly.js

poly.js

166 ms

desktop_ui.js

desktop_ui.js

164 ms

printing.js

printing.js

163 ms

v1_8758f7bb.png

v1_8758f7bb.png

902 ms

rs=AA2YrTs33gabkwDr4JwYH8vF35mufGVgkg

rs=AA2YrTs33gabkwDr4JwYH8vF35mufGVgkg

813 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

890 ms

stats.js

stats.js

133 ms

controls.js

controls.js

147 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

853 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

878 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

970 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

992 ms

controls_common.js

controls_common.js

142 ms

desktop_controls.js

desktop_controls.js

142 ms

closure_ui.js

closure_ui.js

141 ms

searchbox_library.js

searchbox_library.js

141 ms

searchbox.js

searchbox.js

402 ms

desktop_searchbox_ui.js

desktop_searchbox_ui.js

403 ms

cards.js

cards.js

402 ms

desktop_cards_ui.js

desktop_cards_ui.js

279 ms

googlelogo_color_74x24dp.png

googlelogo_color_74x24dp.png

570 ms

googlelogo_62x24_with_2_stroke_color_66x26dp.png

googlelogo_62x24_with_2_stroke_color_66x26dp.png

570 ms

transparent.png

transparent.png

676 ms

desktop_spritesheet.png

desktop_spritesheet.png

687 ms

mapcnt6.png

mapcnt6.png

561 ms

sv5.png

sv5.png

560 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

459 ms

kh

kh

571 ms

@

@

272 ms

tmapctrl.png

tmapctrl.png

246 ms

cb_scout5.png

cb_scout5.png

267 ms

tmapctrl4.png

tmapctrl4.png

271 ms

ic_directions_quantum.png

ic_directions_quantum.png

270 ms

spinner_color.gif

spinner_color.gif

219 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

233 ms

vt

vt

111 ms

vt

vt

74 ms

vt

vt

43 ms

vt

vt

41 ms

vt

vt

44 ms

vt

vt

43 ms

vt

vt

47 ms

vt

vt

64 ms

vt

vt

46 ms

vt

vt

47 ms

vt

vt

66 ms

vt

vt

63 ms

vt

vt

65 ms

vt

vt

70 ms

vt

vt

110 ms

vt

vt

67 ms

vt

vt

69 ms

vt

vt

68 ms

vt

vt

69 ms

vt

vt

113 ms

vt

vt

69 ms

vt

vt

102 ms

vt

vt

70 ms

vt

vt

70 ms

vt

vt

71 ms

vt

vt

72 ms

vt

vt

72 ms

vt

vt

72 ms

vt

vt

111 ms

vt

vt

72 ms

vt

vt

102 ms

vt

vt

99 ms

vt

vt

99 ms

vt

vt

102 ms

vt

vt

110 ms

vt

vt

74 ms

vt

vt

70 ms

vt

vt

71 ms

vt

vt

79 ms

vt

vt

67 ms

vt

vt

68 ms

vt

vt

68 ms

Accessibility Review

googlemaps.com 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

googlemaps.com best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

googlemaps.com 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 Googlemaps.com 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 Googlemaps.com 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

googlemaps.com

Open Graph description is not detected on the main page of Google Maps. 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: