845 ms in total
22 ms
472 ms
351 ms
Click here to check amazing Places Google content for United States. Otherwise, check out these important facts you probably never knew about places.google.com
List your business on Google with a free Business Profile (formerly Google my Business). Turn people who find you on Search & Maps into new customers.
Visit places.google.comWe analyzed Places.google.com page load time and found that the first response time was 22 ms and then it took 823 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
places.google.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.4 s
68/100
25%
Value3.8 s
84/100
10%
Value2,340 ms
5/100
30%
Value0
100/100
15%
Value8.6 s
37/100
10%
22 ms
24 ms
32 ms
36 ms
45 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Places.google.com, 52% (26 requests) were made to Google.com and 12% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (145 ms) relates to the external source Google.com.
Page size can be reduced by 267.3 kB (13%)
2.1 MB
1.8 MB
In fact, the total size of Places.google.com 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 25.3 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. This page needs HTML code to be minified as it can gain 4.7 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.3 kB or 81% of the original size.
Potential reduce by 1.7 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. Places Google images are well optimized though.
Potential reduce by 137.2 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 137.2 kB or 65% of the original size.
Potential reduce by 103.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Places.google.com needs all CSS files to be minified and compressed as it can save up to 103.2 kB or 85% of the original size.
Number of requests can be reduced by 28 (68%)
41
13
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Places 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 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
places.google.com
22 ms
24 ms
css
32 ms
css
36 ms
css
45 ms
mybusiness.min.css
16 ms
basic.js
28 ms
picturefill.min.js
29 ms
angular.min.js
10 ms
angular-animate.min.js
11 ms
angular-messages.min.js
26 ms
peitho2.min.js
8 ms
mybusiness.min.js
26 ms
googlelogo_color_116x41dp.png
145 ms
icon-fab-scroll.png
8 ms
icon-footer-gplus.png
9 ms
icon-footer-blogger.png
12 ms
icon-footer-twitter.png
8 ms
icon-footer-youtube.png
9 ms
icon-footer-help.png
9 ms
googlelogo_color_116x41dp.png
12 ms
hero-browser_1x.png
23 ms
hero-results_1x.png
21 ms
hero-laptop-content-2_1x.png
42 ms
hero-animation-shadow_1x.png
24 ms
benefits-control_1x.png
80 ms
benefits-manage_1x.png
42 ms
benefits-show_1x.png
101 ms
add-business_1x.png
80 ms
gtm.js
42 ms
loader.js
5 ms
phone-4.js
3 ms
phone
116 ms
conversion_async.js
32 ms
analytics.js
15 ms
collect
12 ms
collect
14 ms
61 ms
64 ms
64 ms
57 ms
57 ms
64 ms
collect
90 ms
60 ms
61 ms
57 ms
54 ms
53 ms
57 ms
places.google.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
places.google.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
places.google.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Places.google.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Places.google.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.
places.google.com
Open Graph description is not detected on the main page of Places 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: