Tools & Wizards About Us
36dsa.fnd.to screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

36dsa.fnd.to

Funded Today - The Crowdfunding Experts

Page Load Speed

2.5 sec in total

First Response

144 ms

Resources Loaded

2.2 sec

Page Rendered

166 ms

36dsa.fnd.to screenshot

About Website

Visit 36dsa.fnd.to now to see the best up-to-date 36 Dsa Fnd content for United States and also check out these interesting facts you probably never knew about 36dsa.fnd.to

The world's most successful crowdfunding agency. Over $495,432,405 raised. Have an idea for a Kickstarter or Indiegogo campaign? We can help.

Visit 36dsa.fnd.to

Key Findings

We analyzed 36dsa.fnd.to page load time and found that the first response time was 144 ms and then it took 2.3 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.

Performance Metrics

36dsa.fnd.to performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

www.funded.today

144 ms

www.funded.today

871 ms

jquery.min.js

61 ms

css

58 ms

css

88 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 36dsa.fnd.to, 23% (13 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Funded.today.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.1 kB (18%)

Content Size

884.5 kB

After Optimization

727.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 36dsa.fnd.to main page is 884.5 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. 45% of websites need less resources to load. Images take 441.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.7 kB

  • Original 13.0 kB
  • After minification 11.0 kB
  • After compression 3.3 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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.7 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 9.4 kB

  • Original 441.2 kB
  • After minification 431.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. 36 Dsa Fnd images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 14.9 kB

  • Original 167.1 kB
  • After minification 166.7 kB
  • After compression 152.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-47%

Potential reduce by 123.1 kB

  • Original 263.2 kB
  • After minification 255.2 kB
  • After compression 140.1 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. 36dsa.fnd.to needs all CSS files to be minified and compressed as it can save up to 123.1 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (49%)

Requests Now

41

After Optimization

21

  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 36 Dsa Fnd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.funded.today

www.funded.today

144 ms

www.funded.today

www.funded.today

871 ms

jquery.min.js

jquery.min.js

61 ms

css

css

58 ms

css

css

88 ms

css

css

87 ms

bootstrap.min.css

bootstrap.min.css

39 ms

semantic.min.css

semantic.min.css

237 ms

semantic.min.js

semantic.min.js

342 ms

bootstrap-select.min.css

bootstrap-select.min.css

397 ms

bootstrap-select.min.js

bootstrap-select.min.js

425 ms

moment.min.js

moment.min.js

428 ms

daterangepicker.min.js

daterangepicker.min.js

449 ms

daterangepicker.min.css

daterangepicker.min.css

460 ms

jquery.tablesorter.js

jquery.tablesorter.js

44 ms

jquery.tablesorter.widgets.min.js

jquery.tablesorter.widgets.min.js

47 ms

widget-staticRow.min.js

widget-staticRow.min.js

51 ms

gen_validatorv4.min.js

gen_validatorv4.min.js

469 ms

base.css

base.css

504 ms

funded-today-v0.1.css

funded-today-v0.1.css

474 ms

main.js

main.js

474 ms

css

css

31 ms

analytics.js

analytics.js

106 ms

fbevents.js

fbevents.js

85 ms

logo_white.png

logo_white.png

102 ms

home_icon_white.png

home_icon_white.png

103 ms

pledges_icon_white.png

pledges_icon_white.png

102 ms

crowdcon_icon_white.png

crowdcon_icon_white.png

101 ms

blog_icon_white.png

blog_icon_white.png

102 ms

about_icon_white.png

about_icon_white.png

101 ms

logo_black.jpg

logo_black.jpg

144 ms

mobile-poster.png

mobile-poster.png

334 ms

learn_more_round.png

learn_more_round.png

146 ms

cred.jpg

cred.jpg

171 ms

pledges_icon.png

pledges_icon.png

144 ms

crowdcon_icon.png

crowdcon_icon.png

157 ms

blog_icon.png

blog_icon.png

171 ms

ft-fb1.png

ft-fb1.png

175 ms

ft-tw1.png

ft-tw1.png

175 ms

ft-email.png

ft-email.png

175 ms

footer-logo.png

footer-logo.png

203 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

72 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

77 ms

Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff

Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff

77 ms

vzIUHo9z-oJ4WgkpPOtg13YhjbSpvc47ee6xR_80Hnw.woff

vzIUHo9z-oJ4WgkpPOtg13YhjbSpvc47ee6xR_80Hnw.woff

77 ms

d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff

d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff

82 ms

mnpfi9pxYH-Go5UiibESIrO3LdcAZYWl9Si6vvxL-qU.woff

mnpfi9pxYH-Go5UiibESIrO3LdcAZYWl9Si6vvxL-qU.woff

75 ms

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff

80 ms

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff

80 ms

EInbV5DfGHOiMmvb1Xr-hqRDOzjiPcYnFooOUGCOsRk.woff

EInbV5DfGHOiMmvb1Xr-hqRDOzjiPcYnFooOUGCOsRk.woff

79 ms

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff

74 ms

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff

73 ms

evC1haE-MsorTl_A7_uSGbO3LdcAZYWl9Si6vvxL-qU.woff

evC1haE-MsorTl_A7_uSGbO3LdcAZYWl9Si6vvxL-qU.woff

93 ms

2PcBT6-VmYhQCus-O11S5-vvDin1pK8aKteLpeZ5c0A.woff

2PcBT6-VmYhQCus-O11S5-vvDin1pK8aKteLpeZ5c0A.woff

90 ms

111 ms

collect

collect

45 ms

Accessibility Review

36dsa.fnd.to accessibility score

84

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

36dsa.fnd.to best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

36dsa.fnd.to SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 36dsa.fnd.to can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 36dsa.fnd.to 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.

Social Sharing Optimization

36dsa.fnd.to

Open Graph description is not detected on the main page of 36 Dsa Fnd. 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: