Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

alteza.by

Купить натяжные потолки в Минске, Продажа, монтаж, установка натяжных потолков

Page Load Speed

5.9 sec in total

First Response

485 ms

Resources Loaded

5 sec

Page Rendered

418 ms

About Website

Visit alteza.by now to see the best up-to-date Alteza content for Belarus and also check out these interesting facts you probably never knew about alteza.by

Производство, продажа, монтаж, установка натяжных потолков в Минске. Компания ALTEZA — крупнейший производитель потолков в Беларуси

Visit alteza.by

Key Findings

We analyzed Alteza.by page load time and found that the first response time was 485 ms and then it took 5.4 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

alteza.by performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value5,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.881

0/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

alteza.by

485 ms

alteza.by

879 ms

font-awesome.min.css

145 ms

jquery-2.2.3.min.js

291 ms

index.js

390 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 85% of them (99 requests) were addressed to the original Alteza.by, 4% (5 requests) were made to Api.venyoo.ru and 3% (3 requests) were made to 133921.selcdn.ru. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Alteza.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.4 kB (4%)

Content Size

8.0 MB

After Optimization

7.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alteza.by main page is 8.0 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. 70% of websites need less resources to load. Images take 7.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 240.5 kB

  • Original 274.4 kB
  • After minification 216.4 kB
  • After compression 33.9 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 58.0 kB, which is 21% 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 240.5 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 49.6 kB

  • Original 7.3 MB
  • After minification 7.2 MB

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. Alteza images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 19.6 kB

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

CSS Optimization

-22%

Potential reduce by 8.6 kB

  • Original 39.3 kB
  • After minification 39.2 kB
  • After compression 30.7 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. Alteza.by needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (44%)

Requests Now

107

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

alteza.by accessibility score

68

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

alteza.by best practices score

75

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

SEO Factors

alteza.by SEO score

84

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 Alteza.by 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 Alteza.by 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 Alteza. 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: