3.6 sec in total
312 ms
3.1 sec
151 ms
Visit documentation.civicrm.org now to see the best up-to-date Documentation CiviCRM content for Germany and also check out these interesting facts you probably never knew about documentation.civicrm.org
Visit documentation.civicrm.orgWe analyzed Documentation.civicrm.org page load time and found that the first response time was 312 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
documentation.civicrm.org performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.9 s
6/100
25%
Value5.1 s
62/100
10%
Value290 ms
79/100
30%
Value0.362
30/100
15%
Value6.9 s
54/100
10%
312 ms
750 ms
338 ms
299 ms
268 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Documentation.civicrm.org, 88% (50 requests) were made to Wiki.civicrm.org and 7% (4 requests) were made to Civicrm.org. The less responsive or slowest element that took the longest time to load (822 ms) relates to the external source Wiki.civicrm.org.
Page size can be reduced by 74.3 kB (70%)
105.5 kB
31.2 kB
In fact, the total size of Documentation.civicrm.org main page is 105.5 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. 30% of websites need less resources to load. HTML takes 80.2 kB which makes up the majority of the site volume.
Potential reduce by 68.6 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 10.0 kB, which is 12% 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 68.6 kB or 85% of the original size.
Potential reduce by 5.4 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, Documentation CiviCRM needs image optimization as it can save up to 5.4 kB or 71% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 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.
Potential reduce by 279 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. Documentation.civicrm.org needs all CSS files to be minified and compressed as it can save up to 279 B or 53% of the original size.
Number of requests can be reduced by 33 (62%)
53
20
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Documentation CiviCRM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
documentation.civicrm.org
312 ms
CiviCRM+Documentation
750 ms
batch.css
338 ms
batch.css
299 ms
batch.css
268 ms
batch.css
295 ms
batch.css
289 ms
confluence.extra.information:information-plugin-styles.css
291 ms
com.atlassian.confluence.plugins.pagetree:pagetree-resources.css
386 ms
com.atlassian.mywork.mywork-confluence-host-plugin:mw-header-anchor.css
386 ms
colors.css
401 ms
default-theme.css
374 ms
custom.css
361 ms
batch.js
822 ms
batch.js
424 ms
batch.js
769 ms
batch.js
415 ms
batch.js
417 ms
batch.js
425 ms
com.atlassian.confluence.plugins.pagetree:pagetree-resources.js
508 ms
com.atlassian.mywork.mywork-confluence-host-plugin:mw-header-anchor.js
512 ms
ga.js
203 ms
index.html
210 ms
white_menu_indicator.gif
123 ms
white_breadcrumbs_indicator.png
107 ms
menu_indicator.gif
119 ms
tools_20.png
103 ms
attachment_16.png
116 ms
page_history_16.png
114 ms
mail_content_16.gif
287 ms
lock_16_grey.png
273 ms
grey_arrow_down.gif
280 ms
grey_arrow_right.gif
280 ms
check.png
281 ms
civicrm-doc-wiki-header.jpg
284 ms
bullet_green_small.png
362 ms
information.png
353 ms
icons.png
380 ms
index.html
435 ms
i18n
168 ms
com.atlassian.confluence.plugins.confluence-like
151 ms
com.atlassian.confluence.plugins.share-page
154 ms
naturalchildren.action
143 ms
naturalchildren.action
133 ms
userpopup-shadows.png
145 ms
b.png
148 ms
__utm.gif
42 ms
a30aeec852418baad5b0d21e2d32e5c4
120 ms
likes
91 ms
comment-likes
100 ms
tree_plus.gif
129 ms
tree_square.gif
122 ms
batch.css
95 ms
header.css
84 ms
civi-header-bar-logo.png
166 ms
batch.css
92 ms
confluence.extra.information:information-plugin-styles.css
93 ms
documentation.civicrm.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.
documentation.civicrm.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
documentation.civicrm.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Documentation.civicrm.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 Documentation.civicrm.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.
documentation.civicrm.org
Open Graph description is not detected on the main page of Documentation CiviCRM. 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: