Tools & Wizards About Us
weg.ru screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

weg.ru

Выставки «Красивые дома. Российский архитектурный салон», «Деревянный Дом», «Салон Каминов», «Салон интерьеров», «Aqua Salon: Wellness & SPA. Бассейны...

Page Load Speed

11.6 sec in total

First Response

1.5 sec

Resources Loaded

9.8 sec

Page Rendered

255 ms

weg.ru screenshot

About Website

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

Организация архитектурных, строительных и интерьерных выставок — «Красивые дома. Российский архитектурный салон», «Деревянный Дом», «Салон Каминов», «Салон интерьеров», «Aqua Salon: Wellness & SPA. Ба...

Visit weg.ru

Key Findings

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

Performance Metrics

weg.ru performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

weg.ru

1473 ms

style.css

440 ms

style_exhibitions.css

589 ms

plusone.js

271 ms

highslide.min.js

782 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 84% of them (62 requests) were addressed to the original Weg.ru, 8% (6 requests) were made to Openstat.net and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Weg.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.4 kB (33%)

Content Size

672.0 kB

After Optimization

451.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weg.ru main page is 672.0 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. 25% of websites need less resources to load. Images take 421.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 40.6 kB

  • Original 48.9 kB
  • After minification 47.7 kB
  • After compression 8.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 40.6 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 32.3 kB

  • Original 421.0 kB
  • After minification 388.7 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. Weg images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 105.8 kB

  • Original 153.1 kB
  • After minification 139.7 kB
  • After compression 47.3 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 105.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 41.7 kB

  • Original 49.1 kB
  • After minification 36.4 kB
  • After compression 7.4 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. Weg.ru needs all CSS files to be minified and compressed as it can save up to 41.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (46%)

Requests Now

70

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weg.ru

weg.ru

1473 ms

style.css

style.css

440 ms

style_exhibitions.css

style_exhibitions.css

589 ms

plusone.js

plusone.js

271 ms

highslide.min.js

highslide.min.js

782 ms

highslide.css

highslide.css

586 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

1066 ms

jMyCarousel.css

jMyCarousel.css

600 ms

jMyCarousel.js

jMyCarousel.js

749 ms

watch.js

watch.js

1 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

52 ms

livejournal2.png

livejournal2.png

1029 ms

sepDotted.gif

sepDotted.gif

372 ms

topMenuBgBg.gif

topMenuBgBg.gif

465 ms

emagbanner-w.png

emagbanner-w.png

7016 ms

portal230.jpg

portal230.jpg

556 ms

topMenuRightBg.gif

topMenuRightBg.gif

370 ms

topMenuSeparator.gif

topMenuSeparator.gif

533 ms

style.css

style.css

1667 ms

topMenuCirc-yellow.gif

topMenuCirc-yellow.gif

1136 ms

icon-mail.gif

icon-mail.gif

1276 ms

icon-sitemap.gif

icon-sitemap.gif

881 ms

sepRight.gif

sepRight.gif

883 ms

headerBot2bg.gif

headerBot2bg.gif

1027 ms

headerTopBg.gif

headerTopBg.gif

1028 ms

mainLogo.gif

mainLogo.gif

1159 ms

headerBg.gif

headerBg.gif

1206 ms

kremlinHeaderBot.jpg

kremlinHeaderBot.jpg

1687 ms

w1.jpg

w1.jpg

1291 ms

w10.jpg

w10.jpg

1367 ms

w11.jpg

w11.jpg

1925 ms

w12.jpg

w12.jpg

1421 ms

w13.jpg

w13.jpg

1529 ms

w14.jpg

w14.jpg

1552 ms

w15.jpg

w15.jpg

1663 ms

w16.jpg

w16.jpg

1690 ms

w17.jpg

w17.jpg

1927 ms

w18.jpg

w18.jpg

1798 ms

w2.jpg

w2.jpg

1938 ms

w3.jpg

w3.jpg

1821 ms

w4.jpg

w4.jpg

1931 ms

w5.jpg

w5.jpg

1952 ms

w6.jpg

w6.jpg

2191 ms

w7.jpg

w7.jpg

2083 ms

w8.jpg

w8.jpg

2086 ms

w9.jpg

w9.jpg

2099 ms

middleTopBg.gif

middleTopBg.gif

2107 ms

facebook.png

facebook.png

1144 ms

googleplusicon.png

googleplusicon.png

1279 ms

vkontakte.png

vkontakte.png

1407 ms

hit

hit

1391 ms

krasivye-doma.gif

krasivye-doma.gif

2043 ms

cnt.js

cnt.js

1379 ms

kdd-logo.gif

kdd-logo.gif

1861 ms

isalon-logo.gif

isalon-logo.gif

1871 ms

derevyannyj-dom.gif

derevyannyj-dom.gif

1787 ms

salon-kaminov.gif

salon-kaminov.gif

1803 ms

aqua-salon.gif

aqua-salon.gif

1819 ms

dom-i-sad.gif

dom-i-sad.gif

1494 ms

kremlinLeftSidebarBg.jpg

kremlinLeftSidebarBg.jpg

1497 ms

rightSidebarTopBg.gif

rightSidebarTopBg.gif

1356 ms

search-btn.gif

search-btn.gif

1463 ms

right.png

right.png

1386 ms

left.png

left.png

1361 ms

2154951.js

2154951.js

130 ms

hit

hit

163 ms

digits

digits

128 ms

cnt

cnt

251 ms

f.gif

f.gif

160 ms

t9tWw3zzRGajHSPxN1et1A

t9tWw3zzRGajHSPxN1et1A

135 ms

drop-shadow.png

drop-shadow.png

136 ms

zoomout.cur

zoomout.cur

141 ms

loader.white.gif

loader.white.gif

137 ms

cnt

cnt

409 ms

Accessibility Review

weg.ru accessibility score

66

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

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.

Best Practices

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

weg.ru SEO score

99

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

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

weg.ru

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