Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

developer.esignlive.com

Welcome to the OneSpan Community | OneSpan Community Platform

Page Load Speed

1.2 sec in total

First Response

74 ms

Resources Loaded

665 ms

Page Rendered

501 ms

developer.esignlive.com screenshot

About Website

Visit developer.esignlive.com now to see the best up-to-date Developer Esignlive content for United States and also check out these interesting facts you probably never knew about developer.esignlive.com

Integrate OneSpan Sign electronic signatures with your company's application and instantly obtain secure e-signatures. Learn how at our developer community.

Visit developer.esignlive.com

Key Findings

We analyzed Developer.esignlive.com page load time and found that the first response time was 74 ms and then it took 1.2 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

developer.esignlive.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

developer.esignlive.com

74 ms

community.onespan.com

136 ms

gtm.js

359 ms

css_-mq7BD4eqOHzl-crPjgZTdQm1oCwKJ0ASQzfBVxZLS8.css

66 ms

font-awesome.min.css

84 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Developer.esignlive.com, 35% (14 requests) were made to Community.onespan.com and 20% (8 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (359 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.3 kB (6%)

Content Size

867.2 kB

After Optimization

811.9 kB

In fact, the total size of Developer.esignlive.com main page is 867.2 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. 65% of websites need less resources to load. Javascripts take 419.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 54.7 kB

  • Original 71.5 kB
  • After minification 71.2 kB
  • After compression 16.8 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 54.7 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 348.0 kB
  • After minification 348.0 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. Developer Esignlive images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 584 B

  • Original 419.1 kB
  • After minification 419.1 kB
  • After compression 418.5 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.

CSS Optimization

-0%

Potential reduce by 17 B

  • Original 28.7 kB
  • After minification 28.7 kB
  • After compression 28.6 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. Developer.esignlive.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (58%)

Requests Now

33

After Optimization

14

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Developer Esignlive. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

developer.esignlive.com accessibility score

92

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-hidden="true"] elements contain focusable descendents

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.

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

developer.esignlive.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

developer.esignlive.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Developer.esignlive.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 Developer.esignlive.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

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