4.6 sec in total
37 ms
4.2 sec
372 ms
Visit fundly.com now to see the best up-to-date Fundly content for Pakistan and also check out these interesting facts you probably never knew about fundly.com
Raise money online with a free personal fundraiser. Individual crowdfunding for yourself, medical, funeral expenses, charity, schools, and businesses!
Visit fundly.comWe analyzed Fundly.com page load time and found that the first response time was 37 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fundly.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.7 s
33/100
25%
Value8.3 s
19/100
10%
Value380 ms
70/100
30%
Value0
100/100
15%
Value19.1 s
3/100
10%
37 ms
1131 ms
198 ms
96 ms
62 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Fundly.com, 12% (9 requests) were made to Fonts.gstatic.com and 11% (8 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fundly.com.
Page size can be reduced by 763.6 kB (44%)
1.7 MB
955.3 kB
In fact, the total size of Fundly.com main page is 1.7 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. Javascripts take 951.4 kB which makes up the majority of the site volume.
Potential reduce by 76.1 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 76.1 kB or 78% of the original size.
Potential reduce by 2.1 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. Fundly images are well optimized though.
Potential reduce by 597.8 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 597.8 kB or 63% of the original size.
Potential reduce by 87.5 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. Fundly.com needs all CSS files to be minified and compressed as it can save up to 87.5 kB or 82% of the original size.
Number of requests can be reduced by 28 (56%)
50
22
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 17 to 1 for JavaScripts and as a result speed up the page load time.
fundly.com
37 ms
fundly.com
1131 ms
3536001.js
198 ms
css
96 ms
api.js
62 ms
fundly-style-53a92c082f918347bf715ad1f65b80a3.css
67 ms
backend_analytics-d4613faac9cff770cc2e7babe1f5b2fb.js
64 ms
fbds.js
507 ms
gtm.js
247 ms
728_90_ad.jpg
143 ms
1192a0c3-844f-4117-b9f7-895e9252f1e7.jpg
255 ms
devices-optimized-60b3f7def1b7d2e47536b746aeadfd14.jpg
199 ms
recaptcha__en.js
212 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
135 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
176 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
235 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
291 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
292 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
289 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
290 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
288 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
289 ms
fontawesome-webfont-c3505b2ba2be317c06bb81329741ee60.woff
47 ms
fundly-icons.woff
289 ms
analytics.js
102 ms
conversion_async.js
131 ms
roundtrip.js
185 ms
collect
56 ms
collect
182 ms
118 ms
106 ms
ga-audiences
17 ms
32 ms
PTFH5P6GWBCDRFRBOLVWV6.js
199 ms
out
4 ms
tr
24 ms
22 ms
out
12 ms
out
16 ms
out
20 ms
out
20 ms
out
21 ms
u.php
62 ms
adsct
102 ms
sync
69 ms
23 ms
pixel
76 ms
sd
10 ms
377928.gif
10 ms
in
4 ms
tap.php
306 ms
sentinel_base-797f9e3bcc6eee1ed77caf2237a18774.js
22 ms
nr-100.js
397 ms
mixpanel-2.2.min.js
126 ms
all.js
423 ms
homepage-v3-b643dd628dcefa2351e0d2d836e38cbe.js
42 ms
OWCuIriso0IYBasiGT3pFw.js
86 ms
set_ga_client_id
107 ms
bc27c73051
480 ms
feedback-tab.png
46 ms
track.js
493 ms
d50b3363227806d5fea47ee1b5b2103b_ar_h275.jpg
47 ms
419 ms
419 ms
3729939d01949dd423810a083680f52c_ar_h275.jpg
282 ms
7747452a8686f19d0405c41ec878f210_ar_h275.png
415 ms
044fd3a47a31f2606080275edf070028_as_w100_h100.png
413 ms
83840c712bc8b7d20f155821610dd3aa_ar_h275.jpg
443 ms
0454d06bd9a7d0de753b132c31fc7596_ar_h275.jpg
451 ms
abe06aa9ce0c76d7101573a2b20afd46_ar_h275.jpg
514 ms
tab-right-dark-da2413549ce324fc421ae86a0e5881ee.png
270 ms
42 ms
xd_arbiter.php
436 ms
xd_arbiter.php
511 ms
fundly.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 progressbar elements 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
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
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 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 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.
fundly.com
Open Graph data is detected on the main page of Fundly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: