6.5 sec in total
775 ms
5.1 sec
639 ms
Click here to check amazing Opendata Go content for Kenya. Otherwise, check out these important facts you probably never knew about opendata.go.ke
Discover, analyze and download data from ArcGIS Hub. Download in CSV, KML, Zip, GeoJSON, GeoTIFF or PNG. Find API links for GeoServices, WMS, and WFS. Analyze with charts and thematic maps. Take the n...
Visit opendata.go.keWe analyzed Opendata.go.ke page load time and found that the first response time was 775 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
opendata.go.ke performance score
775 ms
839 ms
158 ms
259 ms
258 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 83% of them (55 requests) were addressed to the original Opendata.go.ke, 5% (3 requests) were made to Google-analytics.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Opendata.go.ke.
Page size can be reduced by 962.0 kB (71%)
1.4 MB
395.6 kB
In fact, the total size of Opendata.go.ke main page is 1.4 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. Javascripts take 923.2 kB which makes up the majority of the site volume.
Potential reduce by 146.1 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 146.1 kB or 78% of the original size.
Potential reduce by 2.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. Obviously, Opendata Go needs image optimization as it can save up to 2.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 614.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 614.8 kB or 67% of the original size.
Potential reduce by 198.4 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. Opendata.go.ke needs all CSS files to be minified and compressed as it can save up to 198.4 kB or 84% of the original size.
Number of requests can be reduced by 12 (21%)
56
44
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Opendata Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
opendata.go.ke
775 ms
opendata.go.ke
839 ms
base.css
158 ms
socrata-apps.css
259 ms
errors.js
258 ms
components.css
255 ms
current_site.css
329 ms
mixpanel-analytics.js
278 ms
3913128A-3EEC-47A6-8FE8-67867745C221
408 ms
base.js
731 ms
canvas.js
434 ms
kenya.socrata.com.js
570 ms
jquery.min.js
23 ms
analytics.js
56 ms
349DD1F4-D248-4704-A14D-1B3107C1A95F
82 ms
3C631F7E-A492-4984-A08D-CE792681AEC1
158 ms
B0FF46C1-C95A-45BE-A178-5C4687D525DC
723 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
60 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
68 ms
ss-pika.woff
365 ms
collect
32 ms
widgets.js
170 ms
font-awesome.min.css
48 ms
mixpanel-2.2.min.js
51 ms
bk5y-yyvt.json
118 ms
vu56-ccc2.json
132 ms
xnnd-jbzu.json
170 ms
n9m7-b3h3.json
172 ms
ad56-wdbr.json
134 ms
views.json
496 ms
views.json
352 ms
views.json
376 ms
views.json
456 ms
site_metrics.json
781 ms
views.json
815 ms
views.json
1159 ms
spinner_background.png
441 ms
collect
17 ms
menu_icons.png
506 ms
fontawesome-webfont.woff
8 ms
views.json
595 ms
views.json
631 ms
views.json
610 ms
views.json
819 ms
views.json
815 ms
views.json
830 ms
views.json
881 ms
views.json
899 ms
views.json
1041 ms
views.json
1096 ms
views.json
1047 ms
VDp5Sgg7X9VkZsQoPIj98-Lci3hSX5x3nlSNTkKUUUM
1458 ms
o0_v0DV9dQqEtlTGehQAdrGCo27W0eA9ZwoOMU88HEk
1475 ms
JACiz6m5bW1mwMNIR3t61q0uCdTcjN1XbqLCUxNKOHM
2390 ms
9l7dzORZXJ3_doJnnCLZz9pjA5FlZGJHuX7KOR0-CUE
1926 ms
c7f291ce-b102-42ef-972f-1a653c1a35b9
1803 ms
862f4792-dcfb-4b7c-abbd-0b406ecf93fe
1784 ms
9741afa4-8f02-4724-adc4-ded06766f8c5
2061 ms
dBQ11WRrY7WdmK8MfoHmUXj9clYj1Umvz3kqL8LdsmQ
1895 ms
ajax-loader.gif
1948 ms
fab1d43e-c291-4874-bb73-1025cb46b06f
2322 ms
80d2dac3-1d3b-4c2f-8271-fb31dd19abee
2401 ms
8c0b9866-bdcb-480b-8092-3c0bedf58a45
2051 ms
356C5785-84E6-467C-A442-DE501CD1119F
2018 ms
print.css
82 ms
opendata.go.ke SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opendata.go.ke 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 Opendata.go.ke 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.
opendata.go.ke
Open Graph description is not detected on the main page of Opendata Go. 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: