1.6 sec in total
56 ms
1.3 sec
221 ms
Visit maps.google.co.ug now to see the best up-to-date Maps Google content for Uganda and also check out these interesting facts you probably never knew about maps.google.co.ug
Find local businesses, view maps and get driving directions in Google Maps.
Visit maps.google.co.ugWe analyzed Maps.google.co.ug page load time and found that the first response time was 56 ms and then it took 1.5 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.co.ug performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value5.6 s
17/100
25%
Value4.5 s
72/100
10%
Value1,770 ms
10/100
30%
Value0
100/100
15%
Value7.0 s
53/100
10%
56 ms
33 ms
67 ms
258 ms
78 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Maps.google.co.ug, 75% (61 requests) were made to Google.co.ug and 12% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (504 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 1.6 MB (61%)
2.5 MB
973.3 kB
In fact, the total size of Maps.google.co.ug 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. 55% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 543.9 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 543.9 kB or 75% of the original size.
Potential reduce by 16.2 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.7 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.7 kB or 77% of the original size.
Number of requests can be reduced by 20 (27%)
73
53
The browser has sent 73 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.co.ug
56 ms
maps
33 ms
@
67 ms
@
258 ms
common.js
78 ms
logging_serialization.js
117 ms
util.js
91 ms
onion.js
118 ms
openhand_8_8.cur
157 ms
marker.js
96 ms
layers.js
105 ms
poly.js
103 ms
desktop_ui.js
102 ms
printing.js
102 ms
ViewportInfoService.GetViewportInfo
439 ms
stats.js
113 ms
controls.js
126 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
126 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
223 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
431 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
504 ms
controls_common.js
115 ms
desktop_controls.js
123 ms
closure_ui.js
114 ms
searchbox_library.js
122 ms
searchbox.js
121 ms
desktop_searchbox_ui.js
218 ms
cards.js
219 ms
desktop_cards_ui.js
218 ms
transparent.png
354 ms
desktop_spritesheet.png
331 ms
googlelogo_color_74x24dp.png
122 ms
googlelogo_62x24_with_2_stroke_color_66x26dp.png
122 ms
@
189 ms
mapcnt6.png
122 ms
sv5.png
144 ms
ic_directions_quantum.png
146 ms
ViewportInfoService.GetViewportInfo
109 ms
kh
145 ms
kh
115 ms
tmapctrl.png
73 ms
cb_scout5.png
88 ms
tmapctrl4.png
106 ms
spinner_color.gif
96 ms
vt
95 ms
vt
71 ms
vt
61 ms
vt
67 ms
vt
83 ms
vt
106 ms
vt
99 ms
vt
108 ms
vt
135 ms
vt
116 ms
vt
147 ms
vt
131 ms
vt
147 ms
vt
153 ms
vt
154 ms
vt
221 ms
vt
177 ms
vt
178 ms
vt
191 ms
vt
199 ms
vt
194 ms
vt
214 ms
vt
217 ms
vt
225 ms
vt
240 ms
vt
259 ms
vt
260 ms
vt
262 ms
vt
260 ms
vt
271 ms
vt
276 ms
vt
288 ms
vt
283 ms
vt
267 ms
vt
261 ms
vt
263 ms
vt
248 ms
maps.google.co.ug 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.co.ug 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.co.ug 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.co.ug 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.co.ug 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.co.ug
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: