4.8 sec in total
48 ms
4.5 sec
200 ms
Click here to check amazing United Way Worldwide Fundly content for Pakistan. Otherwise, check out these important facts you probably never knew about unitedwayworldwide.fundly.com
Visit unitedwayworldwide.fundly.comWe analyzed Unitedwayworldwide.fundly.com page load time and found that the first response time was 48 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
unitedwayworldwide.fundly.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value12.1 s
0/100
25%
Value6.8 s
35/100
10%
Value590 ms
51/100
30%
Value0.01
100/100
15%
Value11.7 s
17/100
10%
48 ms
649 ms
322 ms
173 ms
166 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 6% of them (7 requests) were addressed to the original Unitedwayworldwide.fundly.com, 7% (8 requests) were made to Doapv6pcsx1wa.cloudfront.net and 7% (8 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Connect.facebook.net.
Page size can be reduced by 2.4 MB (71%)
3.3 MB
963.1 kB
In fact, the total size of Unitedwayworldwide.fundly.com main page is 3.3 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. 65% of websites need less resources to load. CSS take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 97.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 97.4 kB or 77% of the original size.
Potential reduce by 1.9 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. United Way Worldwide Fundly images are well optimized though.
Potential reduce by 397.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 397.5 kB or 61% of the original size.
Potential reduce by 1.9 MB
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. Unitedwayworldwide.fundly.com needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 80% of the original size.
Number of requests can be reduced by 59 (69%)
85
26
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of United Way Worldwide Fundly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
unitedwayworldwide.fundly.com
48 ms
unitedwayworldwide.fundly.com
649 ms
3536001.js
322 ms
application-0dbfec75b6b6ae584ed5d042e377fcf5.css
173 ms
jquery.min.js
166 ms
modernizr-2.5.2-62246608536cb26ae9202f3aa79d6d83.js
130 ms
google_analytics-9df1a932a974dc6f18aa1f09d8d7f8a9.js
129 ms
metrics-c355c055982531a53a966c5162fc6b2b.js
129 ms
cause-d4319ce5522232955327e4b12db95267.css
142 ms
cwp
91 ms
cause_page-8570c65a8ce984ba785dd545e0262963.js
142 ms
base_js_all-85938a5d248a2fc88d6ce7eda33154d0.js
140 ms
gtm.js
175 ms
webfont.js
15 ms
left.png
10 ms
right.png
39 ms
icon_search.png
106 ms
fundly_logo_knockout.png
130 ms
css
175 ms
rmi4ipp.js
564 ms
fontawesome-webfont-c3505b2ba2be317c06bb81329741ee60.woff
93 ms
conversion_async.js
365 ms
roundtrip.js
1134 ms
ec3e0d489cf27cfda68e0301fbd4b338_ar_h233.jpg
364 ms
137b240e161899709605ec99396b6489.png
364 ms
a5656dac17770816c6d6ca6daea33733.jpg
1005 ms
a4b2ed277d8a9fbe1d44fa456f425ea9.jpg
1004 ms
a3b738941aa4896ac7b49a754f59b775.jpg
1076 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
1045 ms
all.js
1415 ms
mixpanel-2.2.min.js
1030 ms
ga.js
1029 ms
fbds.js
1536 ms
OWCuIriso0IYBasiGT3pFw.js
924 ms
widgets.js
988 ms
in.js
978 ms
plusone.js
986 ms
PinExt.png
869 ms
pinit.js
954 ms
961 ms
a
1274 ms
p.gif
816 ms
p.gif
521 ms
feedback-tab.png
91 ms
tab-right-dark-da2413549ce324fc421ae86a0e5881ee.png
75 ms
255 ms
secureAnonymousFramework
127 ms
cb=gapi.loaded_0
142 ms
cb=gapi.loaded_1
197 ms
fastbutton
368 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
124 ms
318 ms
345 ms
__utm.gif
140 ms
PTFH5P6GWBCDRFRBOLVWV6.js
335 ms
__utm.gif
208 ms
__utm.gif
208 ms
pinit_main.js
118 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
116 ms
postmessageRelay
358 ms
collect
347 ms
count.json
563 ms
642 ms
cb=gapi.loaded_0
196 ms
cb=gapi.loaded_1
94 ms
xd_arbiter.php
729 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
445 ms
585 ms
AIAAgQCCAIMAhACFAIYAhwCIAIkAigCLAIwAjQCOAI8AkACRAJIAkwCUAJUAlgCXAJgAmQCaAJsAnACdAJ4AnwCgAKEAogCjAKQApQCmAKcAqACpAKoAqwCsAK0ArgCvALAAsQCyALMAtAC1ALYAtwC4ALkAugC7ALwAvQC+AL8AAA==
24 ms
AIAAgQCCAIMAhACFAIYAhwCIAIkAigCLAIwAjQCOAI8AkACRAJIAkwCUAJUAlgCXAJgAmQCaAJsAnACdAJ4AnwCgAKEAogCjAKQApQCmAKcAqACpAKoAqwCsAK0ArgCvALAAsQCyALMAtAC1ALYAtwC4ALkAugC7ALwAvQC+AL8AAA==
24 ms
AEAAQQBCAEMARABFAEYARwBIAEkASgBLAEwATQBOAE8AUABRAFIAUwBUAFUAVgBXAFgAWQBaAFsAXABdAF4AXwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAGEAYgBjAGQAZQBmAGcAaABpAGoAawBsAG0AbgBvAHAAcQByAHMAdAB1AHYAdwB4AHkAegB7AHwAfQB+AH8AgACBAIIAgwCEAIUAhgCHAIgAiQCKAIsAjACNAI4AjwCQAJEAkgCTAJQAlQCWAJcAmACZAJoAmwCcAJ0AngCfAKAAoQCiAKMApAClAKYApwCoAKkAqgCrAKwArQCuAK8AsACxALIAswC0ALUAtgC3ALgAuQC6ALsAvAC9AL4AvwAA
22 ms
AAA=
21 ms
AIAAgQCCAIMAhACFAIYAhwCIAIkAigCLAIwAjQCOAI8AkACRAJIAkwCUAJUAlgCXAJgAmQCaAJsAnACdAJ4AnwCgAKEAogCjAKQApQCmAKcAqACpAKoAqwCsAK0ArgCvALAAsQCyALMAtAC1ALYAtwC4ALkAugC7ALwAvQC+AL8AAA==
21 ms
AAA=
19 ms
fbevents.hashing.js
399 ms
out
113 ms
398 ms
out
401 ms
out
428 ms
out
428 ms
out
427 ms
out
426 ms
out
427 ms
3193398744-postmessagerelay.js
424 ms
rpc:shindig_random.js
340 ms
ga-audiences
333 ms
jot
251 ms
127 ms
u.php
210 ms
143 ms
sync
140 ms
adsct
199 ms
pixel
134 ms
cb=gapi.loaded_0
22 ms
tap.php
69 ms
377928.gif
36 ms
sd
32 ms
in
46 ms
track.js
182 ms
nr-100.js
99 ms
23 ms
like.php
97 ms
like.php
74 ms
xd_arbiter.php
139 ms
xd_arbiter.php
290 ms
bc27c73051
141 ms
qeKvIRsJabD.js
494 ms
LVx-xkvaJ0b.png
557 ms
unitedwayworldwide.fundly.com 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
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
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.
unitedwayworldwide.fundly.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
unitedwayworldwide.fundly.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unitedwayworldwide.fundly.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 Unitedwayworldwide.fundly.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.
unitedwayworldwide.fundly.com
Open Graph description is not detected on the main page of United Way Worldwide Fundly. 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: