3.2 sec in total
19 ms
3 sec
173 ms
Welcome to wcan.org homepage info - get ready to check WCAN best content right away, or after learning these important things about wcan.org
Visit wcan.orgWe analyzed Wcan.org page load time and found that the first response time was 19 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wcan.org performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value10.9 s
0/100
25%
Value8.3 s
19/100
10%
Value1,600 ms
12/100
30%
Value0.002
100/100
15%
Value15.0 s
8/100
10%
19 ms
528 ms
80 ms
88 ms
97 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wcan.org, 82% (75 requests) were made to Collegesuccessfoundation.org and 4% (4 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (528 ms) relates to the external source Collegesuccessfoundation.org.
Page size can be reduced by 141.1 kB (16%)
868.4 kB
727.3 kB
In fact, the total size of Wcan.org main page is 868.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. 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 532.7 kB which makes up the majority of the site volume.
Potential reduce by 134.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 134.8 kB or 79% 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. WCAN images are well optimized though.
Potential reduce by 125 B
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.
Number of requests can be reduced by 64 (80%)
80
16
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WCAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
wcan.org
19 ms
528 ms
style.min.css
80 ms
give.css
88 ms
give-donation-summary.css
97 ms
give-fee-recovery-frontend.min.css
103 ms
give-ffm-frontend.css
103 ms
give-ffm-datepicker.css
112 ms
give-currency-switcher-frontend.min.css
122 ms
give-recurring.min.css
129 ms
bootstrap.min.css
34 ms
swiper-bundle.min.css
129 ms
fontawesome.min.css
139 ms
myfonts.css
138 ms
style.min.css
151 ms
addtoany.min.css
151 ms
jquery.min.js
42 ms
core.min.js
163 ms
datepicker.min.js
165 ms
mouse.min.js
170 ms
slider.min.js
172 ms
clipboard.min.js
199 ms
moxie.min.js
201 ms
plupload.min.js
201 ms
underscore.min.js
210 ms
wp-polyfill-inert.min.js
213 ms
regenerator-runtime.min.js
215 ms
wp-polyfill.min.js
234 ms
dom-ready.min.js
228 ms
hooks.min.js
229 ms
i18n.min.js
247 ms
a11y.min.js
248 ms
handlers.min.js
249 ms
give-ffm-frontend.js
273 ms
page.js
43 ms
addtoany.min.js
304 ms
51 ms
give-stripe.js
270 ms
give-stripe-sepa.js
269 ms
give.js
335 ms
link-initialize.js
68 ms
popper.min.js
14 ms
bootstrap.bundle.min.js
18 ms
formreset.min.css
267 ms
formsmain.min.css
246 ms
readyclass.min.css
223 ms
browsers.min.css
221 ms
give-fee-recovery-public.min.js
218 ms
give-stripe-payment-request.js
215 ms
give-recurring.min.js
243 ms
give-stripe-ach.js
267 ms
give-donation-summary.js
256 ms
give-salesforce.js
269 ms
give-currency-switcher-frontend.min.js
269 ms
swiper-bundle.min.js
303 ms
jquery.magnific-popup.min.js
290 ms
functions.min.js
279 ms
jquery.json.min.js
279 ms
gravityforms.min.js
279 ms
conditional_logic.min.js
276 ms
utils.min.js
271 ms
vendor-theme.min.js
270 ms
scripts-theme.min.js
240 ms
eso.KJQApO2n.js
16 ms
gtm.js
153 ms
gximage2
142 ms
logo-white.png
140 ms
logo.png
140 ms
WCAN-banner-about-us.png
195 ms
WCAN-Regional-Coverage-Areas-2023-1024x768.png
196 ms
Cennady-Coleman-Headshot.png
197 ms
Amber-Goodrich-Headshot.png
247 ms
Raul-Sanchez_Headshot.png
196 ms
Melissa_Pico_Headshot.png
200 ms
CSF_leadership_keith-stier-van-essen-300x300.jpg
143 ms
logo-footer.png
137 ms
ac_state_logo_wa_stack_white-501px.png
136 ms
32ED32_A_0.woff
156 ms
32ED32_C_0.woff
158 ms
32ED32_E_0.woff
160 ms
32ED32_6_0.woff
159 ms
32ED32_4_0.woff
207 ms
fa-solid-900.woff
159 ms
fa-regular-400.woff
234 ms
fa-light-300.woff
361 ms
fa-brands-400.woff
204 ms
sm.25.html
41 ms
icons.37.svg.js
73 ms
js
47 ms
analytics.js
161 ms
collect
14 ms
wcan.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
wcan.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wcan.org SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wcan.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 Wcan.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.
wcan.org
Open Graph description is not detected on the main page of WCAN. 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: