Report Summary

  • 19

    Performance

    Renders faster than
    35% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

dryclean.ru

Химчистка ДИАНА в Москве | Цены на услуги стирки и химчистки

Page Load Speed

8.5 sec in total

First Response

455 ms

Resources Loaded

7.4 sec

Page Rendered

637 ms

dryclean.ru screenshot

About Website

Visit dryclean.ru now to see the best up-to-date Dryclean content for Russia and also check out these interesting facts you probably never knew about dryclean.ru

Химчистка "Диана" предлагаем свои услуги по уборке, чистке, химчистке любых видов одежды, мебели, помещений и аксессуаров по самой выгодной цене. ☎️Наш номер телефона в Москве: 8 (800) 222-82-26

Visit dryclean.ru

Key Findings

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

Performance Metrics

dryclean.ru performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value3,320 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.236

53/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

dryclean.ru

455 ms

dryclean.ru

2984 ms

page_a49525ebb4cebe1c85bfaf9b1d736594_v1.css

378 ms

template_3c05392e663c2fdf1a04d1b059a5b40c_v1.css

514 ms

pre2.gif

776 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 56% of them (43 requests) were addressed to the original Dryclean.ru, 6% (5 requests) were made to Api-maps.yandex.ru and 5% (4 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Dryclean.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 850.5 kB (52%)

Content Size

1.6 MB

After Optimization

789.7 kB

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

HTML Optimization

-88%

Potential reduce by 727.9 kB

  • Original 828.1 kB
  • After minification 775.3 kB
  • After compression 100.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 727.9 kB or 88% of the original size.

Image Optimization

-11%

Potential reduce by 7.1 kB

  • Original 61.5 kB
  • After minification 54.5 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, Dryclean needs image optimization as it can save up to 7.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 99.7 kB

  • Original 642.7 kB
  • After minification 642.7 kB
  • After compression 542.9 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 99.7 kB or 16% of the original size.

CSS Optimization

-15%

Potential reduce by 15.8 kB

  • Original 107.9 kB
  • After minification 107.9 kB
  • After compression 92.1 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. Dryclean.ru needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (53%)

Requests Now

62

After Optimization

29

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

Accessibility Review

dryclean.ru accessibility score

65

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

dryclean.ru best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

SEO Factors

dryclean.ru SEO score

83

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

High

Tap targets are not sized appropriately

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