Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

intag.by

Купить кабель в Минске, кабельно-проводниковая продукция | ООО «ИнтАГ»

Page Load Speed

5.1 sec in total

First Response

479 ms

Resources Loaded

4.4 sec

Page Rendered

243 ms

intag.by screenshot

About Website

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

Ищете провода и кабели в Минске? ИнтАГ предлагает кабельно-проводниковую продукцию оптом и в розницу. ✓Опыт более 20 лет. ☎ +375 (17) 2-505-505. ✓Выгодные цены

Visit intag.by

Key Findings

We analyzed Intag.by page load time and found that the first response time was 479 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

intag.by performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

intag.by

479 ms

intag.by

1465 ms

core.min.css

142 ms

style.css

427 ms

owl.carousel.css

367 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 88% of them (72 requests) were addressed to the original Intag.by, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Intag.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 280.8 kB (22%)

Content Size

1.3 MB

After Optimization

977.0 kB

In fact, the total size of Intag.by main page is 1.3 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. 50% of websites need less resources to load. Images take 901.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 114.0 kB

  • Original 135.2 kB
  • After minification 127.0 kB
  • After compression 21.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 114.0 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 105.4 kB

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

JavaScript Optimization

-20%

Potential reduce by 30.0 kB

  • Original 146.6 kB
  • After minification 146.4 kB
  • After compression 116.7 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 30.0 kB or 20% of the original size.

CSS Optimization

-42%

Potential reduce by 31.5 kB

  • Original 74.9 kB
  • After minification 74.9 kB
  • After compression 43.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. Intag.by needs all CSS files to be minified and compressed as it can save up to 31.5 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (36%)

Requests Now

73

After Optimization

47

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

Accessibility Review

intag.by accessibility score

82

Accessibility Issues

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

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

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

High

Page has valid source maps

SEO Factors

intag.by SEO score

85

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

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 Intag.by 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 Intag.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 data is detected on the main page of Intag. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: