Tools & Wizards About Us
try.docsend.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

try.docsend.com

The pre-seed round in 2021-22: Adapting the pitch deck for a new market - Dropbox

Page Load Speed

1.7 sec in total

First Response

382 ms

Resources Loaded

1.2 sec

Page Rendered

73 ms

try.docsend.com screenshot

About Website

Visit try.docsend.com now to see the best up-to-date Try Docsend content for United States and also check out these interesting facts you probably never knew about try.docsend.com

New research on pre-seed startup fundraising in 2021-2022 shows data on how early-stage founders and investors ran their process. Download the report now.

Visit try.docsend.com

Key Findings

We analyzed Try.docsend.com page load time and found that the first response time was 382 ms and then it took 1.3 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.

Performance Metrics

try.docsend.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,410 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

fundraising-report

382 ms

privacy_consent,top_frame_marketing_tracker,ux_analytics

151 ms

utag.sync.js

50 ms

utag.js

104 ms

clientlib-base.9d86e5741780393fe182a97b50a39567.css

33 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Try.docsend.com, 16% (4 requests) were made to Aem.dropbox.com and 12% (3 requests) were made to Knotch-cdn.com. The less responsive or slowest element that took the longest time to load (561 ms) relates to the external source Cfl.dropboxstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.8 kB (45%)

Content Size

603.6 kB

After Optimization

330.8 kB

  • HTML
  • JavaScript

In fact, the total size of Try.docsend.com main page is 603.6 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. 60% of websites need less resources to load. HTML takes 356.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 272.5 kB

  • Original 356.9 kB
  • After minification 354.3 kB
  • After compression 84.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 272.5 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 343 B

  • Original 246.8 kB
  • After minification 246.7 kB
  • After compression 246.4 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.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fundraising-report

fundraising-report

382 ms

privacy_consent,top_frame_marketing_tracker,ux_analytics

privacy_consent,top_frame_marketing_tracker,ux_analytics

151 ms

utag.sync.js

utag.sync.js

50 ms

utag.js

utag.js

104 ms

clientlib-base.9d86e5741780393fe182a97b50a39567.css

clientlib-base.9d86e5741780393fe182a97b50a39567.css

33 ms

clientlib-base.bd1c8b8674d71c25d278618716d1a119.js

clientlib-base.bd1c8b8674d71c25d278618716d1a119.js

96 ms

clientlib-dependencies.4309b328bfd674671ae561f47a29ba61.js

clientlib-dependencies.4309b328bfd674671ae561f47a29ba61.js

65 ms

knotch.min.js

knotch.min.js

94 ms

ktag.min.js

ktag.min.js

96 ms

forms2.min.js

forms2.min.js

147 ms

privacy_consent%2Ctop_frame_marketing_tracker%2Cux_analytics

privacy_consent%2Ctop_frame_marketing_tracker%2Cux_analytics

123 ms

DocSend.svg

DocSend.svg

100 ms

index.html

index.html

23 ms

AtlasGrotesk-Regular-Web.woff

AtlasGrotesk-Regular-Web.woff

45 ms

AtlasGrotesk-Light-Web.woff

AtlasGrotesk-Light-Web.woff

561 ms

AtlasGrotesk-Thin-Web.woff

AtlasGrotesk-Thin-Web.woff

65 ms

AtlasGrotesk-Medium-Web.woff

AtlasGrotesk-Medium-Web.woff

73 ms

AtlasGrotesk-Bold-Web.woff

AtlasGrotesk-Bold-Web.woff

73 ms

AtlasGrotesk-Black-Web.woff

AtlasGrotesk-Black-Web.woff

302 ms

SharpGroteskDBCyrBook23.woff

SharpGroteskDBCyrBook23.woff

74 ms

SharpGroteskDBKO-Book23.woff

SharpGroteskDBKO-Book23.woff

83 ms

SharpGroteskDBThaiBook-23.woff

SharpGroteskDBThaiBook-23.woff

83 ms

45cf59b9-9d84-448e-91c8-961d17bf9bde.json

45cf59b9-9d84-448e-91c8-961d17bf9bde.json

2 ms

notify.bugsnag.com

notify.bugsnag.com

62 ms

45cf59b9-9d84-448e-91c8-961d17bf9bde.json

45cf59b9-9d84-448e-91c8-961d17bf9bde.json

3 ms

Accessibility Review

try.docsend.com accessibility score

85

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 IDs are not unique

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

Low

No form fields have multiple labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

try.docsend.com 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

Missing source maps for large first-party JavaScript

SEO Factors

try.docsend.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Try.docsend.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 Try.docsend.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.

Social Sharing Optimization

try.docsend.com

Open Graph data is detected on the main page of Try Docsend. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: