1.4 sec in total
69 ms
1.2 sec
185 ms
Click here to check amazing 12 Fnd content for United States. Otherwise, check out these important facts you probably never knew about 12.fnd.to
The world's most successful crowdfunding agency. Over $546,992,774 raised. Have an idea for a Kickstarter or Indiegogo campaign? We can help.
Visit 12.fnd.toWe analyzed 12.fnd.to page load time and found that the first response time was 69 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
12.fnd.to performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value9.7 s
0/100
25%
Value6.3 s
42/100
10%
Value670 ms
44/100
30%
Value0.084
93/100
15%
Value17.4 s
4/100
10%
69 ms
440 ms
74 ms
73 ms
112 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 12.fnd.to, 9% (4 requests) were made to Fonts.googleapis.com and 7% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (440 ms) relates to the external source Funded.today.
Page size can be reduced by 157.1 kB (18%)
884.5 kB
727.5 kB
In fact, the total size of 12.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.
Potential reduce by 9.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. 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.
Potential reduce by 9.4 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. 12 Fnd images are well optimized though.
Potential reduce by 14.9 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.
Potential reduce by 123.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. 12.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.
Number of requests can be reduced by 20 (49%)
41
21
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 12 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.
www.funded.today
69 ms
www.funded.today
440 ms
jquery.min.js
74 ms
css
73 ms
css
112 ms
css
122 ms
bootstrap.min.css
41 ms
semantic.min.css
146 ms
semantic.min.js
212 ms
bootstrap-select.min.css
200 ms
bootstrap-select.min.js
201 ms
moment.min.js
200 ms
daterangepicker.min.js
200 ms
daterangepicker.min.css
206 ms
jquery.tablesorter.js
48 ms
jquery.tablesorter.widgets.min.js
52 ms
widget-staticRow.min.js
107 ms
gen_validatorv4.min.js
206 ms
base.css
240 ms
funded-today-v0.1.css
206 ms
main.js
206 ms
css
54 ms
analytics.js
81 ms
fbevents.js
31 ms
logo_white.png
53 ms
home_icon_white.png
54 ms
pledges_icon_white.png
52 ms
crowdcon_icon_white.png
51 ms
blog_icon_white.png
52 ms
about_icon_white.png
52 ms
logo_black.jpg
85 ms
mobile-poster.png
216 ms
learn_more_round.png
81 ms
cred.jpg
124 ms
pledges_icon.png
82 ms
crowdcon_icon.png
85 ms
blog_icon.png
114 ms
ft-fb1.png
115 ms
ft-tw1.png
125 ms
ft-email.png
126 ms
footer-logo.png
148 ms
93 ms
collect
25 ms
12.fnd.to 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
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.
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
Links do not have a discernible name
12.fnd.to 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
Browser errors were logged to the console
Page has valid source maps
12.fnd.to SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 12.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 12.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.
12.fnd.to
Open Graph description is not detected on the main page of 12 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: