Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

alveus.ru

Купить технику для кухни в Москве - интернет магазин Бонави

Page Load Speed

9.5 sec in total

First Response

762 ms

Resources Loaded

8.6 sec

Page Rendered

172 ms

alveus.ru screenshot

About Website

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

Belongs to the major European suppliers of kitchen sinks, Cookers, Mixer taps, …

Visit alveus.ru

Key Findings

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

alveus.ru performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value400 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.354

31/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

alveus.ru

762 ms

www.alveus.ru

1196 ms

553 ms

ede_site.css

393 ms

ede_site_ru_nrm_52.css

275 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 97% of them (33 requests) were addressed to the original Alveus.ru, 3% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Stats.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 600.5 kB (61%)

Content Size

979.7 kB

After Optimization

379.3 kB

In fact, the total size of Alveus.ru main page is 979.7 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. 45% of websites need less resources to load. Javascripts take 381.6 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 87.1 kB

  • Original 98.4 kB
  • After minification 93.1 kB
  • After compression 11.3 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 87.1 kB or 89% of the original size.

Image Optimization

-28%

Potential reduce by 93.7 kB

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

JavaScript Optimization

-71%

Potential reduce by 269.2 kB

  • Original 381.6 kB
  • After minification 324.2 kB
  • After compression 112.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 269.2 kB or 71% of the original size.

CSS Optimization

-89%

Potential reduce by 150.5 kB

  • Original 169.6 kB
  • After minification 128.1 kB
  • After compression 19.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. Alveus.ru needs all CSS files to be minified and compressed as it can save up to 150.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

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

Accessibility Review

alveus.ru accessibility score

46

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

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

[id] attributes on active, focusable elements are not unique

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

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

alveus.ru best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

    RU

  • Encoding

    UTF-8

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