20.2 sec in total
420 ms
19.2 sec
636 ms
Welcome to elocks.ru homepage info - get ready to check Elocks best content for Russia right away, or after learning these important things about elocks.ru
Основное направление нашей компании – это сервис всех видов замков и дверей, вскрытие замков дверей и автомобилей, а также сейфов, ремонт и установка дверей. Забудьте о случаях, когда при поломке замк...
Visit elocks.ruWe analyzed Elocks.ru page load time and found that the first response time was 420 ms and then it took 19.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
elocks.ru performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value9.1 s
1/100
25%
Value12.6 s
3/100
10%
Value32,970 ms
0/100
30%
Value0.001
100/100
15%
Value43.4 s
0/100
10%
420 ms
735 ms
283 ms
420 ms
285 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 52% of them (83 requests) were addressed to the original Elocks.ru, 9% (15 requests) were made to Api-maps.yandex.ru and 6% (10 requests) were made to Vec01.maps.yandex.net. The less responsive or slowest element that took the longest time to load (15.8 sec) belongs to the original domain Elocks.ru.
Page size can be reduced by 816.5 kB (33%)
2.5 MB
1.7 MB
In fact, the total size of Elocks.ru main page is 2.5 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. 75% 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 38.7 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 38.7 kB or 77% of the original size.
Potential reduce by 417.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, Elocks needs image optimization as it can save up to 417.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 307.9 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 307.9 kB or 68% of the original size.
Potential reduce by 52.4 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. Elocks.ru needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 82% of the original size.
Number of requests can be reduced by 39 (27%)
147
108
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elocks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
elocks.ru
420 ms
www.elocks.ru
735 ms
plugins.css
283 ms
screen.css
420 ms
magnific-popup.css
285 ms
357 ms
jquery-1.11.1.min.js
534 ms
jquery.easing.min.js
260 ms
jquery.mask.min.js
274 ms
jquery.magnific-popup.js
415 ms
inside.js
316 ms
slick.min.js
522 ms
main.js
411 ms
analytics.js
22 ms
logo.png
145 ms
ico_home_cur.png
147 ms
i1.png
265 ms
i2.png
265 ms
i3.png
284 ms
i4.png
291 ms
doverie.png
902 ms
i13.png
374 ms
i24.png
528 ms
i25.png
665 ms
i26.png
754 ms
i29.png
421 ms
i30.png
501 ms
i280.png
755 ms
i308.png
663 ms
i231.png
665 ms
i32.png
772 ms
i241.png
813 ms
i249.png
811 ms
i235.png
977 ms
i233.png
835 ms
i252.png
913 ms
i330.png
1000 ms
i247.png
1138 ms
i334.png
1025 ms
i31.png
1047 ms
i340.png
1072 ms
i336.png
1134 ms
i28.png
1139 ms
i170.png
1258 ms
watch.js
12 ms
i202.png
1247 ms
i206.png
1247 ms
collect
13 ms
587 ms
collect
70 ms
i173.png
1192 ms
i197.png
1534 ms
ga-audiences
70 ms
i188.png
1171 ms
i221.png
1502 ms
i213.png
1425 ms
i342.png
1416 ms
i259.png
1389 ms
i225.png
1389 ms
i287.png
1367 ms
i306.png
1362 ms
i1.jpg
1309 ms
i2.jpg
1262 ms
i3.jpg
1241 ms
i4.jpg
1154 ms
124 ms
plusone.js
154 ms
code.js
600 ms
chatra.js
173 ms
i6.jpg
1108 ms
i5.jpg
1114 ms
BebasNeue-Bold.ttf
1484 ms
i1.png
1008 ms
i2.png
1028 ms
309 ms
i3.png
1099 ms
i4.png
1096 ms
logo_foot.png
1095 ms
cb=gapi.loaded_0
35 ms
cb=gapi.loaded_1
53 ms
fastbutton
139 ms
chat.chatra.io
128 ms
vk.png
1192 ms
postmessageRelay
158 ms
e55dc2684a14fbbaed861ba6c0dbd9870f058a69.css
244 ms
aefd4518ebaa68e92832cdf9e4052ee05867581a.js
621 ms
tw.png
1132 ms
f.png
1211 ms
cb=gapi.loaded_0
79 ms
cb=gapi.loaded_1
78 ms
grlryt2bdKIyfMSOhzd1eA.woff
146 ms
i.png
1192 ms
home_abs_bg.png
1026 ms
head_phone.png
1130 ms
1077434459-postmessagerelay.js
213 ms
rpc:shindig_random.js
209 ms
i6.jpg
15774 ms
super_shadow.png
1063 ms
news_one.png
1201 ms
callme_zag_span.png
1202 ms
callme_zag_vop.png
1226 ms
services_zag.png
1108 ms
ico_a_v1.png
1107 ms
cb=gapi.loaded_0
346 ms
home_txt_bg.png
1635 ms
footer.png
1156 ms
combine.js
711 ms
gallery-prev.png
877 ms
gallery-next.png
1255 ms
counter
162 ms
combine.js
372 ms
info
30 ms
util_cursor_storage_grab.cur
123 ms
util_cursor_storage_grabbing.cur
178 ms
util_cursor_storage_help.cur
226 ms
util_cursor_storage_zoom_in.cur
350 ms
sync
183 ms
sync
71 ms
tracker
248 ms
196 ms
tiles
248 ms
tiles
466 ms
tiles
455 ms
tiles
217 ms
tiles
215 ms
tiles
193 ms
combine.js
490 ms
inception-1458751524111.js
435 ms
tiles
202 ms
tiles
200 ms
197 ms
combine.js
289 ms
tiles
259 ms
tiles
234 ms
tiles
234 ms
tiles
317 ms
tiles
147 ms
tiles
174 ms
tiles
214 ms
tiles
230 ms
tiles
255 ms
tiles
122 ms
tiles
252 ms
tiles
245 ms
tiles
93 ms
tiles
61 ms
tiles
88 ms
tiles
58 ms
tiles
121 ms
tiles
277 ms
tiles
68 ms
tiles
201 ms
tiles
66 ms
tiles
262 ms
tiles
226 ms
tiles
230 ms
tiles
86 ms
tiles
178 ms
tiles
168 ms
tiles
168 ms
elocks.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
elocks.ru 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
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
Issues were logged in the Issues panel in Chrome Devtools
elocks.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elocks.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Elocks.ru 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.
elocks.ru
Open Graph description is not detected on the main page of Elocks. 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: