3 sec in total
329 ms
2.4 sec
273 ms
Welcome to oikoumene.org homepage info - get ready to check Oikoumene best content for United States right away, or after learning these important things about oikoumene.org
Inspiring the worldwide fellowship of churches to work together for unity, justice and peace.
Visit oikoumene.orgWe analyzed Oikoumene.org page load time and found that the first response time was 329 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
oikoumene.org performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value23.3 s
0/100
25%
Value16.1 s
0/100
10%
Value410 ms
67/100
30%
Value0.124
83/100
15%
Value21.2 s
1/100
10%
329 ms
215 ms
240 ms
963 ms
250 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 95% of them (53 requests) were addressed to the original Oikoumene.org, 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Oikoumene.org.
Page size can be reduced by 616.3 kB (68%)
911.5 kB
295.2 kB
In fact, the total size of Oikoumene.org main page is 911.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. 40% of websites need less resources to load. CSS take 467.6 kB which makes up the majority of the site volume.
Potential reduce by 31.0 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 6.1 kB, which is 16% 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 31.0 kB or 80% of the original size.
Potential reduce by 3.7 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. Oikoumene images are well optimized though.
Potential reduce by 154.1 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 154.1 kB or 66% of the original size.
Potential reduce by 427.5 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. Oikoumene.org needs all CSS files to be minified and compressed as it can save up to 427.5 kB or 91% of the original size.
Number of requests can be reduced by 35 (64%)
55
20
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oikoumene. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
en
329 ms
foundation-icons.css
215 ms
bss-slider.css
240 ms
app.css
963 ms
wccresponsive-theme-scheme-cachekey-570f355a9e0f9e58b50bd9c39e413182.css
250 ms
resourcejquery-cachekey-ca355366eac84fb8bf8fdfb5469a355c.css
251 ms
collective.js.jqueryui.custom.min-cachekey-6f92d55aea3635ed9fa93ec85036acc7.css
325 ms
resourceplone.app.discussion.stylesheetsdiscussion-cachekey-218b75944758547a2ff470dc2b0a5968.css
379 ms
resourceplone.formwidget.autocompletejquery.autocomplete-cachekey-ce3ead0d7026758be6ea21b69166e88a.css
380 ms
resourceplone.app.jquerytools.dateinput-cachekey-f65e1e103902b0a13c84cb6775460fbe.css
401 ms
faceted_view-cachekey-2ae95914534acf77ee6cd30b6b77f507.css
469 ms
resourcecollective.flowplayer.cssflowplayer-cachekey-55069f28ae474ed746d42e666b37c9bd.css
499 ms
resourcefl-play-cachekey-dea4804726431773c6e60c5b45da2ef0.css
496 ms
ploneCustom-cachekey-4b6de89235d297c321f86b070d1620bb.css
511 ms
resourcewcc.tinymcestyles-cachekey-6dadf73d7371a0537f804564694f64b8.css
544 ms
resourceplone.formwidget.datetimestyles-cachekey-cf7b11ea223621f1d98726fd4b242cb4.css
578 ms
resourcewcc.committeestyles-cachekey-552b750fbe97e60188f93293d2796b8c.css
620 ms
resourceplonetruegallery-portlet-cachekey-bed320bedffb4c9011abd33f9dc59ecd.css
623 ms
at-cachekey-79a1df580ab993efeb951958ddd1cc0e.kss
622 ms
themewccresponsive.themejsjquery-1.7.2.min-cachekey-8357958cccbc8f78dad484e67be1b77d.js
757 ms
jquery-integration-cachekey-2d55bfff8fc5dd3e0ce26292cf815fd4.js
789 ms
themewccresponsive.themejsmodernizr-cachekey-ea14f28ef0ee1a2071614071529c26fb.js
853 ms
livesearch-cachekey-116391115d0f6b9f420c8428205e5427.js
751 ms
resourceplone.formwidget.autocompletejquery.autocomplete.min-cachekey-0d2c7811058ae3cfbd8e4c1c13b0c864.js
1064 ms
faceted_view-cachekey-6bc07efddf8b32c4b722776bc7b8e039.js
875 ms
resourcecollective.flowplayerflowplayer.min-cachekey-8d524c27014894d873ec0b7ea6cd6d9c.js
877 ms
resourcewcc.carouselslider-cachekey-e139ed3754e72d83ee762bf2ca4f87a5.js
900 ms
resourceplonetruegallery-portlet-cachekey-caf0ac3fbcd44fc56b6a97cfaa56ab13.js
1014 ms
style.css
1014 ms
jquery.js
1093 ms
jquery.easing.js
1015 ms
script.js
1091 ms
homepage.js
1092 ms
foundation.min.js
1405 ms
tinynav.min.js
952 ms
better-simple-slideshow.min.js
952 ms
app.js
942 ms
logo-mobile-en.png
125 ms
logo.png
126 ms
button-search.png
126 ms
load-indicator.gif
179 ms
fb442421-7af0-47ec-af01-ebc366c92897.jpeg
182 ms
fa96f470-ff14-4fc5-bb3e-f6890e0dd265.jpeg
400 ms
2d08581d-b18f-40f0-9977-0317c10cebed.jpeg
462 ms
b4a2cdf3-605b-4e5a-ba77-40cb86fd8947.jpeg
255 ms
d97c76a8-8405-48b7-83d1-dd2855febf86.jpeg
399 ms
f2dee65a-f19e-4dee-aa04-d51744e55a38.jpeg
399 ms
facebook.png
399 ms
twitter.png
400 ms
gplus.png
424 ms
e5e1715b-3f25-4248-9468-504fcd2a53cf.png
422 ms
d89d7990-8a48-48f7-94a1-10ebd57de170.png
468 ms
ga.js
31 ms
__utm.gif
12 ms
__utm.gif
19 ms
slider-arrow-red.png
111 ms
oikoumene.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.
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
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.
oikoumene.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
oikoumene.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oikoumene.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 Oikoumene.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.
oikoumene.org
Open Graph description is not detected on the main page of Oikoumene. 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: