10.2 sec in total
66 ms
10 sec
145 ms
Welcome to wiki.openmrs.org homepage info - get ready to check Wiki OpenMRS best content for India right away, or after learning these important things about wiki.openmrs.org
Visit wiki.openmrs.orgWe analyzed Wiki.openmrs.org page load time and found that the first response time was 66 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wiki.openmrs.org performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value5.3 s
22/100
25%
Value5.0 s
63/100
10%
Value200 ms
89/100
30%
Value0.183
66/100
15%
Value5.6 s
69/100
10%
66 ms
2262 ms
123 ms
261 ms
90 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 81% of them (50 requests) were addressed to the original Wiki.openmrs.org, 6% (4 requests) were made to Id.openmrs.org and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Wiki.openmrs.org.
Page size can be reduced by 275.1 kB (78%)
354.9 kB
79.7 kB
In fact, the total size of Wiki.openmrs.org main page is 354.9 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. 50% of websites need less resources to load. HTML takes 235.5 kB which makes up the majority of the site volume.
Potential reduce by 208.5 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 34.8 kB, which is 15% 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 208.5 kB or 89% of the original size.
Potential reduce by 2.8 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, Wiki OpenMRS needs image optimization as it can save up to 2.8 kB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 63.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 63.7 kB or 56% of the original size.
Potential reduce by 153 B
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. Wiki.openmrs.org needs all CSS files to be minified and compressed as it can save up to 153 B or 44% of the original size.
Number of requests can be reduced by 28 (52%)
54
26
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiki OpenMRS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
wiki.openmrs.org
66 ms
Home
2262 ms
batch.css
123 ms
batch.css
261 ms
batch.css
90 ms
confluence.macros.dashboard:dashboard-macros-resources.css
83 ms
confluence.extra.information:information-plugin-adg-styles.css
84 ms
batch.js
206 ms
batch.js
353 ms
batch.js
119 ms
confluence.macros.dashboard:dashboard-macros-resources.js
140 ms
colors.css
158 ms
custom.css
152 ms
app-optimized.js
240 ms
doc-theme.js
159 ms
css
57 ms
batch.css
32 ms
batch.css
78 ms
analytics.js
244 ms
confluence-logo.png
65 ms
global.logo
63 ms
red_padlock.png
54 ms
grey_attach.png
54 ms
feed-icon-16x16.png
53 ms
33211eb1a0ae02c7.png
238 ms
talk-chairs.png
237 ms
sidebar-shadow.png
197 ms
tree.png
187 ms
vgrabber.gif
186 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
208 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
207 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
280 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
283 ms
atlassian-icons.woff
206 ms
f7740989739f3096d24a429f83c6c367
180 ms
panel-items
180 ms
likes
166 ms
comment-likes
158 ms
naturalchildren.action
341 ms
comments
133 ms
style.css
41 ms
userpopup-shadows.png
126 ms
b.png
126 ms
collect
65 ms
collect
102 ms
subcalendars.json
161 ms
globalnav
37 ms
editor.action
157 ms
batch.js
254 ms
batch.css
328 ms
search-white.png
31 ms
events.json
732 ms
events.json
98 ms
events.json
5566 ms
status.json
82 ms
other_16.png
214 ms
jcaptcha
194 ms
browse-macros.action
139 ms
com.gliffy.integration.confluence.ANALYTICS_OFF
37 ms
tips
37 ms
events_24.png
31 ms
batch.css
118 ms
wiki.openmrs.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
wiki.openmrs.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wiki.openmrs.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Wiki.openmrs.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 Wiki.openmrs.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.
wiki.openmrs.org
Open Graph description is not detected on the main page of Wiki OpenMRS. 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: