1.6 sec in total
33 ms
1.4 sec
168 ms
Click here to check amazing Maps Google content for Puerto Rico. Otherwise, check out these important facts you probably never knew about maps.google.com.pr
Find local businesses, view maps and get driving directions in Google Maps.
Visit maps.google.com.prWe analyzed Maps.google.com.pr page load time and found that the first response time was 33 ms and then it took 1.6 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.com.pr performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value5.3 s
22/100
25%
Value3.9 s
83/100
10%
Value1,330 ms
17/100
30%
Value0
100/100
15%
Value6.4 s
59/100
10%
33 ms
71 ms
249 ms
122 ms
138 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Maps.google.com.pr, 73% (61 requests) were made to Google.com.pr and 12% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (806 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.7 MB (67%)
2.5 MB
802.6 kB
In fact, the total size of Maps.google.com.pr main page is 2.5 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 669.2 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 669.2 kB or 74% of the original size.
Potential reduce by 5.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. Maps Google images are well optimized though.
Potential reduce by 990.8 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 990.8 kB or 77% of the original size.
Number of requests can be reduced by 45 (59%)
76
31
The browser has sent 76 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
33 ms
@
71 ms
@
249 ms
common.js
122 ms
logging_serialization.js
138 ms
util.js
166 ms
onion.js
167 ms
openhand_8_8.cur
597 ms
marker.js
171 ms
layers.js
171 ms
poly.js
172 ms
desktop_ui.js
168 ms
printing.js
169 ms
v1_8758f7bb.png
738 ms
rs=AA2YrTs33gabkwDr4JwYH8vF35mufGVgkg
562 ms
ViewportInfoService.GetViewportInfo
715 ms
stats.js
139 ms
controls.js
128 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
701 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
740 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
791 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
806 ms
controls_common.js
122 ms
desktop_controls.js
122 ms
closure_ui.js
190 ms
searchbox_library.js
190 ms
searchbox.js
189 ms
desktop_searchbox_ui.js
401 ms
cards.js
401 ms
desktop_cards_ui.js
527 ms
transparent.png
508 ms
mapcnt6.png
396 ms
sv5.png
432 ms
desktop_spritesheet.png
479 ms
googlelogo_color_74x24dp.png
278 ms
googlelogo_62x24_with_2_stroke_color_66x26dp.png
304 ms
ViewportInfoService.GetViewportInfo
339 ms
kh
399 ms
kh
398 ms
tmapctrl.png
333 ms
cb_scout5.png
378 ms
tmapctrl4.png
336 ms
ic_directions_quantum.png
217 ms
spinner_color.gif
266 ms
cb=gapi.loaded_0
274 ms
@18.198625,-66.583635,9z
144 ms
vt
73 ms
vt
69 ms
vt
66 ms
vt
64 ms
vt
42 ms
vt
73 ms
vt
78 ms
vt
69 ms
vt
75 ms
vt
76 ms
vt
91 ms
vt
95 ms
vt
89 ms
vt
92 ms
vt
109 ms
vt
112 ms
vt
112 ms
vt
151 ms
vt
110 ms
vt
110 ms
vt
126 ms
vt
129 ms
vt
134 ms
vt
137 ms
vt
126 ms
vt
142 ms
vt
143 ms
vt
171 ms
vt
158 ms
vt
165 ms
vt
162 ms
vt
164 ms
vt
169 ms
vt
191 ms
vt
180 ms
vt
142 ms
vt
144 ms
maps.google.com.pr 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.com.pr 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.com.pr 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.com.pr 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.com.pr 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.com.pr
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: