2.6 sec in total
492 ms
2 sec
133 ms
Visit isign.io now to see the best up-to-date Isign content for Lithuania and also check out these interesting facts you probably never knew about isign.io
Easily and securely sign legally binding documents in the EU using electronic signatures. With Dokobit it’s a breeze. Start signing now — it’s free.
Visit isign.ioWe analyzed Isign.io page load time and found that the first response time was 492 ms and then it took 2.2 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.
isign.io performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value7.3 s
4/100
25%
Value5.9 s
48/100
10%
Value590 ms
50/100
30%
Value0.001
100/100
15%
Value7.4 s
49/100
10%
492 ms
236 ms
335 ms
601 ms
456 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Isign.io, 3% (1 request) were made to Cdn.cookielaw.org and 3% (1 request) were made to Sgtm.dokobit.com. The less responsive or slowest element that took the longest time to load (837 ms) relates to the external source Sgtm.dokobit.com.
Page size can be reduced by 46.9 kB (18%)
261.9 kB
215.0 kB
In fact, the total size of Isign.io main page is 261.9 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. 30% of websites need less resources to load. Javascripts take 108.9 kB which makes up the majority of the site volume.
Potential reduce by 30.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 10.3 kB, which is 26% 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 30.1 kB or 77% of the original size.
Potential reduce by 12.5 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, Isign needs image optimization as it can save up to 12.5 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.3 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.
Potential reduce by 2.0 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. Isign.io has all CSS files already compressed.
Number of requests can be reduced by 8 (30%)
27
19
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Isign. 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.
www.dokobit.com
492 ms
app.css
236 ms
captcha.js
335 ms
base.js
601 ms
OtAutoBlock.js
456 ms
otSDKStub.js
28 ms
vivus.min.js
338 ms
le.min.js
387 ms
app.js
374 ms
animations.js
446 ms
gtm.js
837 ms
logo-dokobit-by-signicat-ua.svg
188 ms
Connection.svg
184 ms
circle-k.png
186 ms
islandsbanki.png
181 ms
creditinfo.png
195 ms
telia.png
186 ms
luminor.png
296 ms
toyota.png
297 ms
ellex.png
297 ms
workis.png
298 ms
modus-group.png
299 ms
bta.png
308 ms
rimi.png
408 ms
logo-dokobit-by-signicat-white.svg
409 ms
EU_trust_mark_en.png
411 ms
iso.png
412 ms
signicat_stamp_of_trust.svg
413 ms
mabry-regular-pro.woff
566 ms
mabry-medium-pro.woff
555 ms
mabry-bold-pro.woff
765 ms
isign.io accessibility score
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
Image elements do not have [alt] attributes
isign.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
isign.io 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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Isign.io 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 Isign.io 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.
isign.io
Open Graph data is detected on the main page of Isign. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: