Tools & Wizards About Us
wecharity.org screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

wecharity.org

WE Charity Foundation (WCF) | Ensuring Sustainable Impact for Future Generations

Page Load Speed

7.9 sec in total

First Response

61 ms

Resources Loaded

7.8 sec

Page Rendered

60 ms

wecharity.org screenshot

About Website

Welcome to wecharity.org homepage info - get ready to check WE Charity best content for Canada right away, or after learning these important things about wecharity.org

WE Charity Foundation (WCF) will continue the work begun by WE Charity Canada. WCF will ensure support and security of critical flagship projects in Kenya.

Visit wecharity.org

Key Findings

We analyzed Wecharity.org page load time and found that the first response time was 61 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wecharity.org performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

www.wecharity.org

61 ms

minified.js

24 ms

focus-within-polyfill.js

22 ms

polyfill.min.js

7304 ms

bootstrap-features.dbbc2053.bundle.min.js

61 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Wecharity.org, 44% (12 requests) were made to Static.parastorage.com and 44% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.9 kB (66%)

Content Size

456.3 kB

After Optimization

154.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wecharity.org main page is 456.3 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. 35% of websites need less resources to load. HTML takes 379.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 294.2 kB

  • Original 379.6 kB
  • After minification 377.9 kB
  • After compression 85.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 294.2 kB or 78% of the original size.

Image Optimization

-23%

Potential reduce by 7.7 kB

  • Original 33.0 kB
  • After minification 25.4 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. Obviously, WE Charity needs image optimization as it can save up to 7.7 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 48 B

  • Original 43.7 kB
  • After minification 43.7 kB
  • After compression 43.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 9 (39%)

Requests Now

23

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WE Charity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.wecharity.org

www.wecharity.org

61 ms

minified.js

minified.js

24 ms

focus-within-polyfill.js

focus-within-polyfill.js

22 ms

polyfill.min.js

polyfill.min.js

7304 ms

bootstrap-features.dbbc2053.bundle.min.js

bootstrap-features.dbbc2053.bundle.min.js

61 ms

main.c5638ec5.bundle.min.js

main.c5638ec5.bundle.min.js

61 ms

lodash.min.js

lodash.min.js

60 ms

react.production.min.js

react.production.min.js

62 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

60 ms

wix-perf-measure.bundle.min.js

wix-perf-measure.bundle.min.js

60 ms

react-dom.production.min.js

react-dom.production.min.js

61 ms

WCF-10.png

WCF-10.png

146 ms

e348d4_0fccc924bfa646558c705f74568c42fd~mv2.jpg

e348d4_0fccc924bfa646558c705f74568c42fd~mv2.jpg

219 ms

e348d4_f1b9a528a6d045dd97ba23b27986bdf7~mv2.jpg

e348d4_f1b9a528a6d045dd97ba23b27986bdf7~mv2.jpg

231 ms

e348d4_d3594d7c15484620b84378149aa08a94~mv2.png

e348d4_d3594d7c15484620b84378149aa08a94~mv2.png

244 ms

WCEF_LOGO-10.png

WCEF_LOGO-10.png

217 ms

e348d4_d00e2ac2a2e54bd1a3ca97e92a40d34e~mv2.jpg

e348d4_d00e2ac2a2e54bd1a3ca97e92a40d34e~mv2.jpg

231 ms

WCEF_LOGO-09.png

WCEF_LOGO-09.png

274 ms

WCF-10.png

WCF-10.png

296 ms

e348d4_f93940eefc6f48fa89fb7867375d39fa~mv2.jpeg

e348d4_f93940eefc6f48fa89fb7867375d39fa~mv2.jpeg

235 ms

file.woff

file.woff

180 ms

file.woff

file.woff

98 ms

file.woff

file.woff

104 ms

deprecation-en.v5.html

deprecation-en.v5.html

3 ms

bolt-performance

bolt-performance

18 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

7 ms

Accessibility Review

wecharity.org accessibility score

95

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

wecharity.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wecharity.org SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wecharity.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 Wecharity.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.

Social Sharing Optimization

wecharity.org

Open Graph data is detected on the main page of WE Charity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: