Tools & Wizards About Us
insuresign.echosign.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

insuresign.echosign.com

Sign In — e-signature and e-sign Software Solution — Adobe Sign

Page Load Speed

3.3 sec in total

First Response

213 ms

Resources Loaded

2.9 sec

Page Rendered

147 ms

insuresign.echosign.com screenshot

About Website

Welcome to insuresign.echosign.com homepage info - get ready to check Insure Sign Echo best content for United States right away, or after learning these important things about insuresign.echosign.com

Adobe Sign provides a Sign In page for all returning Signers.

Visit insuresign.echosign.com

Key Findings

We analyzed Insuresign.echosign.com page load time and found that the first response time was 213 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

insuresign.echosign.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value2,510 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

login

213 ms

pfu1huz.js

168 ms

grayskin.css

234 ms

echosign.css

350 ms

translations.js

301 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Insuresign.echosign.com, 32% (7 requests) were made to Secure.na1.echocdn.com and 27% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (580 ms) relates to the external source Secure.na1.echocdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.6 kB (70%)

Content Size

174.4 kB

After Optimization

51.8 kB

  • HTML
  • JavaScript

In fact, the total size of Insuresign.echosign.com main page is 174.4 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. 25% of websites need less resources to load. Javascripts take 139.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 26.1 kB

  • Original 35.3 kB
  • After minification 29.0 kB
  • After compression 9.1 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 6.3 kB, which is 18% 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 26.1 kB or 74% of the original size.

JavaScript Optimization

-69%

Potential reduce by 96.5 kB

  • Original 139.2 kB
  • After minification 127.0 kB
  • After compression 42.7 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 96.5 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (47%)

Requests Now

17

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

login

login

213 ms

pfu1huz.js

pfu1huz.js

168 ms

grayskin.css

grayskin.css

234 ms

echosign.css

echosign.css

350 ms

translations.js

translations.js

301 ms

lib.js

lib.js

580 ms

all.js

all.js

543 ms

mbox.js

mbox.js

28 ms

insuresign.echosign.com

insuresign.echosign.com

97 ms

e93kqRA2orMmTNynfqmnQ4Z-7nBsVAyQfzFdWG70ssGffwrpgsMWeMJ6Mk6g5MsfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

e93kqRA2orMmTNynfqmnQ4Z-7nBsVAyQfzFdWG70ssGffwrpgsMWeMJ6Mk6g5MsfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

90 ms

fqHHH0oavYIJrgQF3Vrp64_L_DLLJf1uyZantAMBApCffwhpgsMWeMJ6Mk6g5MFfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

fqHHH0oavYIJrgQF3Vrp64_L_DLLJf1uyZantAMBApCffwhpgsMWeMJ6Mk6g5MFfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

134 ms

UWXCdk5kJrKABDtWMYORMjckyl56fIRgo0PMgr30EYCffFepgsMWeMJ6Mk6g5MifbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

UWXCdk5kJrKABDtWMYORMjckyl56fIRgo0PMgr30EYCffFepgsMWeMJ6Mk6g5MifbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff

337 ms

logo2010033515200283804831356289.png

logo2010033515200283804831356289.png

66 ms

A12_help.png

A12_help.png

30 ms

login-buttons.png

login-buttons.png

65 ms

s_code_echosign.js

s_code_echosign.js

257 ms

target.js

target.js

91 ms

ajax

ajax

23 ms

YeEGytxnpGrwTm0fI-AF0Qu9MB0QawuJphmE5HRWxpSff5pQgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

YeEGytxnpGrwTm0fI-AF0Qu9MB0QawuJphmE5HRWxpSff5pQgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff

41 ms

standard

standard

44 ms

p.gif

p.gif

122 ms

s41243155924603

s41243155924603

7 ms

Accessibility Review

insuresign.echosign.com accessibility score

98

Accessibility Issues

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.

Best Practices

insuresign.echosign.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

insuresign.echosign.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Insuresign.echosign.com 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 Insuresign.echosign.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

insuresign.echosign.com

Open Graph description is not detected on the main page of Insure Sign Echo. 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: