7.7 sec in total
685 ms
6.8 sec
176 ms
Click here to check amazing Active content for Belarus. Otherwise, check out these important facts you probably never knew about active.by
Компания обладает уникальной платформой поставки и управления облачными сервисами собственной разработки, обеспечивающей круглосуточный доступ к услугам
Visit active.byWe analyzed Active.by page load time and found that the first response time was 685 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
active.by performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value15.6 s
0/100
25%
Value23.5 s
0/100
10%
Value43,540 ms
0/100
30%
Value0.007
100/100
15%
Value59.1 s
0/100
10%
685 ms
1318 ms
1005 ms
1405 ms
16 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 51% of them (46 requests) were addressed to the original Active.by, 10% (9 requests) were made to Trackers.adtarget.me and 8% (7 requests) were made to Rt.intarget.ru. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Active.by.
Page size can be reduced by 164.5 kB (28%)
587.7 kB
423.2 kB
In fact, the total size of Active.by main page is 587.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. 35% of websites need less resources to load. Images take 290.5 kB which makes up the majority of the site volume.
Potential reduce by 48.7 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 48.7 kB or 75% of the original size.
Potential reduce by 4.0 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. Active images are well optimized though.
Potential reduce by 111.8 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 111.8 kB or 48% of the original size.
Number of requests can be reduced by 44 (52%)
84
40
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Active. 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 as a result speed up the page load time.
active.by
685 ms
www.active.by
1318 ms
1005 ms
1405 ms
conversion.js
16 ms
gtm.js
146 ms
analytics.js
145 ms
mixpanel-2-latest.min.js
143 ms
loader.js
313 ms
logoActiveCloud.png
403 ms
i-info.png
212 ms
arr_down.gif
212 ms
nav-top-sep.png
406 ms
site-search.png
408 ms
site-search-button.png
411 ms
services-tab.png
413 ms
banner-tabs-control.png
414 ms
dot-blue.gif
604 ms
banner-vh.jpg
1040 ms
banner-bonus.png
1295 ms
banner-cs.jpg
1241 ms
banner-sb.jpg
812 ms
banner-activebackup.jpg
614 ms
banner-ssl.jpg
1001 ms
banner-h1c.jpg
1015 ms
banner-lync.png
1610 ms
banner-ox.jpg
1203 ms
banner-daas.jpg
1217 ms
banner-rentsoft.jpg
1242 ms
banner-mx.jpg
1804 ms
banner-symantec.jpg
1422 ms
banner-sla.jpg
1442 ms
arrs-actions.png
1445 ms
blank.gif
1493 ms
ajax_middle.gif
1624 ms
news-line-lr.png
1644 ms
news-line-bg.png
1648 ms
teasers54.png
1695 ms
teasers25.png
1809 ms
teasers5.png
1826 ms
teasers7.png
1846 ms
teasers49.png
1847 ms
social-bars.png
1897 ms
show.php
1948 ms
tlds.json
961 ms
btn-video-text.jpg
1910 ms
34 ms
linkid.js
28 ms
conversion_async.js
19 ms
watch.js
231 ms
fbds.js
18 ms
code.js
308 ms
pixel.min.js
190 ms
collect
22 ms
collect
60 ms
43 ms
32 ms
SegoeScript.woff
2827 ms
btn-video.jpg
1845 ms
39 ms
ga-audiences
36 ms
version.js
158 ms
watch.js
573 ms
carusel-shadow.png
1854 ms
banner-carusel-arr.png
1703 ms
intargetModule.js
314 ms
counter
155 ms
93 ms
comm.html
159 ms
98 ms
check
165 ms
95 ms
advert.gif
114 ms
pixel
34 ms
284 ms
cke
308 ms
sync.cgi
570 ms
1
114 ms
sync
52 ms
cookie
158 ms
93 ms
95 ms
96 ms
callback
307 ms
96 ms
97 ms
flags.jpg
205 ms
i-solutions-mainpage.png
205 ms
tracker
154 ms
4 ms
zp.js
655 ms
active.by accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
active.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
active.by SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Active.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 Active.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.
active.by
Open Graph description is not detected on the main page of Active. 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: