4 sec in total
363 ms
3.6 sec
119 ms
Welcome to jembi.org homepage info - get ready to check Jembi best content for Mozambique right away, or after learning these important things about jembi.org
Partnering with international aid organisations and governments to build human-centred health information system
Visit jembi.orgWe analyzed Jembi.org page load time and found that the first response time was 363 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
jembi.org performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value12.0 s
0/100
25%
Value5.4 s
57/100
10%
Value930 ms
30/100
30%
Value0.104
88/100
15%
Value12.4 s
14/100
10%
363 ms
528 ms
527 ms
935 ms
1092 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Jembi.org, 41% (16 requests) were made to Static.parastorage.com and 33% (13 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 578.2 kB (61%)
944.3 kB
366.0 kB
In fact, the total size of Jembi.org main page is 944.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. 65% of websites need less resources to load. HTML takes 709.3 kB which makes up the majority of the site volume.
Potential reduce by 561.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 561.2 kB or 79% of the original size.
Potential reduce by 17.0 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. Jembi images are well optimized though.
Potential reduce by 48 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 13 (45%)
29
16
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jembi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
www.jembi.org
363 ms
minified.js
528 ms
focus-within-polyfill.js
527 ms
polyfill.min.js
935 ms
bootstrap-features.24d4529b.bundle.min.js
1092 ms
main.24eb524d.bundle.min.js
1089 ms
lodash.min.js
899 ms
react.production.min.js
1087 ms
siteTags.bundle.min.js
1090 ms
wix-perf-measure.bundle.min.js
1089 ms
react-dom.production.min.js
1088 ms
hotjar-971223.js
1094 ms
cc44c7_28b0d55dfaea41d0a32e03529cc77992~mv2.png
1290 ms
thunderbolt
1171 ms
Image%20by%20Trevor%20Cole.jpg
1293 ms
cc44c7_0e905e49cd53484b96e92b31cd0e674c~mv2.png
1393 ms
IMG_7266_edited.png
1394 ms
IMG_7266_edited.png
1391 ms
IMG_7266_edited.jpg
1387 ms
09ad59ce71ae4243bc54251181afab81.png
642 ms
6a12a00025b94516b158d8a9365dd17b.png
643 ms
elementory-browser-support.min.js
447 ms
file.woff
293 ms
file.woff
357 ms
file.woff
609 ms
file.woff
479 ms
e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff
69 ms
file.woff
357 ms
97uahxiqZRoncBaCEI3aWz8E0i7KZn-EPnyo3HZu7kw.woff
63 ms
9_7S_tWeGDh5Pq3u05RVkj8E0i7KZn-EPnyo3HZu7kw.woff
63 ms
modules.cbd9768ba80ba0be5b17.js
176 ms
thunderbolt
121 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
217 ms
preact-incoming-feedback.20418d2133dcdcacb2fa.js
78 ms
font-hotjar_5.0ddfe2.ttf
8 ms
deprecation-en.v5.html
9 ms
bolt-performance
89 ms
deprecation-style.v5.css
47 ms
right-arrow.svg
44 ms
jembi.org accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
jembi.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
jembi.org SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jembi.org 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 Jembi.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.
jembi.org
Open Graph data is detected on the main page of Jembi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: