4.1 sec in total
485 ms
3.4 sec
190 ms
Click here to check amazing Lock content. Otherwise, check out these important facts you probably never knew about lock.ru
1С-Битрикс: Управление сайтом
Visit lock.ruWe analyzed Lock.ru page load time and found that the first response time was 485 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lock.ru performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value1.1 s
100/100
10%
Value0 ms
100/100
30%
Value0.002
100/100
15%
Value0.7 s
100/100
10%
485 ms
1184 ms
731 ms
267 ms
267 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lock.ru, 79% (38 requests) were made to Tlock.ru and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Tlock.ru.
Page size can be reduced by 413.9 kB (40%)
1.0 MB
625.3 kB
In fact, the total size of Lock.ru main page is 1.0 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. 20% of websites need less resources to load. Images take 581.4 kB which makes up the majority of the site volume.
Potential reduce by 20.9 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 3.1 kB, which is 11% 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 20.9 kB or 75% of the original size.
Potential reduce by 52.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. Lock images are well optimized though.
Potential reduce by 313.6 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 313.6 kB or 79% of the original size.
Potential reduce by 26.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. Lock.ru needs all CSS files to be minified and compressed as it can save up to 26.6 kB or 80% of the original size.
Number of requests can be reduced by 24 (59%)
41
17
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lock. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lock.ru
485 ms
www.tlock.ru
1184 ms
jquery.js
731 ms
funcs.js
267 ms
Validator.js
267 ms
core.css
273 ms
style.css
288 ms
style.css
287 ms
style.css
396 ms
template_styles.css
407 ms
core.js
844 ms
core_ajax.js
566 ms
session.js
529 ms
rsasecurity.js
667 ms
script.js
549 ms
lightbox.js
802 ms
lightbox.css
682 ms
watch.js
0 ms
analytics.js
9 ms
collect
13 ms
blank.gif
564 ms
MB16_468x60_uch_new.gif
277 ms
spread.php
502 ms
spread.php
270 ms
fon.png
288 ms
logo.png
158 ms
1.gif
144 ms
login_go.gif
158 ms
kalelottery.jpg
287 ms
submitit.gif
157 ms
new.gif
275 ms
5e775ffb5f3a683852dee4e6661a7093_10362_01.jpg
295 ms
9024500c7fdca9e2590682ace4a25a91_33107_01.jpg
287 ms
4efd2403b664bfb592117430a180d7fe_34753_01.jpg
292 ms
special.gif
407 ms
a350c7f24be5c69b460b141cf795b3c5_1107_01.jpg
415 ms
6518721df02f816eaf2e67a49ef19b41_13789_01.jpg
416 ms
8f67abfbeae19ec869f47bb8aecdbd25_13950_01.jpg
451 ms
armadillo_classic1.jpg
725 ms
submitit2.gif
440 ms
forma.png
521 ms
searchit.gif
532 ms
main_news.gif
519 ms
main_news2.gif
547 ms
searchit2.gif
552 ms
bg_pol1.gif
653 ms
mb16_468x60_uch_new.gif
381 ms
blank.gif
337 ms
lock.ru accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lock.ru 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
lock.ru SEO score
RU
N/A
WINDOWS-1251
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lock.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Lock.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lock.ru
Open Graph description is not detected on the main page of Lock. 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: