2.1 sec in total
190 ms
1.4 sec
421 ms
Visit givingwhatwecan.org now to see the best up-to-date Giving What We Can content for Australia and also check out these interesting facts you probably never knew about givingwhatwecan.org
100x your impact by finding and donating to the best charities. Learn about high-impact philanthropy, join an effective giving community, take a giving pledge.
Visit givingwhatwecan.orgWe analyzed Givingwhatwecan.org page load time and found that the first response time was 190 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
givingwhatwecan.org performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value7.2 s
5/100
25%
Value5.6 s
53/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value12.3 s
15/100
10%
190 ms
268 ms
175 ms
222 ms
142 ms
Our browser made a total of 21 requests to load all elements on the main page. We found that 24% of them (5 requests) were addressed to the original Givingwhatwecan.org, 38% (8 requests) were made to Images.contentful.com and 19% (4 requests) were made to Netlify.scdn4.secure.raxcdn.com. The less responsive or slowest element that took the longest time to load (588 ms) relates to the external source Netlify.scdn4.secure.raxcdn.com.
Page size can be reduced by 276.2 kB (56%)
491.4 kB
215.2 kB
In fact, the total size of Givingwhatwecan.org main page is 491.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 403.9 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.4 kB or 74% of the original size.
Potential reduce by 1.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. Giving What We Can images are well optimized though.
Potential reduce by 249.5 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 249.5 kB or 62% of the original size.
Number of requests can be reduced by 7 (39%)
18
11
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Giving What We Can. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
givingwhatwecan.org
190 ms
www.givingwhatwecan.org
268 ms
app.min.css
175 ms
lab.min.js
222 ms
IMG_2326.JPG
142 ms
gwwc-logo-transparent-nav.png
19 ms
12045476_10153607315397973_3914635633628886437_o.jpg
121 ms
IMG_1609.JPG
120 ms
logo_foundation_large.png
211 ms
SCI_Logo.png
124 ms
Deworm-The-World-Initiative-Logo.png
123 ms
PHC_Logo.png
129 ms
shutterstock_255204166.jpg
266 ms
jquery.min.js
133 ms
3479250027.js
390 ms
webfont.js
148 ms
app.min.js
87 ms
analytics.min.js
250 ms
calculator.min.js
101 ms
content-blocks.min.js
104 ms
icons.woff
588 ms
givingwhatwecan.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
givingwhatwecan.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
Page has valid source maps
givingwhatwecan.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Givingwhatwecan.org 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 Givingwhatwecan.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.
givingwhatwecan.org
Open Graph data is detected on the main page of Giving What We Can. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: