Tools & Wizards About Us
elocks.ru screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

elocks.ru

Аварийная служба вскрытия дверей в Санкт Петербурге

Page Load Speed

6.1 sec in total

First Response

558 ms

Resources Loaded

5.2 sec

Page Rendered

342 ms

elocks.ru screenshot

About Website

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.ru

Key Findings

We analyzed Elocks.ru page load time and found that the first response time was 558 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

elocks.ru performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value5,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

elocks.ru

558 ms

elocks.ru

582 ms

www.elocks.ru

424 ms

www.elocks.ru

583 ms

plugins.css

140 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 73% of them (84 requests) were addressed to the original Elocks.ru, 5% (6 requests) were made to Apis.google.com and 4% (5 requests) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.callibri.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.8 kB (19%)

Content Size

748.5 kB

After Optimization

605.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elocks.ru main page is 748.5 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. 50% of websites need less resources to load. Images take 384.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 43.3 kB

  • Original 55.5 kB
  • After minification 51.6 kB
  • After compression 12.2 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 43.3 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 25.1 kB

  • Original 384.8 kB
  • After minification 359.6 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. Elocks images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 66.4 kB

  • Original 286.6 kB
  • After minification 285.7 kB
  • After compression 220.2 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 66.4 kB or 23% of the original size.

CSS Optimization

-36%

Potential reduce by 7.9 kB

  • Original 21.7 kB
  • After minification 19.8 kB
  • After compression 13.8 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 7.9 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (35%)

Requests Now

107

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 107 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 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

elocks.ru

elocks.ru

558 ms

elocks.ru

elocks.ru

582 ms

www.elocks.ru

www.elocks.ru

424 ms

www.elocks.ru

www.elocks.ru

583 ms

plugins.css

plugins.css

140 ms

screen.css

screen.css

282 ms

magnific-popup.css

magnific-popup.css

415 ms

callibri.js

callibri.js

1265 ms

684 ms

jquery.min.js

jquery.min.js

18 ms

jquery.easing.min.js

jquery.easing.min.js

441 ms

jquery.mask.min.js

jquery.mask.min.js

441 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

568 ms

inside.js

inside.js

441 ms

slick.min.js

slick.min.js

441 ms

main.js

main.js

549 ms

gtm.js

gtm.js

71 ms

logo.png

logo.png

138 ms

watsap.png

watsap.png

140 ms

viber.png

viber.png

154 ms

telega.png

telega.png

154 ms

ico_home_cur.png

ico_home_cur.png

298 ms

i1.png

i1.png

299 ms

i2.png

i2.png

300 ms

i3.png

i3.png

300 ms

i4.png

i4.png

300 ms

doverie2.png

doverie2.png

431 ms

i13.png

i13.png

408 ms

i308.png

i308.png

411 ms

i24.png

i24.png

418 ms

i25.png

i25.png

430 ms

i30.png

i30.png

432 ms

i231.png

i231.png

544 ms

i32.png

i32.png

547 ms

i26.png

i26.png

560 ms

i252.png

i252.png

568 ms

i330.png

i330.png

569 ms

i336.png

i336.png

570 ms

i28.png

i28.png

679 ms

i29.png

i29.png

682 ms

i340.png

i340.png

697 ms

i235.png

i235.png

705 ms

i249.png

i249.png

706 ms

i31.png

i31.png

709 ms

i334.png

i334.png

815 ms

i241.png

i241.png

819 ms

i287.png

i287.png

816 ms

i173.png

i173.png

857 ms

i170.png

i170.png

857 ms

i202.png

i202.png

857 ms

i206.png

i206.png

898 ms

i197.png

i197.png

827 ms

i188.png

i188.png

841 ms

i221.png

i221.png

847 ms

i213.png

i213.png

836 ms

i259.png

i259.png

839 ms

i1.jpg

i1.jpg

940 ms

plusone.js

plusone.js

33 ms

code.js

code.js

749 ms

chatra.js

chatra.js

82 ms

i2.jpg

i2.jpg

800 ms

i3.jpg

i3.jpg

819 ms

i4.jpg

i4.jpg

826 ms

i6.jpg

i6.jpg

827 ms

BebasNeue-Bold.ttf

BebasNeue-Bold.ttf

1248 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

26 ms

fastbutton

fastbutton

39 ms

postmessageRelay

postmessageRelay

43 ms

chat.chatra.io

chat.chatra.io

13 ms

0f4b36301fb51872f1b179a76dbf2e28b4b4a818.css

0f4b36301fb51872f1b179a76dbf2e28b4b4a818.css

36 ms

meteor_runtime_config.js

meteor_runtime_config.js

17 ms

da64b544ef77c8a36b93ed650846594943696be1.js

da64b544ef77c8a36b93ed650846594943696be1.js

85 ms

i5.jpg

i5.jpg

822 ms

i1.png

i1.png

824 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

27 ms

rpc:shindig_random.js

rpc:shindig_random.js

12 ms

developers.google.com

developers.google.com

335 ms

i2.png

i2.png

839 ms

i3.png

i3.png

833 ms

i4.png

i4.png

833 ms

logo_foot.png

logo_foot.png

933 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

pay.png

pay.png

827 ms

vk.png

vk.png

848 ms

tw.png

tw.png

843 ms

f.png

f.png

834 ms

i.png

i.png

933 ms

yt.png

yt.png

937 ms

home_abs_bg.png

home_abs_bg.png

853 ms

head_phone.png

head_phone.png

857 ms

i7.jpg

i7.jpg

983 ms

super_shadow.png

super_shadow.png

932 ms

news_one.png

news_one.png

936 ms

callme_zag_span.png

callme_zag_span.png

961 ms

callme_zag_vop.png

callme_zag_vop.png

864 ms

services_zag.png

services_zag.png

866 ms

ico_a_v1.png

ico_a_v1.png

940 ms

591 ms

home_txt_bg.jpg

home_txt_bg.jpg

1038 ms

footer.png

footer.png

931 ms

icon_top.png

icon_top.png

933 ms

gallery-prev.png

gallery-prev.png

867 ms

gallery-next.png

gallery-next.png

867 ms

sync-loader.js

sync-loader.js

947 ms

counter

counter

125 ms

dyn-goal-config.js

dyn-goal-config.js

249 ms

b24f513706454b8a88be.css

b24f513706454b8a88be.css

380 ms

199 ms

e690f6dd33c8870d6972.yandex.ru.js

e690f6dd33c8870d6972.yandex.ru.js

600 ms

2343feb4aaeecff3cdc3.yandex.ru.js

2343feb4aaeecff3cdc3.yandex.ru.js

663 ms

number

number

682 ms

watch.js

watch.js

8 ms

full-72b452cea15198cd837dc4cc43e4d4606d6bf516.js

full-72b452cea15198cd837dc4cc43e4d4606d6bf516.js

725 ms

logo-web-ru-80x40.svg

logo-web-ru-80x40.svg

576 ms

Accessibility Review

elocks.ru accessibility score

69

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

elocks.ru best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

elocks.ru SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    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.

Social Sharing Optimization

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: