Tools & Wizards About Us
ochki.net screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ochki.net

Ochki.net: узнайте всё об очках и контактных линзах!

Page Load Speed

5.8 sec in total

First Response

345 ms

Resources Loaded

4.7 sec

Page Rendered

769 ms

ochki.net screenshot

About Website

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

OCHKI.net – портал для всех, кто интересуется контактными линзами и очками. Это надёжный источник информации обо всём, что связано с очковой и контактной коррекцией зрения, а также возможность первым ...

Visit ochki.net

Key Findings

We analyzed Ochki.net page load time and found that the first response time was 345 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

ochki.net performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value7,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.552

13/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

ochki.net

345 ms

www.ochki.net

1010 ms

js

51 ms

css

37 ms

750 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 76% of them (70 requests) were addressed to the original Ochki.net, 5% (5 requests) were made to Api-maps.yandex.ru and 3% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (68%)

Content Size

2.8 MB

After Optimization

894.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ochki.net main page is 2.8 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. 65% of websites need less resources to load. HTML takes 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 1.8 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 85.1 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 1.8 MB or 95% of the original size.

Image Optimization

-5%

Potential reduce by 15.6 kB

  • Original 296.7 kB
  • After minification 281.1 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. Ochki images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 103.9 kB

  • Original 565.3 kB
  • After minification 565.3 kB
  • After compression 461.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 103.9 kB or 18% of the original size.

CSS Optimization

-31%

Potential reduce by 30.7 kB

  • Original 97.6 kB
  • After minification 97.6 kB
  • After compression 66.9 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. Ochki.net needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (43%)

Requests Now

80

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ochki.net

ochki.net

345 ms

www.ochki.net

www.ochki.net

1010 ms

js

js

51 ms

css

css

37 ms

750 ms

core.css

core.css

227 ms

bootstrap.css

bootstrap.css

432 ms

font-awesome.css

font-awesome.css

330 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

329 ms

owl.carousel.css

owl.carousel.css

327 ms

jquery.fancybox.css

jquery.fancybox.css

328 ms

select2.min.css

select2.min.css

328 ms

datepicker.min.css

datepicker.min.css

428 ms

main.css

main.css

532 ms

style.css

style.css

428 ms

core.js

core.js

736 ms

jquery-3.4.1.js

jquery-3.4.1.js

737 ms

jquery.lazy.min.js

jquery.lazy.min.js

528 ms

owl.carousel.js

owl.carousel.js

531 ms

jquery.fancybox.js

jquery.fancybox.js

633 ms

svg4everybody.js

svg4everybody.js

628 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

634 ms

blazy.min.js

blazy.min.js

632 ms

select2.min.js

select2.min.js

836 ms

datepicker.min.js

datepicker.min.js

736 ms

datepicker.init.js

datepicker.init.js

734 ms

form-validate.js

form-validate.js

734 ms

ac.js

ac.js

844 ms

main.js

main.js

845 ms

script.js

script.js

844 ms

context.js

context.js

1061 ms

rttr.js

rttr.js

843 ms

js

js

68 ms

analytics.js

analytics.js

26 ms

collect

collect

19 ms

collect

collect

68 ms

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

1857 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

92 ms

ba.js

ba.js

326 ms

398c7a6fdf4d81ce6db7d37d594e5cf6.jpg

398c7a6fdf4d81ce6db7d37d594e5cf6.jpg

243 ms

sprite.symbol.svg

sprite.symbol.svg

205 ms

logo.png

logo.png

203 ms

4a77a7065675c8a17dbc77c9918d9f9d.jpg

4a77a7065675c8a17dbc77c9918d9f9d.jpg

242 ms

b2059d53e9ddee21eb5db52c93095ff7.gif

b2059d53e9ddee21eb5db52c93095ff7.gif

645 ms

065ee3c7ebd2c5d7eaa570334777087b.gif

065ee3c7ebd2c5d7eaa570334777087b.gif

544 ms

056fa7d9c0d56598457260803cf59ee9.gif

056fa7d9c0d56598457260803cf59ee9.gif

648 ms

6c8cd1babb86d9c588bc0ded288a47b9.jpg

6c8cd1babb86d9c588bc0ded288a47b9.jpg

242 ms

c0906d797cc19d16a7473ab12caeca99.jpg

c0906d797cc19d16a7473ab12caeca99.jpg

341 ms

dd55c2e228e7feb32bdd6cb405e72787.jpg

dd55c2e228e7feb32bdd6cb405e72787.jpg

341 ms

7fce8d000a1b804760543c3a2f311734.jpg

7fce8d000a1b804760543c3a2f311734.jpg

341 ms

1c89052e6458f9acca72182b5733bb23.jpg

1c89052e6458f9acca72182b5733bb23.jpg

443 ms

fdec14e87c78243a0398cb6235a0976f.jpg

fdec14e87c78243a0398cb6235a0976f.jpg

444 ms

3899886f9ec5e51c4bf8813e5f41e872.jpg

3899886f9ec5e51c4bf8813e5f41e872.jpg

442 ms

05d7c4331c2abd42666e377c2ed45ad1.jpg

05d7c4331c2abd42666e377c2ed45ad1.jpg

544 ms

ac15e2e0419fdb0c7ea17995ab98e9d2.jpg

ac15e2e0419fdb0c7ea17995ab98e9d2.jpg

543 ms

e223e39e4c7627bfbf7ad905704860ed.jpg

e223e39e4c7627bfbf7ad905704860ed.jpg

545 ms

cc66def6ed31cffc2b533d2b9340f832.jpg

cc66def6ed31cffc2b533d2b9340f832.jpg

644 ms

ee6868274269977d86a2ac96ab2cb3b6.jpg

ee6868274269977d86a2ac96ab2cb3b6.jpg

645 ms

1fabaebfb2403b85c93ee78bff049983.jpg

1fabaebfb2403b85c93ee78bff049983.jpg

645 ms

2733a17df4a41ab4212ec56e1157d0b2.jpg

2733a17df4a41ab4212ec56e1157d0b2.jpg

646 ms

a2caa48189e77817ad56a44cdb21dfd4.jpg

a2caa48189e77817ad56a44cdb21dfd4.jpg

744 ms

9db88a69c8d5609d4b093e00fea78499.jpg

9db88a69c8d5609d4b093e00fea78499.jpg

745 ms

f0ade1fc212272a9fbeb8e83fb06019f.jpg

f0ade1fc212272a9fbeb8e83fb06019f.jpg

746 ms

733902871b381ac8d4eba472a4a0a511.jpg

733902871b381ac8d4eba472a4a0a511.jpg

747 ms

e91921c976bbebf7f8f9a35fa4470558.jpg

e91921c976bbebf7f8f9a35fa4470558.jpg

746 ms

2aa30c0ccf9b57a22eab7b702ebd02a2.jpg

2aa30c0ccf9b57a22eab7b702ebd02a2.jpg

747 ms

0052c757a40a47ae89cfb495065b2cd6.jpg

0052c757a40a47ae89cfb495065b2cd6.jpg

844 ms

f0946dbd53c9b5dd9ddcc80127bd754c.jpg

f0946dbd53c9b5dd9ddcc80127bd754c.jpg

845 ms

7a5d146f66823c2b188c788656107820.jpg

7a5d146f66823c2b188c788656107820.jpg

846 ms

452ad1ccfb2be0d5c476c7c5d186f5e7.jpg

452ad1ccfb2be0d5c476c7c5d186f5e7.jpg

847 ms

4901616538441341877f54b3a5bda881.jpg

4901616538441341877f54b3a5bda881.jpg

847 ms

926e4828cf682aea3fcfc5dee1df7269.jpg

926e4828cf682aea3fcfc5dee1df7269.jpg

848 ms

bb4e8173f3a942ca8af1c3dd0e182e70.jpg

bb4e8173f3a942ca8af1c3dd0e182e70.jpg

945 ms

e4b5a73fb9e644cd925e46597c13d338.gif

e4b5a73fb9e644cd925e46597c13d338.gif

1131 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

172 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

173 ms

tag.js

tag.js

845 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

913 ms

Oswald-Bold.woff

Oswald-Bold.woff

758 ms

Oswald-Regular.woff

Oswald-Regular.woff

712 ms

ajax_counter.php

ajax_counter.php

989 ms

ragget-bottom.jpg

ragget-bottom.jpg

723 ms

bx_stat

bx_stat

192 ms

advert.gif

advert.gif

599 ms

sync_cookie_image_decide

sync_cookie_image_decide

200 ms

grab.cur

grab.cur

126 ms

grabbing.cur

grabbing.cur

158 ms

help.cur

help.cur

282 ms

zoom_in.cur

zoom_in.cur

379 ms

1

1

127 ms

202495854ca8e8b358a8f76a0fc9ac32.jpg

202495854ca8e8b358a8f76a0fc9ac32.jpg

205 ms

6e2a53fd237258ab5e6bc8046e65ce39.jpg

6e2a53fd237258ab5e6bc8046e65ce39.jpg

103 ms

Accessibility Review

ochki.net accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

ochki.net best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ochki.net SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ochki.net 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 Ochki.net 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

ochki.net

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