Tools & Wizards About Us
evikom.by screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

evikom.by

ТЦ ЭВИКОМ - Торговый Центр "Эвиком" г.Витебск | Аренда объектов торговли, услуг, общепита

Page Load Speed

31.4 sec in total

First Response

639 ms

Resources Loaded

26.1 sec

Page Rendered

4.7 sec

evikom.by screenshot

About Website

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

Предоставляем в аренду торговые и офисные площади, магазины, павильоны, роллеты для оказания услуг, розничной торговли, общепита, фитнеса.

Visit evikom.by

Key Findings

We analyzed Evikom.by page load time and found that the first response time was 639 ms and then it took 30.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

evikom.by performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

evikom.by

639 ms

ind.php

199 ms

line.php

798 ms

main.css

172 ms

script.js

506 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 59% of them (23 requests) were addressed to the original Evikom.by, 5% (2 requests) were made to U7885.23.spylog.com and 5% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Informer.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 871.2 kB (79%)

Content Size

1.1 MB

After Optimization

228.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Evikom.by main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 654 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 695 B

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 654 B or 48% of the original size.

Image Optimization

-3%

Potential reduce by 18 B

  • Original 704 B
  • After minification 686 B

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

JavaScript Optimization

-79%

Potential reduce by 868.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 226.4 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 868.4 kB or 79% of the original size.

CSS Optimization

-81%

Potential reduce by 2.2 kB

  • Original 2.7 kB
  • After minification 2.2 kB
  • After compression 495 B

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. Evikom.by needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (61%)

Requests Now

31

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evikom. 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.

Network Requests Diagram

evikom.by

evikom.by

639 ms

ind.php

ind.php

199 ms

line.php

line.php

798 ms

main.css

main.css

172 ms

script.js

script.js

506 ms

runtime.js

runtime.js

1226 ms

index-evikom.js

index-evikom.js

3202 ms

flash.js

flash.js

499 ms

counter2.2.js

counter2.2.js

495 ms

120x60.gif

120x60.gif

733 ms

image.php

image.php

693 ms

26666-9.GIF

26666-9.GIF

733 ms

catalog-tut5.gif

catalog-tut5.gif

1069 ms

3_1_FFD386FF_FFB366FF_0_pageviews

3_1_FFD386FF_FFB366FF_0_pageviews

20426 ms

site-evikom-slice_12_over.gif

site-evikom-slice_12_over.gif

681 ms

site-evikom-slice_10_over.gif

site-evikom-slice_10_over.gif

690 ms

site-evikom-slice_08.gif

site-evikom-slice_08.gif

694 ms

site-evikom-slice_10.gif

site-evikom-slice_10.gif

689 ms

site-evikom-slice_12.gif

site-evikom-slice_12.gif

688 ms

site-evikom-slice_04.jpg

site-evikom-slice_04.jpg

712 ms

site-evikom-slice_07.gif

site-evikom-slice_07.gif

711 ms

site-evikom-slice_11.gif

site-evikom-slice_11.gif

711 ms

site-evikom2.gif

site-evikom2.gif

710 ms

point.gif

point.gif

709 ms

otl_mesto_dreklamy.gif

otl_mesto_dreklamy.gif

710 ms

reply.gif

reply.gif

724 ms

icon_biggrin.gif

icon_biggrin.gif

723 ms

icon_smile.gif

icon_smile.gif

722 ms

new_topic.gif

new_topic.gif

724 ms

catalog-tut5.gif

catalog-tut5.gif

533 ms

allc.gif

allc.gif

556 ms

tochka.gif

tochka.gif

498 ms

cnt

cnt

668 ms

u7885.23.spylog.com

u7885.23.spylog.com

1573 ms

hit

hit

2634 ms

watch.js

watch.js

0 ms

cnt

cnt

3362 ms

hit

hit

177 ms

adlik

adlik

224 ms

Accessibility Review

evikom.by accessibility score

33

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

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

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

evikom.by best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

evikom.by SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

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

evikom.by

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