2.9 sec in total
448 ms
2.2 sec
290 ms
Welcome to fundraise.com homepage info - get ready to check Fundraise best content for United States right away, or after learning these important things about fundraise.com
Fundraise.com: The best free online fundraising platform. Start a successful crowdfunding campaign on the site with over $100,000,000 raised.
Visit fundraise.comWe analyzed Fundraise.com page load time and found that the first response time was 448 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fundraise.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value7.9 s
3/100
25%
Value5.8 s
50/100
10%
Value2,140 ms
6/100
30%
Value0.004
100/100
15%
Value16.6 s
5/100
10%
448 ms
575 ms
113 ms
97 ms
97 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fundraise.com, 35% (27 requests) were made to D1iyr2k6cjfoq0.cloudfront.net and 23% (18 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Cdn.optimizely.com.
Page size can be reduced by 850.1 kB (35%)
2.4 MB
1.6 MB
In fact, the total size of Fundraise.com main page is 2.4 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 53.7 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 53.7 kB or 80% of the original size.
Potential reduce by 64.5 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. Fundraise images are well optimized though.
Potential reduce by 448.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 448.3 kB or 64% of the original size.
Potential reduce by 283.6 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. Fundraise.com needs all CSS files to be minified and compressed as it can save up to 283.6 kB or 73% of the original size.
Number of requests can be reduced by 24 (36%)
66
42
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fundraise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.fundraise.com
448 ms
108039789.js
575 ms
application-894006d1a6f4b2478827f7bdaa290556.css
113 ms
exterior-234cc3ce42f15ef5770852d292c087be.css
97 ms
magnific-popup-b7afe1e0b46c040192e442e723492ce7.css
97 ms
widgets.js
196 ms
application-37068736fcff92ab003f498b718ac13a.js
110 ms
jquery.magnific-popup-b78291ac1a694a8be8be93b23d201c6f.js
99 ms
home_donation_activity-5d09022d90ca48fb65e8b25fc87169e6.js
95 ms
home-dd71570f7189f9610cd8683745181bd3.js
102 ms
all.js
546 ms
logo-05645ae8136763a40ef0bc6f527a5c9e.png
13 ms
scott-and-mike.jpg
179 ms
grain-e79a82f7ea28ae9ebcc38add7a789093.jpg
44 ms
banner1-26efaa9b0391575d608ee8aa253a0702.jpg
174 ms
banner2-9b545dae2c3a25667956d7193c099cbc.jpg
152 ms
banner3-34c3e5c7ae5826ce6703cd1605d30168.png
253 ms
puzzle-7e9c8cd6cc1f120f4622d14d2b2bd3d4.png
43 ms
checkin-b438e3568472d5202a3db011e527eb60.png
42 ms
earth-acc19f3fd26c21000a2d1b0251dd9acb.png
169 ms
whosusing-3dcdb0608b73dc90eebb4ff8c3783193.png
172 ms
bca-cecb44c6f80d45811cd78e8f3a24641c.jpg
169 ms
fobh-b2c704b23620bbca174c523c82aefde7.jpg
174 ms
fitzgerald-36be2309a8f0b2f1c1d51c30ad5456e6.png
191 ms
mslf-1a82a78ebb6d31d625e9f90e83c7439b.jpg
176 ms
cn-2013-jas.jpg
223 ms
image.jpeg
222 ms
img-6407-frank-demiero-headshot-7-28-13-300x240.jpg
266 ms
zane1.jpg
222 ms
jlcleftface.jpg
249 ms
367099-orig.jpg
219 ms
run2.jpg
249 ms
misty.jpg
274 ms
6-postcards.jpg
247 ms
12-14-wise-street.jpeg
248 ms
jason-rathje-marathon-pic.jpg
296 ms
salesky1.jpg
277 ms
laosed.jpg
275 ms
give.jpg
267 ms
2015-04-07-17-01-33.jpg
314 ms
deliver-1.jpg
310 ms
giraffe.jpg
297 ms
logo_white-8f1862d15007d9f81a5cf8e98b697d38.png
137 ms
ProximaNova-Reg-webfont-296582772c2ebf32413f334881649841.woff
149 ms
ProximaNova-Bold-webfont-9bb189e7b8fbf9d68271548bd3560fb9.woff
148 ms
ProximaNova-Xbold-webfont-6c39d55b5bf1281781fc1c13108282c6.woff
149 ms
CXprdjeD3aUjTx0MvEQ7AfigcgoPmlwXF+gVgbWwj
67 ms
TisaWebPro-Italic-988759e21fc437af644de94343d41b5c.woff
111 ms
TisaWebPro-13f1d0c6ad8c1b2b1468fc97a678456b.woff
112 ms
TisaWebPro-Bold-0dfe85b48a743b633bbbd92e36f6f42e.woff
112 ms
ga.js
157 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
94 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
47 ms
__utm.gif
21 ms
info.json
84 ms
jot
95 ms
121 ms
xd_arbiter.php
434 ms
tracker.js
51 ms
nr-100.js
57 ms
roundtrip.js
60 ms
like.php
88 ms
xd_arbiter.php
341 ms
f6d04dc7f6
115 ms
W6VDDNUIZJHTFMBTLP5WMW.js
146 ms
vpc6VNjRPXV.js
64 ms
LVx-xkvaJ0b.png
62 ms
out
6 ms
out
8 ms
out
35 ms
sync
82 ms
adsct
146 ms
pv
84 ms
65 ms
377928.gif
14 ms
sd
13 ms
pixel
23 ms
in
4 ms
fundraise.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 input fields do not have accessible names
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
fundraise.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
Browser errors were logged to the console
fundraise.com SEO score
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 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 Fundraise.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 Fundraise.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.
fundraise.com
Open Graph description is not detected on the main page of Fundraise. 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: