8.8 sec in total
1.6 sec
6.7 sec
470 ms
Visit idsign.app now to see the best up-to-date IDsign content for India and also check out these interesting facts you probably never knew about idsign.app
LICENSED CERTIFYING AUTHORITY QCID Technologies Private Limited Get in touch IDSign CA Products & Services Digital Signature Certificates Digital Signature Certificates (DSC) or Digital Signature are ...
Visit idsign.appWe analyzed Idsign.app page load time and found that the first response time was 1.6 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
idsign.app performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value25.9 s
0/100
25%
Value15.2 s
1/100
10%
Value2,470 ms
4/100
30%
Value0.023
100/100
15%
Value23.1 s
1/100
10%
1607 ms
253 ms
498 ms
711 ms
722 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 61% of them (71 requests) were addressed to the original Idsign.app, 33% (38 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Idsign.app.
Page size can be reduced by 157.0 kB (11%)
1.4 MB
1.2 MB
In fact, the total size of Idsign.app main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 760.3 kB which makes up the majority of the site volume.
Potential reduce by 139.0 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 139.0 kB or 84% of the original size.
Potential reduce by 1.9 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. IDsign images are well optimized though.
Potential reduce by 2.4 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 13.7 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. Idsign.app has all CSS files already compressed.
Number of requests can be reduced by 64 (90%)
71
7
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IDsign. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
www.idsign.app
1607 ms
frontend.min.css
253 ms
post-1383.css
498 ms
mediaelementplayer-legacy.min.css
711 ms
wp-mediaelement.min.css
722 ms
styles.css
722 ms
lc-public.css
727 ms
wp-ulike.min.css
742 ms
base.css
759 ms
auxin-icon.css
948 ms
main.css
1213 ms
ekiticons.css
966 ms
elementor-icons.min.css
975 ms
swiper.min.css
986 ms
post-106.css
1013 ms
elementor.css
1185 ms
elementor-widgets.css
1274 ms
she-header-style.css
1274 ms
post-249.css
1275 ms
css
52 ms
custom.css
1280 ms
portfolio.css
1423 ms
post-139.css
1453 ms
post-119.css
1457 ms
widget-styles.css
1467 ms
responsive.css
1492 ms
css
71 ms
opensanshebrew.css
80 ms
fontawesome.min.css
1521 ms
solid.min.css
1660 ms
regular.min.css
1694 ms
jquery.min.js
1731 ms
jquery-migrate.min.js
1752 ms
loader.js
62 ms
lc-public.js
1755 ms
she-header.js
1773 ms
modernizr-custom.min.js
1899 ms
js
96 ms
pixel.js
64 ms
imagesloaded.min.js
2277 ms
masonry.min.js
2278 ms
plugins.min.js
2469 ms
e-202447.js
33 ms
scripts.min.js
2277 ms
widgets.js
2033 ms
mediaelement-and-player.min.js
1795 ms
mediaelement-migrate.min.js
1583 ms
wp-mediaelement.min.js
1574 ms
plugins.min.js
1573 ms
scripts.js
1581 ms
portfolio.js
1736 ms
index.js
1710 ms
index.js
1528 ms
wp-ulike.min.js
1605 ms
frontend-script.js
1649 ms
widget-scripts.js
1648 ms
custom.js
1652 ms
webpack.runtime.min.js
1500 ms
frontend-modules.min.js
1426 ms
waypoints.min.js
1436 ms
core.min.js
1520 ms
frontend.min.js
1591 ms
animate-circle.min.js
1629 ms
elementor.js
1504 ms
underscore.min.js
1491 ms
wp-util.min.js
1496 ms
frontend.min.js
1560 ms
image001-logo.png
1014 ms
Path-17.svg
1028 ms
prj-sld-img-min.jpg
1521 ms
sign-sld-1024x848.jpeg
1315 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
38 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
73 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
71 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
70 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
69 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
73 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
72 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
74 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
76 ms
fa-solid-900.woff
1261 ms
fa-regular-400.woff
1052 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf
77 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf
73 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf
76 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf
76 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf
77 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf
79 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf
81 ms
elementskit.woff
1573 ms
OpenSansHebrew-ExtraBold.woff
78 ms
OpenSansHebrew-Bold.woff
81 ms
OpenSansHebrew-Regular.woff
78 ms
OpenSansHebrew-Light.woff
80 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
85 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
84 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
84 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
83 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
84 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
83 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
169 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
170 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
168 ms
auxin-front-2.woff
1288 ms
pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf
168 ms
pxiGyp8kv8JHgFVrJJLucHtF.ttf
170 ms
pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf
168 ms
pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf
175 ms
pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf
173 ms
pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf
173 ms
pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf
173 ms
auxin-front.woff
1626 ms
pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf
114 ms
pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf
111 ms
symbols.svg
558 ms
yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
836 ms
idsign.app accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
idsign.app best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
idsign.app 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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idsign.app 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 Idsign.app 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.
idsign.app
Open Graph data is detected on the main page of IDsign. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: