5.5 sec in total
107 ms
4.5 sec
801 ms
Click here to check amazing Donor Com Munity content for United States. Otherwise, check out these important facts you probably never knew about donorcommunity.com
ExceedFurther, Arreva’s online donor and fundraising software, helps nonprofits transform fundraising and cultivate relationships with donors and constituents.
Visit donorcommunity.comWe analyzed Donorcommunity.com page load time and found that the first response time was 107 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
donorcommunity.com performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value24.3 s
0/100
25%
Value22.3 s
0/100
10%
Value28,690 ms
0/100
30%
Value0.283
43/100
15%
Value47.4 s
0/100
10%
107 ms
356 ms
38 ms
103 ms
176 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Donorcommunity.com, 72% (84 requests) were made to Arreva.com and 8% (9 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (570 ms) relates to the external source Arreva.com.
Page size can be reduced by 917.0 kB (30%)
3.1 MB
2.2 MB
In fact, the total size of Donorcommunity.com main page is 3.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. 85% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 117.2 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 117.2 kB or 82% of the original size.
Potential reduce by 209.8 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. Donor Com Munity images are well optimized though.
Potential reduce by 264.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 264.4 kB or 64% of the original size.
Potential reduce by 325.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. Donorcommunity.com needs all CSS files to be minified and compressed as it can save up to 325.7 kB or 61% of the original size.
Number of requests can be reduced by 61 (65%)
94
33
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Donor Com Munity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
donorcommunity.com
107 ms
www.arreva.com
356 ms
mentions.css
38 ms
main.css
103 ms
aui.css
176 ms
main.css
164 ms
combo
271 ms
js_loader_modules
261 ms
barebone.jsp
303 ms
js_bundle_config
264 ms
1799533.js
160 ms
main.css
261 ms
combo
266 ms
combo
261 ms
fa_all.js
570 ms
arreva.js
262 ms
jquery.fancybox.min.css
262 ms
jquery.fancybox.min.js
292 ms
style.css
263 ms
style.css
456 ms
prov.js
291 ms
style.css
294 ms
arreva_style.js
292 ms
lightslider.js
451 ms
lightslider.css
448 ms
element.js
433 ms
combo
544 ms
main.js
433 ms
analytics.js
276 ms
gtm.js
274 ms
fbevents.js
378 ms
layout_set_logo
232 ms
article
347 ms
spacer.png
231 ms
article
242 ms
article
421 ms
article
241 ms
0a467d3c-f56d-5149-6c70-9c5a867d09c0
345 ms
3896827c-0e2a-598b-fd1e-3248e83fdac3
344 ms
bf2f8bd0-ed90-c33a-33ce-4cbd9ba8f8b6
430 ms
aaa9439d-8258-817d-1718-7d2cbba19c81
430 ms
1327de47-cd0b-dff3-3562-d5cc8660d4d6
432 ms
fa2d0b43-1971-b3e1-ac10-c635f328e5a2
432 ms
48640f1e-1de5-c02e-4354-f8e467869656
486 ms
8fdc8260-a80f-98f4-ebc6-c898936a3a37
457 ms
d3886ed9-8774-d99f-80a2-efc06684f445
448 ms
25c347d0-5df3-e86f-02d0-983e1586fbeb
448 ms
39818a1d-ba3f-8e04-7f40-1aa29a0b79bd
447 ms
31a6413c-1a9e-7884-6d3a-cda32c508b58
446 ms
2f763ebb-7fc4-8380-0876-cfa181eabcb8
470 ms
a3f12415-14af-100c-a113-d44e0c86af59
470 ms
64d61ad4-926c-185a-552c-5dc875cb81ff
467 ms
article
460 ms
article
479 ms
1def966a-4e9c-a825-37f4-50535903a654
495 ms
collectedforms.js
417 ms
1799533.js
495 ms
1799533.js
466 ms
css
414 ms
css
418 ms
css
431 ms
css
444 ms
css
433 ms
css
449 ms
css
451 ms
icon
435 ms
css2
455 ms
collect
112 ms
1202055096631845
162 ms
rawline-400.woff
56 ms
rawline-500.woff
58 ms
rawline-300.woff
56 ms
rawline-200.woff
70 ms
rawline-100.woff
55 ms
rawline-600.woff
68 ms
rawline-700.woff
72 ms
rawline-800.woff
69 ms
rawline-900.woff
69 ms
rawline-500i.woff
69 ms
rawline-400i.woff
72 ms
rawline-300i.woff
69 ms
rawline-200i.woff
72 ms
rawline-100i.woff
120 ms
rawline-600i.woff
72 ms
rawline-700i.woff
121 ms
rawline-800i.woff
123 ms
rawline-900i.woff
123 ms
199 ms
56 ms
27 ms
icons.svg
28 ms
32 ms
28 ms
20 ms
dark70per.png
294 ms
available_languages.jsp
294 ms
297 ms
295 ms
Zp5JWbAnZ-s
312 ms
controls.png
178 ms
www-player.css
140 ms
www-embed-player.js
200 ms
base.js
271 ms
fetch-polyfill.js
265 ms
378 ms
237 ms
236 ms
42 ms
ad_status.js
258 ms
VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js
264 ms
embed.js
73 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
156 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
160 ms
91 ms
id
119 ms
Create
334 ms
donorcommunity.com 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
[aria-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
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.
donorcommunity.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
donorcommunity.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Donorcommunity.com 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 Donorcommunity.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.
donorcommunity.com
Open Graph description is not detected on the main page of Donor Com Munity. 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: