Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

happylook.ru

Сеть салонов оптики «Счастливый взгляд» – интернет-магазин контактных линз, очков, оправ и аксессуаров

Page Load Speed

4.5 sec in total

First Response

722 ms

Resources Loaded

3.6 sec

Page Rendered

182 ms

happylook.ru screenshot

About Website

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

Услуги сети салонов оптики «Счастливый взгляд» . Услуги офтальмолога: проверка зрения, подбор коррекции и лечение. Изготовление и ремонт очков. Изготовление линз любой сложности. Бонусы для покупателе...

Visit happylook.ru

Key Findings

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

Performance Metrics

happylook.ru performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value6,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

happylook.ru

722 ms

common.css

126 ms

jquery.js

376 ms

prefixfree.min.js

255 ms

common.js

256 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 89% of them (80 requests) were addressed to the original Happylook.ru, 3% (3 requests) were made to Mc.yandex.ru and 3% (3 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Happylook.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 319.6 kB (18%)

Content Size

1.7 MB

After Optimization

1.4 MB

In fact, the total size of Happylook.ru main page is 1.7 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 57.2 kB

  • Original 73.1 kB
  • After minification 70.8 kB
  • After compression 16.0 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 57.2 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 96.3 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. Happylook images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 137.7 kB

  • Original 245.2 kB
  • After minification 235.0 kB
  • After compression 107.5 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 137.7 kB or 56% of the original size.

CSS Optimization

-78%

Potential reduce by 28.5 kB

  • Original 36.7 kB
  • After minification 33.4 kB
  • After compression 8.2 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. Happylook.ru needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (24%)

Requests Now

87

After Optimization

66

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Happylook. 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 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

happylook.ru accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<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

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

happylook.ru SEO score

86

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

    N/A

  • Encoding

    UTF-8

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

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