Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

qwazer.ru

Ремонт стиральных машин

Page Load Speed

7.8 sec in total

First Response

1.5 sec

Resources Loaded

3.5 sec

Page Rendered

2.8 sec

qwazer.ru screenshot

About Website

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

Visit qwazer.ru

Key Findings

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

Performance Metrics

qwazer.ru performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

qwazer.ru

1547 ms

style.css

198 ms

logo.gif

195 ms

home.gif

204 ms

mail.gif

205 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 88% of them (21 requests) were addressed to the original Qwazer.ru, 8% (2 requests) were made to Counter.yadro.ru and 4% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Qwazer.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.6 kB (57%)

Content Size

369.1 kB

After Optimization

157.5 kB

In fact, the total size of Qwazer.ru main page is 369.1 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. Only 5% of websites need less resources to load. HTML takes 242.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 206.7 kB

  • Original 242.4 kB
  • After minification 239.0 kB
  • After compression 35.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 206.7 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 2.4 kB

  • Original 123.2 kB
  • After minification 120.8 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. Qwazer images are well optimized though.

CSS Optimization

-72%

Potential reduce by 2.5 kB

  • Original 3.4 kB
  • After minification 2.9 kB
  • After compression 973 B

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. Qwazer.ru needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 72% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qwazer. According to our analytics all requests are already optimized.

Accessibility Review

qwazer.ru accessibility score

88

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

qwazer.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

qwazer.ru SEO score

100

Search Engine Optimization Advices

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 Qwazer.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 Qwazer.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 Qwazer. 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: