1.6 sec in total
21 ms
1.2 sec
341 ms
Click here to check amazing Causes content for India. Otherwise, check out these important facts you probably never knew about causes.com
Causes.com is the easiest way to take action on issues you care about. Contact lawmakers and leaders with one-click voting, learn about bills, keep track of important issues, and rally your friends ar...
Visit causes.comWe analyzed Causes.com page load time and found that the first response time was 21 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
causes.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value9.6 s
0/100
25%
Value22.6 s
0/100
10%
Value13,590 ms
0/100
30%
Value0
100/100
15%
Value45.4 s
0/100
10%
21 ms
94 ms
10 ms
26 ms
97 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 32% of them (21 requests) were addressed to the original Causes.com, 14% (9 requests) were made to Use.edgefonts.net and 6% (4 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (295 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 373.2 kB (33%)
1.1 MB
770.3 kB
In fact, the total size of Causes.com main page is 1.1 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 591.4 kB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.3 kB or 67% of the original size.
Potential reduce by 6.2 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. Causes images are well optimized though.
Potential reduce by 328.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 328.3 kB or 66% of the original size.
Potential reduce by 19.4 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. Causes.com needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 75% of the original size.
Number of requests can be reduced by 30 (60%)
50
20
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Causes. 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 4 to 1 for CSS and as a result speed up the page load time.
causes.com
21 ms
www.causes.com
94 ms
application-f069f881581b3f84abaec49453ebc096.css
10 ms
static_pages-3e25245c7b96fc432983a1b81ce258e0.css
26 ms
ga.js
97 ms
analytics.js
45 ms
jquery.min.js
124 ms
1013001.js
261 ms
open-sans:n3,i3,n4,i4,n6:all;bitter:n4,i4:all.js
226 ms
100-50-4-26fcdeb61176fd7c4a89f2c36b3b85cf.png
33 ms
brigade-logo-ed4c3b9b1d48287d73886a707f2dc617.svg
30 ms
full-5906370d579d4e53003068c542f2bb35.svg
94 ms
stickers@2x-acd0f18c79ccc72270b08b2d7447ace2.jpg
94 ms
support@2x-879cebb227821140fd7fa78f9c5e0d6a.jpg
97 ms
campaign@2x-9cae67e4ccf1c4b2c6ed618b4685e0f5.jpg
36 ms
malaria@2x-12258ff717ef4b687b027ed6e75e89a9.jpg
33 ms
ricky@2x-990beddcf39202ff2e9f40b0660ddd02.jpg
92 ms
trevor@2x-afbb033889ad4052fc20c20214f5aff7.jpg
92 ms
begley@2x-476fee409f6bf9f9f23ed2a9856a0369.jpg
93 ms
gabby@2x-00f11c2643c999cc7fc1f474c34031ad.jpg
96 ms
sierra@2x-289454a9e301c86f7e405c767379673f.jpg
96 ms
wwf@2x-0a6a0993ead3a33c21d4315808590a7a.jpg
97 ms
toms@2x-2885cc2b0b86067a1553d246a46f4c5c.jpg
97 ms
application-2a6437085623fb5dde30dda67000aa81.js
98 ms
collect
40 ms
causes-f56042f1db05ea1e7a4c65ea2d5240c2.ttf
22 ms
__utm.gif
17 ms
jquery.min.js
17 ms
application-2a6437085623fb5dde30dda67000aa81.js
7 ms
__utm.gif
9 ms
1013001.js
110 ms
www.causes.com
30 ms
oSor1vVkbxnJdM3bZehuyzwSQNmyYSLdnvtJEL-K0cMffOktggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i26e.woff
82 ms
8lg95k2oTR3CMSTPE8FTIk3Hv0HkSdohE2j77mHmcSbffO0tggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i26I.woff
141 ms
x1Ob4VJJBBoAV4d7qCbE0EbaCDfzl7Nr0oUP3SVjCpSffOctggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i262.woff
191 ms
9A44bMac7SfPlubWGbYW_5xPAw2J1eKsi8LxOioPjcvffw2eggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i265.woff
136 ms
fJ-OIQPtfG1wiKM9W7odBz-6cMNIqwfWW-1KRBCWX2GffOxeggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i26I.woff
167 ms
ZeswiHq4zZyrBiOY1GBXq_JGWvGZI6LPSrg62eXv6uvffOKtggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i265.woff
165 ms
yBcwlyJHfx02g8I1xnhi8fVIM24I6fd7RSTBYoF9hjbffO7tggMdeMJ6Mk6gwyBuSh90ZAs1ZAZzd1sDOco8i26F.woff
167 ms
all.js
249 ms
p.gif
137 ms
52 ms
xd_arbiter.php
295 ms
iframe_api
52 ms
roundtrip.js
64 ms
xd_arbiter.php
273 ms
www-widgetapi.js
25 ms
Ll73lyqfIoY
54 ms
PX3Q6T5ZP5AX5GEGPWD5BR.js
21 ms
out
10 ms
out
52 ms
out
51 ms
www-embed-player-vflZsBgOl.css
21 ms
www-embed-player.js
47 ms
base.js
101 ms
adsct
208 ms
156 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
38 ms
ad_status.js
46 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
43 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
43 ms
sync
24 ms
sd
19 ms
377928.gif
14 ms
pixel
36 ms
in
3 ms
causes.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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.
causes.com 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
Missing source maps for large first-party JavaScript
causes.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Causes.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Causes.com 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.
causes.com
Open Graph data is detected on the main page of Causes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: