8 sec in total
2 sec
4.6 sec
1.4 sec
Click here to check amazing CEED content. Otherwise, check out these important facts you probably never knew about ceed.org
Bringing Justice to Sustainability Grounded in the lived experiences of low income and communities of color, we root our work in research, community
Visit ceed.orgWe analyzed Ceed.org page load time and found that the first response time was 2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ceed.org performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value7.7 s
3/100
25%
Value3.5 s
88/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value10.0 s
26/100
10%
2020 ms
92 ms
121 ms
257 ms
154 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 70% of them (60 requests) were addressed to the original Ceed.org, 12% (10 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ceed.org.
Page size can be reduced by 834.4 kB (16%)
5.3 MB
4.5 MB
In fact, the total size of Ceed.org main page is 5.3 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. 60% of websites need less resources to load. Images take 4.4 MB 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. 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 31.0 kB or 77% of the original size.
Potential reduce by 121.5 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. CEED images are well optimized though.
Potential reduce by 415.9 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 415.9 kB or 71% of the original size.
Potential reduce by 265.9 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. Ceed.org needs all CSS files to be minified and compressed as it can save up to 265.9 kB or 77% of the original size.
Number of requests can be reduced by 52 (63%)
83
31
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CEED. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
ceed.org
2020 ms
css
92 ms
styles.css
121 ms
bootstrap.min.css
257 ms
font-awesome.min.css
154 ms
main.css
156 ms
style.css
118 ms
jquery-ui-1.11.4.custom.css
135 ms
mediaelementplayer.min.css
199 ms
wp-mediaelement.css
173 ms
wpv-pagination.css
190 ms
ytprefs.min.css
205 ms
styles.css
213 ms
jquery.js
330 ms
jquery-migrate.min.js
231 ms
modernizr.min.js
247 ms
respond.min.js
245 ms
html5shiv.js
262 ms
jquery.min.js
53 ms
ytprefs.min.js
290 ms
effects.css
329 ms
style.css
251 ms
dashicons.min.css
264 ms
thickbox.css
256 ms
jquery.form.min.js
301 ms
scripts.js
299 ms
qppr_frontend_script.min.js
295 ms
bootstrap.min.js
305 ms
main.js
331 ms
core.min.js
345 ms
datepicker.min.js
390 ms
mediaelement-and-player.min.js
408 ms
wp-mediaelement.js
355 ms
underscore.min.js
372 ms
wp-util.min.js
375 ms
backbone.min.js
421 ms
wp-playlist.js
404 ms
wpv-pagination-embedded.js
657 ms
fitvids.min.js
437 ms
wp-embed.min.js
377 ms
front_end_js.js
392 ms
thickbox.js
377 ms
flexvideo.css
360 ms
wp-emoji-release.min.js
558 ms
analytics.js
194 ms
iframe_api
101 ms
donate_now.png
410 ms
logo-2.png
161 ms
pagination_dots.png
99 ms
DSC_1168.jpg
621 ms
1.png
101 ms
bg-brown-1.png
95 ms
India2008-1-300x300.jpg
157 ms
DSC_1168-300x300.jpg
155 ms
ev-300x300.jpg
157 ms
z6-300x300.jpg
156 ms
4126689583_90fa1f5ef4_o1-300x300.jpg
401 ms
DSC_1248-300x300.jpg
367 ms
EPSON001-300x300.jpg
178 ms
logo.png
422 ms
fontawesome-webfont.woff
299 ms
glyphicons-halflings-regular.woff
299 ms
collect
255 ms
www-widgetapi.js
27 ms
7b22616374696f6e223a227770765f6765745f70616765222c2270616765223a322c22766965775f6e756d626572223a22313335382d434154545264353439303833373233383339323066653636623431343139316361633539374350494431333630222c227770765f636f6c756d6e5f736f72745f6964223a226d656e755f6f72646572222c227770765f636f6c756d6e5f736f72745f646972223a2264657363222c227770765f766965775f7769646765745f6964223a302c22766965775f68617368223a2265794a755957316c496a6f69614739745a53317a62476c6b5a5849694c434a705a484d694f6949784e4459324c4341784e4445304c4341784e444977496e303d222c22706f73745f6964223a2231333630222c226470735f7072223a7b7d2c226470735f67656e6572616c223a7b7d2c226765745f706172616d73223a7b7d7d
1593 ms
7b22616374696f6e223a227770765f6765745f70616765222c2270616765223a332c22766965775f6e756d626572223a22313335382d434154545264353439303833373233383339323066653636623431343139316361633539374350494431333630222c227770765f636f6c756d6e5f736f72745f6964223a226d656e755f6f72646572222c227770765f636f6c756d6e5f736f72745f646972223a2264657363222c227770765f766965775f7769646765745f6964223a302c22766965775f68617368223a2265794a755957316c496a6f69614739745a53317a62476c6b5a5849694c434a705a484d694f6949784e4459324c4341784e4445304c4341784e444977496e303d222c22706f73745f6964223a2231333630222c226470735f7072223a7b7d2c226470735f67656e6572616c223a7b7d2c226765745f706172616d73223a7b7d7d
576 ms
loadingAnimation.gif
58 ms
page.php
83 ms
bC7hIHbP4Mf.css
298 ms
q68gy-v_YMF.js
503 ms
YvxwM8R7ol8.js
634 ms
ihptErjAmMX.js
569 ms
12366254_869039526544439_4860955561393821311_n.jpg
428 ms
178950_229751067139958_645183045_n.jpg
493 ms
12038522_1514594272194839_8277005462211096951_n.jpg
561 ms
547908_608092075936878_548265258_n.jpg
626 ms
12705646_10205717085187680_2917458481732840003_n.jpg
629 ms
316709_253368381362527_777284_n.jpg
627 ms
12243431_127702120927893_9107540165684066086_n.jpg
699 ms
10622899_10202702901162596_8800236201729906045_n.jpg
627 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
73 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
72 ms
kDOzhTr2W91.js
145 ms
ceed.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
ceed.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ceed.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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ceed.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 Ceed.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.
ceed.org
Open Graph data is detected on the main page of CEED. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: