297 ms in total
11 ms
145 ms
141 ms
Click here to check amazing DATIM content for Rwanda. Otherwise, check out these important facts you probably never knew about datim.org
DHIS 2
Visit datim.orgWe analyzed Datim.org page load time and found that the first response time was 11 ms and then it took 286 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
datim.org performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value1.6 s
99/100
25%
Value1.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
11 ms
12 ms
11 ms
31 ms
58 ms
Our browser made a total of 12 requests to load all elements on the main page. We found that 92% of them (11 requests) were addressed to the original Datim.org, 8% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (74 ms) relates to the external source Fonts.googleapis.com.
Page size can be reduced by 3.9 kB (11%)
36.3 kB
32.3 kB
In fact, the total size of Datim.org main page is 36.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 30.9 kB which makes up the majority of the site volume.
Potential reduce by 3.8 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 1.3 kB, which is 24% 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 3.8 kB or 70% of the original size.
Potential reduce by 173 B
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. DATIM images are well optimized though.
Number of requests can be reduced by 3 (33%)
9
6
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DATIM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
datim.org
11 ms
login.action;jsessionid=A6DEF8F9C098D85D03CF13D7657E6A5E
12 ms
jquery.min.js
11 ms
login.js
31 ms
widgets.css
58 ms
login.css
29 ms
external
60 ms
icon
74 ms
pepfar.png
10 ms
logo_front_DATIM.png
10 ms
LiberationSans-Bold-webfont.woff
10 ms
logo_front.png
3 ms
datim.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
datim.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
datim.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Datim.org 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 Datim.org 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.
datim.org
Open Graph description is not detected on the main page of DATIM. 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: