2.6 sec in total
11 ms
2.3 sec
239 ms
Welcome to hellosign.com homepage info - get ready to check Hello Sign best content for United States right away, or after learning these important things about hellosign.com
Dropbox Sign (formerly HelloSign) is the easiest way to send, receive and manage legally binding electronic signatures. Try it free!
Visit hellosign.comWe analyzed Hellosign.com page load time and found that the first response time was 11 ms and then it took 2.6 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.
hellosign.com performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value19.8 s
0/100
25%
Value12.9 s
2/100
10%
Value1,740 ms
10/100
30%
Value0
100/100
15%
Value24.8 s
0/100
10%
11 ms
559 ms
73 ms
71 ms
174 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Hellosign.com, 41% (45 requests) were made to S3.amazonaws.com and 11% (12 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (565 ms) relates to the external source Assets.zendesk.com.
Page size can be reduced by 2.4 MB (71%)
3.4 MB
963.8 kB
In fact, the total size of Hellosign.com main page is 3.4 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. 60% of websites need less resources to load. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 72.6 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 72.6 kB or 83% of the original size.
Potential reduce by 28.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, Hello Sign needs image optimization as it can save up to 28.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.9 MB
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 1.9 MB or 71% of the original size.
Potential reduce by 382.4 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. Hellosign.com needs all CSS files to be minified and compressed as it can save up to 382.4 kB or 86% of the original size.
Number of requests can be reduced by 46 (53%)
86
40
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hello 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 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hellosign.com
11 ms
www.hellosign.com
559 ms
es5-shim.js
73 ms
es5-sham.js
71 ms
10955010.js
174 ms
default.bundle.js
82 ms
hellosign.bundle.js
92 ms
jquery-1.11.0.min.js
80 ms
6-jquery.hellofax.ajax-override.js
81 ms
fastclick.js
78 ms
hammer.js
379 ms
foundation.js
81 ms
awb1ysu.js
147 ms
hellosign.css
96 ms
api.js
71 ms
forms2.min.js
69 ms
event
213 ms
www.hellosign.com
55 ms
analytics.js
189 ms
gtm.js
120 ms
footer_social_twitter.png
48 ms
footer_social_fb.png
89 ms
footer_social_googleplus.png
88 ms
footer_social_linkedin.png
88 ms
footer_social_instagram.png
88 ms
footer_madeinsf.png
87 ms
skyhigh-seal.png
88 ms
logo_white@2x.png
105 ms
53f2cf12db6a96c759ef2da82bd7f115.png
106 ms
ed3bc2257057b500d9ea3afe74ba8f5f.png
106 ms
api-icon-white@2x.png
307 ms
po_icon.png
105 ms
approvals_icon.png
105 ms
deals_icon.png
176 ms
onboard_icon.png
177 ms
agreements_icon.png
176 ms
features_toolsforbusiness@2x.png
174 ms
features_banklevelsecurity@2x.png
175 ms
features_googleintegrations@2x.png
176 ms
logos_kickstarter@2x.png
177 ms
logos_twitter@2x.png
177 ms
logos_samsung@2x.png
177 ms
logos_lyft@2x.png
180 ms
logos_intuit_stacked_black@2x.png
177 ms
45968f7692fd4bdc61065ad61bb3111e.png
178 ms
werehiring@2x.png
178 ms
footer_logo_white@2x.png
179 ms
skyhigh-seal_@2x.png
179 ms
footer_social_twitter@2x.png
180 ms
footer_social_fb@2x.png
179 ms
footer_social_googleplus@2x.png
180 ms
footer_social_linkedin@2x.png
180 ms
footer_social_instagram@2x.png
301 ms
footer_madeinsf@2x.png
302 ms
recaptcha__en.js
145 ms
ZPknmvaJ7OkkH7BVJmIecJUIq06pnU7AJoio6EY_zKtffHY3gsMdeMJ6Mk6f5Mw.woff
68 ms
Uhoh7WKz7NCVTi3ZpxOYcobBnzl9o73D2QSOuPniCh3ff4x3gsMdeMJ6Mk6f5MI.woff
144 ms
KVSoBhzrCzhjzIizNeqz2Ck5az7a_Mahp7A59cHuNQtffHV3gsMdeMJ6Mk6f5Mb.woff
149 ms
3QUA9b820pm24P8uwCC-V2a_MVXq4hd4ldMFw0sZ5wMffHL3gsMdeMJ6Mk6f5Mj.woff
270 ms
HtoYSVzeXRfn1VHNmwd0wQ_KH8H5OYRuB9zzbqrn0ejffH13gsMdeMJ6Mk6f5MS.woff
270 ms
getForm
308 ms
main.js
565 ms
roundtrip.js
299 ms
oct.js
267 ms
bat.js
115 ms
fbevents.js
146 ms
munchkin.js
99 ms
collect
57 ms
collect
212 ms
pA1FdT4pGOEiy7Iy65JNJX1pQIvRXrV96_QMy3QfJWbff528ggMdeMJ6Mk6f5Mt.woff
42 ms
xCw2p4PBm2DdhX3_U0h1iap0LWtG_ldOtig4k1x4Th3ff5Q8ggMdeMJ6Mk6f5gI.woff
60 ms
cD4G6-C6JjbFtlhF76ouK-CcmjECPSCVm-R_XbeT9WIffFx8ggMdeMJ6Mk6f5Mb.woff
72 ms
ZBdefQNcNMzAT9Ak_28HmLdBdigAHKLmFbLldOw_lvGff5V8ggMdeMJ6Mk6f5MS.woff
41 ms
MRBPXIDk7MtfckcscxB8R-TjoB-iLHVOFmvPOWRBXgSffHO3gsMdeMJ6Mk6f5MX.woff
162 ms
collect
58 ms
collect
72 ms
forms2.css
14 ms
forms2-theme-simple.css
43 ms
162 ms
56df829b2760d3e961cd83169a825ab9.png
68 ms
p.gif
155 ms
ga-audiences
49 ms
XDFrame
151 ms
adsct
103 ms
adsct
113 ms
munchkin.js
24 ms
visitWebPage
49 ms
XMCKTFHLL5CIPODIC4BPYW.js
43 ms
67 ms
64 ms
out
46 ms
out
49 ms
out
49 ms
out
48 ms
out
50 ms
adsct
111 ms
pixel
141 ms
117 ms
117 ms
update.html
94 ms
sync
21 ms
sd
4 ms
377928.gif
19 ms
pixel
16 ms
blips
60 ms
in
8 ms
config
57 ms
nr-852.min.js
248 ms
widget_v2.132.js
12 ms
hellosign.com accessibility score
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
hellosign.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
hellosign.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hellosign.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 Hellosign.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.
hellosign.com
Open Graph description is not detected on the main page of Hello Sign. 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: