Tools & Wizards About Us
divanvdom.ru screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

divanvdom.ru

⭐Интернет-магазин ДИВАН В ДОМ⭐ - мебель от производителя в Москве

Page Load Speed

5.9 sec in total

First Response

535 ms

Resources Loaded

5 sec

Page Rendered

325 ms

divanvdom.ru screenshot

About Website

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

✅ Интернет-магазин Диван в Дом - купить недорого диваны, кровати, корпусную мебель российских производителей с доставкой по Москве и области.

Visit divanvdom.ru

Key Findings

We analyzed Divanvdom.ru page load time and found that the first response time was 535 ms and then it took 5.3 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

divanvdom.ru performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

divanvdom.ru

535 ms

divanvdom.ru

499 ms

www.divanvdom.ru

828 ms

js

85 ms

ui.design-tokens.min.css

132 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 80% of them (68 requests) were addressed to the original Divanvdom.ru, 4% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Divanvdom.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 744.0 kB (43%)

Content Size

1.7 MB

After Optimization

992.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Divanvdom.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. 65% of websites need less resources to load. Javascripts take 874.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 62.1 kB

  • Original 77.7 kB
  • After minification 64.3 kB
  • After compression 15.5 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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 62.1 kB or 80% of the original size.

Image Optimization

-80%

Potential reduce by 597.0 kB

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

JavaScript Optimization

-9%

Potential reduce by 77.8 kB

  • Original 874.3 kB
  • After minification 874.3 kB
  • After compression 796.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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 7.0 kB

  • Original 39.5 kB
  • After minification 38.0 kB
  • After compression 32.5 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. Divanvdom.ru needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (35%)

Requests Now

72

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

divanvdom.ru

divanvdom.ru

535 ms

divanvdom.ru

divanvdom.ru

499 ms

www.divanvdom.ru

www.divanvdom.ru

828 ms

js

js

85 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

132 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

262 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

365 ms

page_4bac2c5a0b930b6a0fabc0a01ed93c8e_v1.css

page_4bac2c5a0b930b6a0fabc0a01ed93c8e_v1.css

372 ms

template_bad0d1abbce0ed5a711a1b8567a520ba_v1.css

template_bad0d1abbce0ed5a711a1b8567a520ba_v1.css

520 ms

core.min.js

core.min.js

651 ms

kernel_main_v1.js

kernel_main_v1.js

532 ms

dexie3.bundle.min.js

dexie3.bundle.min.js

533 ms

core_ls.min.js

core_ls.min.js

485 ms

core_frame_cache.min.js

core_frame_cache.min.js

491 ms

protobuf.min.js

protobuf.min.js

727 ms

model.min.js

model.min.js

612 ms

rest.client.min.js

rest.client.min.js

660 ms

pull.client.min.js

pull.client.min.js

661 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

663 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

32 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

853 ms

css2

css2

49 ms

template_7f552a5f9a8a8b4db0748c423a1f8d73_v1.js

template_7f552a5f9a8a8b4db0748c423a1f8d73_v1.js

1037 ms

zMsHDtwfjK

zMsHDtwfjK

409 ms

ba.js

ba.js

314 ms

fav2_gray.png

fav2_gray.png

204 ms

vhod.png

vhod.png

202 ms

logo.png

logo.png

202 ms

phones.png

phones.png

127 ms

warranty.png

warranty.png

125 ms

search.png

search.png

201 ms

cartt.png

cartt.png

245 ms

podp.png

podp.png

245 ms

btn.png

btn.png

297 ms

placeholder.png

placeholder.png

286 ms

pr1.png

pr1.png

287 ms

pr2.png

pr2.png

297 ms

pr3.png

pr3.png

364 ms

pr4.png

pr4.png

364 ms

str.png

str.png

414 ms

ca1.png

ca1.png

415 ms

ca2.png

ca2.png

546 ms

ca3.png

ca3.png

548 ms

ca4.png

ca4.png

724 ms

ca5.png

ca5.png

605 ms

ca6.png

ca6.png

544 ms

ca7.png

ca7.png

544 ms

ca8.png

ca8.png

673 ms

ca9.png

ca9.png

802 ms

ca10.png

ca10.png

675 ms

bf89fa3b4cae43aa3070049cda8c7386.jpg

bf89fa3b4cae43aa3070049cda8c7386.jpg

678 ms

favv.png

favv.png

724 ms

7abbed2a2025de877b40d895aa9c46f8.jpg

7abbed2a2025de877b40d895aa9c46f8.jpg

803 ms

e6d459c93dd419918f6c8e520f101158.jpg

e6d459c93dd419918f6c8e520f101158.jpg

805 ms

ee363ecd2283123619e6b558d41e74c1.jpg

ee363ecd2283123619e6b558d41e74c1.jpg

808 ms

810b4fa7fb2e84f97fbc683223e8fc9d.jpg

810b4fa7fb2e84f97fbc683223e8fc9d.jpg

843 ms

logo2.png

logo2.png

845 ms

captcha.php

captcha.php

945 ms

opensans-regular.woff

opensans-regular.woff

824 ms

opensans-light.woff

opensans-light.woff

956 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

88 ms

opensans-semibold.woff

opensans-semibold.woff

963 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

101 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

125 ms

zMsHDtwfjK

zMsHDtwfjK

204 ms

opensans-bold.woff

opensans-bold.woff

973 ms

tag.js

tag.js

869 ms

po1.png

po1.png

819 ms

analytics.js

analytics.js

63 ms

butt.png

butt.png

867 ms

po2.png

po2.png

877 ms

btnn.png

btnn.png

898 ms

seotxt.png

seotxt.png

995 ms

collect

collect

14 ms

social.png

social.png

956 ms

top.png

top.png

955 ms

js

js

50 ms

bx_stat

bx_stat

187 ms

bx_loader.gif

bx_loader.gif

918 ms

strel2.png

strel2.png

916 ms

ajax-loader.gif

ajax-loader.gif

916 ms

zMsHDtwfjK

zMsHDtwfjK

648 ms

advert.gif

advert.gif

679 ms

145 ms

bundle_ru_RU.js

bundle_ru_RU.js

223 ms

Accessibility Review

divanvdom.ru accessibility score

88

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-hidden="true"] elements contain focusable descendents

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

divanvdom.ru best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

divanvdom.ru SEO score

82

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

    RU

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Divanvdom.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 Divanvdom.ru main page’s claimed encoding is . 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

divanvdom.ru

Open Graph data is detected on the main page of Divanvdom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: