5.9 sec in total
1.6 sec
4 sec
255 ms
Click here to check amazing ECKAN content. Otherwise, check out these important facts you probably never knew about eckan.org
ECKAN serves needs in East-Central Kansas, helping people leave poverty behind forever. Get support with housing, Head Start, food, and essential needs. Make a tax-deductible donation.
Visit eckan.orgWe analyzed Eckan.org page load time and found that the first response time was 1.6 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eckan.org performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value7.3 s
5/100
25%
Value11.7 s
4/100
10%
Value1,230 ms
20/100
30%
Value0.098
90/100
15%
Value13.4 s
11/100
10%
1647 ms
195 ms
28 ms
72 ms
127 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 84% of them (46 requests) were addressed to the original Eckan.org, 5% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Eckan.org.
Page size can be reduced by 867.8 kB (35%)
2.5 MB
1.6 MB
In fact, the total size of Eckan.org main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 63.4 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 63.4 kB or 85% of the original size.
Potential reduce by 27.1 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. ECKAN images are well optimized though.
Potential reduce by 223.3 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 223.3 kB or 68% of the original size.
Potential reduce by 554.0 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. Eckan.org needs all CSS files to be minified and compressed as it can save up to 554.0 kB or 86% of the original size.
Number of requests can be reduced by 34 (71%)
48
14
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECKAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.eckan.org
1647 ms
hmf7hbt.js
195 ms
css
28 ms
cff-style.css
72 ms
style-structure.css
127 ms
style.css
131 ms
chosen.css
134 ms
frontend.css
139 ms
tribe-events-full.min.css
147 ms
grid.css
144 ms
base.css
196 ms
layout.css
275 ms
shortcodes.css
280 ms
magnific-popup.css
206 ms
mediaelementplayer.css
217 ms
enfold_child.css
299 ms
custom.css
248 ms
style.css
279 ms
event-mod.css
291 ms
font-awesome.min.css
59 ms
jquery.js
434 ms
jquery-migrate.min.js
341 ms
epl.js
343 ms
jquery-front-scripts.js
349 ms
avia-compat.js
360 ms
js
59 ms
cff-scripts.js
369 ms
avia.js
533 ms
shortcodes.js
569 ms
jquery.magnific-popup.min.js
417 ms
mediaelement-and-player.min.js
533 ms
wp-mediaelement.min.js
531 ms
comment-reply.min.js
532 ms
wp-embed.min.js
532 ms
wp-emoji-release.min.js
481 ms
logo-trans-300x80.png
218 ms
ECKAN-FADE-LOGO.png
740 ms
ECKAN-SIGN-1500x430.jpg
298 ms
sketch-of-1320-1500x430.jpg
301 ms
All-Staff-1280x430.jpg
423 ms
Anderson-County-300x192.png
356 ms
Coffey-resized-300x192.jpg
208 ms
Douglas-Co-300x192.png
458 ms
Franklin-CO-300x192.png
372 ms
Lyon-County-300x192.jpg
367 ms
Morris-Co-300x180.png
527 ms
Osage-co-300x192.png
509 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
15 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
14 ms
entypo-fontello.woff
349 ms
sKd0EMYPAh5PYCRKSryvW6CWcynf_cDxXwCLxiixG1c.ttf
15 ms
fontawesomeregular.woff
471 ms
fontawesome-webfont.woff
104 ms
tribe-events-full-mobile.min.css
76 ms
print.css
76 ms
eckan.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.
eckan.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
eckan.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
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 Eckan.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 Eckan.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.
eckan.org
Open Graph description is not detected on the main page of ECKAN. 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: