6.7 sec in total
1.9 sec
4.4 sec
329 ms
Click here to check amazing ECEAE content for United States. Otherwise, check out these important facts you probably never knew about eceae.org
Visit eceae.orgWe analyzed Eceae.org page load time and found that the first response time was 1.9 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eceae.org performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.9 s
98/100
25%
Value2.3 s
98/100
10%
Value0 ms
100/100
30%
Value0.155
74/100
15%
Value1.4 s
100/100
10%
1930 ms
272 ms
1105 ms
166 ms
1154 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 75% of them (39 requests) were addressed to the original Eceae.org, 15% (8 requests) were made to Google-analytics.com and 4% (2 requests) were made to F.fontdeck.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Eceae.org.
Page size can be reduced by 381.4 kB (20%)
1.9 MB
1.5 MB
In fact, the total size of Eceae.org main page is 1.9 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 28.3 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 5.9 kB, which is 13% 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 28.3 kB or 64% of the original size.
Potential reduce by 107.0 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. ECEAE images are well optimized though.
Potential reduce by 216.4 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 216.4 kB or 62% of the original size.
Potential reduce by 29.7 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. Eceae.org needs all CSS files to be minified and compressed as it can save up to 29.7 kB or 84% of the original size.
Number of requests can be reduced by 26 (52%)
50
24
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECEAE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
eceae.org
1930 ms
screen.css
272 ms
css3.css
1105 ms
2324.css
166 ms
site-search-submit.gif
1154 ms
Clean-Up-Cruelty.jpg
1740 ms
Cosmetics.jpg
1571 ms
HOME_PAGE_MAIN.png
1596 ms
h3-welcome.png
398 ms
h3-latest-news.png
500 ms
beagle-puppy.jpg
618 ms
drugs.png
993 ms
ECEAE-news-ratsx2.jpg
1097 ms
ECEAE-CuteAnimals-mouse2.JPG
1199 ms
take-action.jpg
1384 ms
Donate.jpg
1389 ms
Shopcrueltyfree.jpg
1306 ms
icon-our-campaigns.png
1432 ms
jquery.tools.min.js
11 ms
icon-save-primates.png
1422 ms
icon-national-group.png
1425 ms
donate-now-large.png
1460 ms
jquery.tools.min.js
1518 ms
stylesheetToggle.js
1521 ms
jquery.countdown.min.js
1570 ms
global.js
1584 ms
javascript.gp
179 ms
cookieControl-5.1.min.js
1613 ms
2324.css
108 ms
page-bg.jpg
996 ms
language-select.gif
603 ms
logo.png
677 ms
site-search-bg.gif
676 ms
news-item-bg.png
717 ms
cta-b.png
705 ms
cta-h.png
707 ms
blue-action-btn.png
798 ms
general-buttons-bg.png
769 ms
rss.gif
822 ms
text-size.gif
824 ms
ga.js
27 ms
jquery.min.js
44 ms
__utm.gif
76 ms
ga.js
30 ms
ga.js
40 ms
ga.js
44 ms
__utm.gif
14 ms
__utm.gif
23 ms
__utm.gif
25 ms
text-size-normal.css
186 ms
text-size-large.css
145 ms
text-size-extra-large.css
97 ms
eceae.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
eceae.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
eceae.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eceae.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 Eceae.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.
eceae.org
Open Graph description is not detected on the main page of ECEAE. 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: