1.3 sec in total
38 ms
1.1 sec
185 ms
Click here to check amazing Support Docu Sign content for United States. Otherwise, check out these important facts you probably never knew about support.docusign.com
DocuSign's help and support portal dedicated to customer success with Digital Transaction Management.
Visit support.docusign.comWe analyzed Support.docusign.com page load time and found that the first response time was 38 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.
support.docusign.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value3.1 s
74/100
25%
Value3.9 s
83/100
10%
Value810 ms
36/100
30%
Value0
100/100
15%
Value15.5 s
7/100
10%
38 ms
14 ms
24 ms
65 ms
86 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 68% of them (69 requests) were addressed to the original Support.docusign.com, 6% (6 requests) were made to Google-analytics.com and 4% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Support.docusign.com.
Page size can be reduced by 438.9 kB (49%)
890.8 kB
452.0 kB
In fact, the total size of Support.docusign.com main page is 890.8 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. Javascripts take 651.6 kB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.3 kB or 82% of the original size.
Potential reduce by 54.6 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. Obviously, Support Docu Sign needs image optimization as it can save up to 54.6 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 322.0 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 322.0 kB or 49% of the original size.
Number of requests can be reduced by 34 (37%)
93
59
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Docu Sign. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
support.docusign.com
38 ms
stub.js
14 ms
VFRemote.js
24 ms
jquery.min.js
65 ms
jquery-ui.min.js
86 ms
jquery.validate.min.js
144 ms
js.cookie.js
34 ms
catComplete.js
42 ms
bootstrap.min.js
54 ms
tinymce.min.js
79 ms
script.js
54 ms
jquery-ui.css
79 ms
bootstrap.min.css
56 ms
fonts.css
75 ms
style.css
79 ms
NetworkTracking.js
75 ms
275532918.js
396 ms
E-v1.js
111 ms
mixpanel-2-2-1b.js
72 ms
logo.png
36 ms
ui-bg_flat_75_ffffff_40x100.png
29 ms
CSP_Trust_Status_Green
19 ms
banner.png
25 ms
search-icon.png
20 ms
CSP_icon_casestatus_pending
20 ms
CSP_icon_casestatus_open
23 ms
CSP_icon_casestatus_resolved
22 ms
servlet.ImageServer
60 ms
servlet.ImageServer
62 ms
servlet.ImageServer
60 ms
servlet.ImageServer
63 ms
servlet.ImageServer
181 ms
servlet.ImageServer
63 ms
servlet.ImageServer
95 ms
servlet.ImageServer
139 ms
servlet.ImageServer
144 ms
servlet.ImageServer
100 ms
servlet.ImageServer
141 ms
servlet.ImageServer
139 ms
servlet.ImageServer
142 ms
servlet.ImageServer
247 ms
servlet.ImageServer
246 ms
servlet.ImageServer
179 ms
servlet.ImageServer
246 ms
servlet.ImageServer
236 ms
servlet.ImageServer
246 ms
servlet.ImageServer
292 ms
servlet.ImageServer
246 ms
servlet.ImageServer
317 ms
servlet.ImageServer
291 ms
servlet.ImageServer
291 ms
servlet.ImageServer
290 ms
servlet.ImageServer
348 ms
servlet.ImageServer
395 ms
servlet.ImageServer
375 ms
servlet.ImageServer
347 ms
servlet.ImageServer
367 ms
servlet.ImageServer
392 ms
servlet.ImageServer
362 ms
servlet.ImageServer
362 ms
servlet.ImageServer
432 ms
servlet.ImageServer
460 ms
servlet.ImageServer
430 ms
27 ms
mavenpro-regular-webfont.woff
349 ms
mavenprolight300_regular-webfont.woff
362 ms
mavenpro-bold-webfont.woff
362 ms
martini-icons.woff
361 ms
servlet.ImageServer
390 ms
CSP_icon_showmore
354 ms
CSP_icon_showless
350 ms
servlet.ImageServer
397 ms
icon-disclosureindicator_blue.svg
322 ms
servlet.ImageServer
398 ms
servlet.ImageServer
370 ms
servlet.ImageServer
423 ms
CSP_icon_blog
283 ms
servlet.ImageServer
331 ms
event
86 ms
gtm.js
81 ms
45 ms
iframe_shim
23 ms
analytics.js
80 ms
elqCfg.min.js
78 ms
wrapper.js
269 ms
1IEYtQv1.min.js
116 ms
iframe-api-v1.js
140 ms
linkid.js
12 ms
svrGP
184 ms
collect
9 ms
collect
79 ms
ip.json
55 ms
pixel
52 ms
pixel
15 ms
collect
21 ms
collect
9 ms
ga-audiences
46 ms
collect
13 ms
ga-audiences
23 ms
svrGP.aspx
46 ms
collect
8 ms
iFrame.html
11 ms
support.docusign.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
support.docusign.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
support.docusign.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.docusign.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Support.docusign.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.
support.docusign.com
Open Graph data is detected on the main page of Support Docu Sign. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: