3.5 sec in total
253 ms
2.9 sec
395 ms
Welcome to creationcare.org homepage info - get ready to check Creationcare best content for United States right away, or after learning these important things about creationcare.org
The Evangelical Environmental Network (EEN) is a ministry that educates, inspires, and mobilizes Christians in their effort to care for God's creation.
Visit creationcare.orgWe analyzed Creationcare.org page load time and found that the first response time was 253 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
creationcare.org performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value26.5 s
0/100
25%
Value4.6 s
70/100
10%
Value330 ms
75/100
30%
Value0.004
100/100
15%
Value7.8 s
45/100
10%
253 ms
9 ms
165 ms
198 ms
178 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Creationcare.org, 16% (16 requests) were made to Static.xx.fbcdn.net and 13% (13 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (492 ms) relates to the external source Facebook.com.
Page size can be reduced by 566.6 kB (35%)
1.6 MB
1.1 MB
In fact, the total size of Creationcare.org main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 825.5 kB which makes up the majority of the site volume.
Potential reduce by 55.8 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 55.8 kB or 74% of the original size.
Potential reduce by 6.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. Creationcare images are well optimized though.
Potential reduce by 479.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 479.3 kB or 71% of the original size.
Potential reduce by 25.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. Creationcare.org needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 48% of the original size.
Number of requests can be reduced by 45 (54%)
84
39
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Creationcare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
creationcare.org
253 ms
webfont.js
9 ms
165 ms
css
198 ms
178 ms
196 ms
style.css
177 ms
gprofiles.js
178 ms
wpgroho.js
174 ms
173 ms
form.js
173 ms
style.css
172 ms
192 ms
w.js
145 ms
sum6cpe.js
295 ms
merriweather.css
16 ms
een-combo-4_web.jpg
157 ms
ad516503a11cd5ca435acc9bb6523536
149 ms
button-back.gif
26 ms
YQixcBt4h8DmZwK9P1bhEQ.woff
126 ms
ygC2Fp8ylofzQwABjiUjiA.woff
140 ms
EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff
194 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
193 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
193 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
193 ms
y7lebkjgREBJK96VQi37ZtIh4imgI8P11RFo6YPCPC0.woff
194 ms
dazS1PrQQuCxC3iOAJFEJbsuoFAk0leveMLeqYtnfAY.woff
193 ms
Genericons.svg
22 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
22 ms
d
181 ms
sdk.js
180 ms
fontawesome-webfont.woff
33 ms
nf2CevwDoKSdL
31 ms
master.html
20 ms
jquery.js
99 ms
Noticons.svg
98 ms
BaABdRAi2AAAA
96 ms
merriweather-bold-webfont.ttf
98 ms
merriweather-regular-webfont.ttf
98 ms
merriweather-light-webfont.ttf
98 ms
hovercard.css
65 ms
services.css
67 ms
graph.facebook.com
107 ms
g.gif
100 ms
g.gif
27 ms
g.gif
28 ms
g.gif
28 ms
p.gif
148 ms
138 ms
postmessage.js
7 ms
jed.js
6 ms
underscore.min.js
7 ms
xd_arbiter.php
131 ms
xd_arbiter.php
245 ms
jquery.wpcom-proxy-request.js
5 ms
31 ms
18 ms
likes-rest.js
22 ms
batch
52 ms
2 ms
e1af68fb69ef4351258b3a22924dd7da
145 ms
4f7a4a53e9f7b28439bdf0ced1347667
155 ms
62589da834866f35cb7ce3aa73857bbc
146 ms
noticons.css
10 ms
style.css
8 ms
e171689648858a1b2a25aa64909c3783
166 ms
b584a95222299d532e131f73aaa02098
194 ms
acdbc1173582111ae951bfb18b1a3afb
179 ms
d106b93f61784be3ee558c46ada276f9
221 ms
1124403b336bbb8beb8ebafc9449549e
252 ms
page.php
492 ms
Noticons.svg
3 ms
LUdypCgtRlc.css
173 ms
46icGyCHNkx.css
206 ms
7UFpPvIym7D.css
247 ms
q68gy-v_YMF.js
351 ms
YvxwM8R7ol8.js
387 ms
ihptErjAmMX.js
318 ms
3So47A9WcrL.js
285 ms
cUsKAwzqrQw.js
442 ms
11224281_1036802296351929_5354949348032813986_n.jpg
310 ms
safe_image.php
300 ms
safe_image.php
334 ms
safe_image.php
367 ms
safe_image.php
369 ms
12011198_1036802583018567_2478065365808725062_n.jpg
295 ms
10168085_1428722110717804_8874026807751587857_n.jpg
328 ms
66582_503722526474256_903073678226450306_n.jpg
364 ms
11179975_10152908873096634_5653824405067091477_n.jpg
364 ms
264625_10150239616795843_4988495_n.jpg
374 ms
12794574_10208613600919411_1258593335236195109_n.jpg
375 ms
312316_560708040624301_695757188_n.jpg
433 ms
wL6VQj7Ab77.png
55 ms
s7jcwEQH7Sx.png
58 ms
GtIpNnEyqq_.png
57 ms
lRyN50VcaFW.js
44 ms
R9a_DtVRZgv.js
41 ms
cUDgRFxaoIk.js
57 ms
0JBr1QHp8Gi.js
39 ms
kDOzhTr2W91.js
40 ms
creationcare.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.
creationcare.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
Missing source maps for large first-party JavaScript
creationcare.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 Creationcare.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 Creationcare.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.
creationcare.org
Open Graph description is not detected on the main page of Creationcare. 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: