Tools & Wizards About Us
062.ru screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

062.ru

Доска объявлений строительные услуги

Page Load Speed

13.8 sec in total

First Response

402 ms

Resources Loaded

13.2 sec

Page Rendered

256 ms

062.ru screenshot

About Website

Welcome to 062.ru homepage info - get ready to check 062 best content for Russia right away, or after learning these important things about 062.ru

Доска объявлений строительные услуги

Visit 062.ru

Key Findings

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

Performance Metrics

062.ru performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

www.062.ru

402 ms

css.css

117 ms

nanoscroller.css

2390 ms

css

38 ms

jquery.min.js

2619 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 93% of them (107 requests) were addressed to the original 062.ru, 2% (2 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain 062.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 236.6 kB (56%)

Content Size

423.8 kB

After Optimization

187.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 38.2 kB

  • Original 48.1 kB
  • After minification 45.2 kB
  • After compression 9.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. 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.2 kB or 79% of the original size.

Image Optimization

-32%

Potential reduce by 60.8 kB

  • Original 187.4 kB
  • After minification 126.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. Obviously, 062 needs image optimization as it can save up to 60.8 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 120.6 kB

  • Original 167.7 kB
  • After minification 145.1 kB
  • After compression 47.1 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 120.6 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 17.0 kB

  • Original 20.6 kB
  • After minification 15.4 kB
  • After compression 3.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. 062.ru needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (38%)

Requests Now

109

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 062. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.062.ru

www.062.ru

402 ms

css.css

css.css

117 ms

nanoscroller.css

nanoscroller.css

2390 ms

css

css

38 ms

jquery.min.js

jquery.min.js

2619 ms

jquery.nanoscroller.min.js

jquery.nanoscroller.min.js

2524 ms

main.js

main.js

2392 ms

template.js

template.js

2411 ms

menu_raduga.css

menu_raduga.css

2392 ms

wz_tooltip.js

wz_tooltip.js

2705 ms

jquery.autocomplete.pack.js

jquery.autocomplete.pack.js

2596 ms

script.js

script.js

2598 ms

jquery.autocomplete.css

jquery.autocomplete.css

2599 ms

main.css

main.css

2645 ms

jquery.mousewheel-3.0.2.pack.js

jquery.mousewheel-3.0.2.pack.js

2740 ms

jquery.fancybox-1.3.1.js

jquery.fancybox-1.3.1.js

2881 ms

jquery.fancybox-1.3.1.css

jquery.fancybox-1.3.1.css

2754 ms

fff.jpg&text=390x100+px

fff.jpg&text=390x100+px

74 ms

logo.jpg

logo.jpg

126 ms

plus16.jpg

plus16.jpg

134 ms

01.png

01.png

193 ms

02.png

02.png

246 ms

03.png

03.png

269 ms

04.png

04.png

247 ms

05.png

05.png

250 ms

06.png

06.png

311 ms

07.png

07.png

368 ms

08.png

08.png

363 ms

09.png

09.png

366 ms

10.png

10.png

383 ms

11.png

11.png

385 ms

12.png

12.png

426 ms

13.png

13.png

482 ms

14.png

14.png

483 ms

15.png

15.png

492 ms

16.png

16.png

520 ms

17.png

17.png

519 ms

18.png

18.png

543 ms

19.png

19.png

2980 ms

20.png

20.png

3014 ms

21.png

21.png

3015 ms

01.png

01.png

2800 ms

02.png

02.png

2817 ms

03.png

03.png

2802 ms

04.png

04.png

3032 ms

05.png

05.png

3033 ms

06.png

06.png

3046 ms

07.png

07.png

3098 ms

watch.js

watch.js

1 ms

08.png

08.png

3142 ms

09.png

09.png

3150 ms

10.png

10.png

3094 ms

KFOmCnqEu92Fr1Mu5mxP.ttf

KFOmCnqEu92Fr1Mu5mxP.ttf

26 ms

KFOlCnqEu92Fr1MmWUlfABc9.ttf

KFOlCnqEu92Fr1MmWUlfABc9.ttf

30 ms

11.png

11.png

3068 ms

12.png

12.png

3076 ms

13.png

13.png

3099 ms

14.png

14.png

3130 ms

15.png

15.png

3104 ms

16.png

16.png

3060 ms

17.png

17.png

3049 ms

18.png

18.png

3085 ms

index.php

index.php

123 ms

19.png

19.png

3074 ms

hit

hit

244 ms

20.png

20.png

3083 ms

21.png

21.png

3103 ms

22.png

22.png

3057 ms

23.png

23.png

3070 ms

24.png

24.png

3100 ms

25.png

25.png

3078 ms

26.png

26.png

3115 ms

27.png

27.png

3106 ms

28.png

28.png

3060 ms

29.png

29.png

5294 ms

30.png

30.png

5328 ms

31.png

31.png

5416 ms

32.png

32.png

5257 ms

hit

hit

510 ms

33.png

33.png

5425 ms

50.png

50.png

3047 ms

34.png

34.png

3204 ms

35.png

35.png

3187 ms

36.png

36.png

3024 ms

37.png

37.png

3016 ms

38.png

38.png

3064 ms

39.png

39.png

3072 ms

40.png

40.png

3133 ms

41.png

41.png

3132 ms

42.png

42.png

3083 ms

43.png

43.png

3040 ms

44.png

44.png

3048 ms

45.png

45.png

3048 ms

46.png

46.png

3116 ms

47.png

47.png

3097 ms

48.png

48.png

3090 ms

all.png

all.png

3048 ms

yarmarka.png

yarmarka.png

3069 ms

975.png

975.png

3067 ms

ya62.png

ya62.png

3106 ms

prosvadbu.png

prosvadbu.png

3087 ms

brigadir.png

brigadir.png

3096 ms

med62.png

med62.png

3065 ms

1569.jpg

1569.jpg

3104 ms

1553.jpg

1553.jpg

3118 ms

1533.jpg

1533.jpg

3116 ms

facebook.png

facebook.png

3076 ms

liveinternet.png

liveinternet.png

5443 ms

livejournal.png

livejournal.png

5511 ms

twitter.png

twitter.png

5445 ms

vk.png

vk.png

5238 ms

rss.png

rss.png

3201 ms

body.png

body.png

3065 ms

lupa.png

lupa.png

3243 ms

totop000.png

totop000.png

3225 ms

Accessibility Review

062.ru accessibility score

71

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

062.ru best practices score

75

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

SEO Factors

062.ru SEO score

92

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

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

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 062.ru can be misinterpreted by Google and other search engines. Our service has detected that English 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 062.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.

Social Sharing Optimization

062.ru

Open Graph description is not detected on the main page of 062. 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: