4.7 sec in total
825 ms
2.6 sec
1.3 sec
Click here to check amazing Digilocker content for India. Otherwise, check out these important facts you probably never knew about digilocker.co.in
www.digilocker.gov.in : Online Document Storage Facility, www.digitallocker.gov.in- Digi Locker,Digital Locker,Digital Marksheet 10th 12th CBSE Board Result
Visit digilocker.co.inWe analyzed Digilocker.co.in page load time and found that the first response time was 825 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
digilocker.co.in performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.4 s
39/100
25%
Value9.0 s
14/100
10%
Value1,520 ms
13/100
30%
Value0.393
26/100
15%
Value9.7 s
29/100
10%
825 ms
540 ms
39 ms
68 ms
49 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 24% of them (25 requests) were addressed to the original Digilocker.co.in, 43% (45 requests) were made to Secure.gravatar.com and 7% (7 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Digilocker.co.in.
Page size can be reduced by 664.7 kB (40%)
1.6 MB
979.2 kB
In fact, the total size of Digilocker.co.in main page is 1.6 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. 40% of websites need less resources to load. Images take 730.9 kB which makes up the majority of the site volume.
Potential reduce by 135.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. This page needs HTML code to be minified as it can gain 18.6 kB, which is 12% 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 135.8 kB or 86% of the original size.
Potential reduce by 72.4 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. Digilocker images are well optimized though.
Potential reduce by 338.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 338.4 kB or 57% of the original size.
Potential reduce by 118.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. Digilocker.co.in needs all CSS files to be minified and compressed as it can save up to 118.0 kB or 76% of the original size.
Number of requests can be reduced by 31 (32%)
98
67
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digilocker. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
digilocker.co.in
825 ms
wp-emoji-release.min.js
540 ms
screen.min.css
39 ms
genericons.css
68 ms
css
49 ms
style.css
44 ms
jetpack.css
56 ms
jquery.js
63 ms
jquery-migrate.min.js
53 ms
adsbygoogle.js
28 ms
genericons.css
13 ms
likebox.php
327 ms
Digilocker-8.png
1543 ms
Digilocker-Reg..png
1018 ms
sign-up.png
693 ms
e37c965010c59e24c9b4c6411dd8436a
167 ms
Digilocker-Acount-Created.png
485 ms
log-in.png
1311 ms
digilocker.co.in
791 ms
Digi-Logo.png
73 ms
cropped-digilocker.png
1870 ms
09ef89b01171be1d9930b86277d7f4aa
160 ms
54dc5ef5780756d124b342faa79dbab4
160 ms
31f2753bc10deeea599026130b1db04e
164 ms
8ae25b5f2cdf38903123f1e9ea1985b5
161 ms
868cdf14ecb50e0a06abf6489e547afb
158 ms
c1b4fc2e5e859ace1dea2b93677d2cb5
175 ms
f01237b65419a0e1ae5d50a49dfd5e4e
227 ms
a021ce92b1804ad3892d5860f3b49f90
217 ms
c2cfb6ad207bb5565cc1727794cc605e
218 ms
1b8c2e6c410a5142d167dc7bc686112f
216 ms
d0b52f5085e320ef00a55b334e995f94
217 ms
ba16b12291a94cda7e31491c34da1a93
460 ms
8cb750f58264a7d26794f3a9c4f866fa
243 ms
5345aa617f8b090669fcc819e7cf0114
253 ms
f86261890ffbf603548a8ddef7cf249c
250 ms
a17ebbb3d1bd51591c34931a2b2fc8f3
460 ms
a770b38e96275226f76c3ce451ebdd1b
260 ms
aabbd25f40b8bc87f6c1c576c7af2783
290 ms
css
1230 ms
ca-pub-3170864087454187.js
62 ms
zrt_lookup.html
76 ms
show_ads_impl.js
110 ms
fad515afa4f672014b2797b4c4fc8625
180 ms
603009228a0c469211bc7e4b1dda79d7
189 ms
2bac5951f420e7ffc87e5cf3c13d84ab
200 ms
bdc8767b771dd77dcbe9cdecf4d282e1
355 ms
90a03ceaf397b3606c90eebee983da16
291 ms
0d3ddfb63bf86b7f8d867361fbb5f1f7
291 ms
7416cf855ec69ace34bc826bc9e3e95e
291 ms
f8c2e87082cf4332a74266af292a96c7
292 ms
f799a42f45b1b5ad76fec2d14d15654d
292 ms
81a7e3d732e2d62f586cbe48fb6744ce
354 ms
cea1e8ab87c51b66849953e50ac67a34
323 ms
d3ff9220586d147c5cee47c069f97aa7
319 ms
b39f8a76c9070acd5617d7178d2d87a6
362 ms
fb4e85ac8c4e227ecc1147498f97e248
363 ms
photon.js
41 ms
devicepx-jetpack.js
55 ms
front.min.js
39 ms
gprofiles.js
342 ms
wpgroho.js
54 ms
comment-reply.min.js
533 ms
navigation.js
92 ms
custom-widget.js
106 ms
wp-embed.min.js
599 ms
spin.js
316 ms
jquery.spin.js
324 ms
jetpack-carousel.js
1118 ms
e-201736.js
55 ms
scrollup.png
1051 ms
6d45f15b99ff6b6ba058c89a7eb0d95a
384 ms
932c9c0a4ece20828629aede5c7925fb
378 ms
ads
61 ms
osd.js
22 ms
warning.png
579 ms
8767d097905af3122aa8a2b0619e9cc9
351 ms
308 ms
fb7f397816d9670f5ab539690662bb3b
344 ms
3212e8433b10f19a0249456109faeebc
366 ms
c1b118c58e9cdf3c98218beaecf8044d
361 ms
19c3e11c7844b6613491a7826ca48102
393 ms
ads
60 ms
f6b7ed3e97374c6c36d6ca96c8f28030
382 ms
ads
39 ms
ads
60 ms
ads
28 ms
YrFakaCOmcf.css
15 ms
UoiRCxUKCCh.js
19 ms
JrFVMrRpAYB.js
45 ms
T-D_V7C7Ph6.js
45 ms
13256292_1702240383396768_3323944037617511663_n.png
31 ms
13240778_1702240276730112_3166801689243242189_n.jpg
11 ms
20914269_1113613742105587_2113994533230617646_n.jpg
10 ms
21271306_590568518000450_6877822130228559190_n.jpg
112 ms
20993982_1524049281023220_7965346930848504898_n.jpg
12 ms
21078707_591728221217979_7476933027393019362_n.jpg
12 ms
18301913_1053225394811300_8101504083586623132_n.jpg
11 ms
wMkwmq5_RAN.png
6 ms
analytics.js
66 ms
hovercard.css
25 ms
services.css
24 ms
g.gif
31 ms
collect
12 ms
digilocker.co.in accessibility score
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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
digilocker.co.in 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
Page has valid source maps
digilocker.co.in SEO score
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 Digilocker.co.in 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 Digilocker.co.in 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.
digilocker.co.in
Open Graph data is detected on the main page of Digilocker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: