5.9 sec in total
398 ms
5.1 sec
419 ms
Click here to check amazing Ecolog content for Belarus. Otherwise, check out these important facts you probably never knew about ecolog.by
Информационный портал промышленных экологов Беларуси! Мы объединяем специалистов, занимающихся непосредственно охраной окружающей среды на предприятиях (организациях), и лиц, заинтересованных в охране...
Visit ecolog.byWe analyzed Ecolog.by page load time and found that the first response time was 398 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ecolog.by performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.2 s
2/100
25%
Value11.3 s
5/100
10%
Value1,950 ms
8/100
30%
Value0.083
94/100
15%
Value19.5 s
2/100
10%
398 ms
1162 ms
244 ms
250 ms
252 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 47% of them (50 requests) were addressed to the original Ecolog.by, 10% (11 requests) were made to Vk.com and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Back-end.nozo.com.
Page size can be reduced by 594.4 kB (61%)
973.6 kB
379.3 kB
In fact, the total size of Ecolog.by main page is 973.6 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. 55% of websites need less resources to load. Javascripts take 579.1 kB which makes up the majority of the site volume.
Potential reduce by 51.4 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 51.4 kB or 74% of the original size.
Potential reduce by 13.8 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. Ecolog images are well optimized though.
Potential reduce by 438.3 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 438.3 kB or 76% of the original size.
Potential reduce by 90.9 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. Ecolog.by needs all CSS files to be minified and compressed as it can save up to 90.9 kB or 83% of the original size.
Number of requests can be reduced by 47 (46%)
102
55
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecolog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ecolog.by
398 ms
www.ecolog.by
1162 ms
style.css
244 ms
ddsmoothmenu.css
250 ms
fancybox.css
252 ms
jquery.js
392 ms
ddsmoothmenu.js
254 ms
fancybox.js
254 ms
swfobject.js
16 ms
core.css
380 ms
ss.css
385 ms
core_window.css
386 ms
style.css
414 ms
core.js
518 ms
core_ajax.js
522 ms
session.js
525 ms
openapi.js
419 ms
core_window.js
524 ms
ss.js
534 ms
widget.js
66 ms
openapi.js
419 ms
zp.js
737 ms
script.js
632 ms
top100.jcn
468 ms
watch.js
1 ms
banner-88x31-rambler-gray2.gif
281 ms
ecolog.png
146 ms
menutop.png
145 ms
beginner.jpg
148 ms
478d591c1d5056f3c45f8d943b40f8f0.gif
758 ms
533ed2b9d0ffaf6bc7cec64d7bcde7f2.gif
262 ms
b2e901ea2f1b80f5d4152d693141004a.jpg
218 ms
efcb8b7bec39888c34d83e35ec1105c6.jpg
381 ms
c535053f70be020c014e69721dc47a0e.JPG
263 ms
f3e1f1565b660c68a5efe6484e7fb82c.jpg
263 ms
fc1479ed50c181963c66752b9f78ee7b.gif
341 ms
da7b3f2a681c1f20c1c2a204eb42ce99.jpg
385 ms
9464a4950a62ccba7d5e665399c6e01e.gif
403 ms
aa7a04193c5c467dbf2653c9e3907b8b.jpg
403 ms
ec0c1f8fd46ba1d510761acae40daa86.gif
466 ms
4c2caf29b35df9b017867e5e470677b2.jpg
501 ms
86e63499d4f227f6051df682c47b2ed1.jpg
507 ms
82a7cd60aa73b142716bfc0606cc0e4b.jpg
511 ms
57f2ccfddb9101c4bf86890ce98bdc3c.jpg
509 ms
50db6dd61593e91294a1f2e19b334879.jpg
587 ms
e1deef178c6431a077baa59d72abceb8.jpg
630 ms
dd0f5d5a658ec6bdc974e04d78738ea0.jpg
631 ms
744755a55d615a9ea3106a1eff4ea004.jpg
638 ms
e964f064cfe29531f106b14875ac3183.JPG
637 ms
8abdf4f8eaaf08de91584320956384d6.gif
1338 ms
9d67307b67f7ec491fc27195b9c68f47.gif
752 ms
wave.png
724 ms
table_main_bg.gif
732 ms
icons.png
732 ms
social.png
847 ms
upload.gif
277 ms
widget_community.php
437 ms
aci.js
196 ms
rightblock.png
777 ms
acode.js
982 ms
likebox.php
238 ms
hit
278 ms
top100.scn
136 ms
1px.gif
688 ms
100 ms
183 ms
kGVFUQ4LgBj.css
194 ms
c0qM4_fl0zF.css
247 ms
SRSW8M763HA.js
339 ms
4uFOsJeWEIM.js
418 ms
y97Ig99UVTs.js
337 ms
KHAtULXOQuz.js
362 ms
hit
148 ms
271 ms
loader_nav19239_3.js
130 ms
lite.css
247 ms
lite.js
504 ms
lang3_0.js
254 ms
widget_community.css
271 ms
xdm.js
254 ms
al_community.js
263 ms
allc.gif
383 ms
match
193 ms
292115_232292063536755_1479676803_n.jpg
235 ms
12729213_572778612879398_2131264878528851684_n.jpg
443 ms
12243575_103723243328360_7216517116023872153_n.jpg
383 ms
11222810_848037821939293_6706593845138838389_n.jpg
382 ms
wL6VQj7Ab77.png
66 ms
1JLnMyDN79z.png
67 ms
c_9fd883da.jpg
428 ms
gOqQXDjmktU.jpg
418 ms
RLdnMIN1Qn8.jpg
425 ms
kGRr9zP0swc.jpg
267 ms
Hy_0UmBwJKY.jpg
420 ms
YTgdXkqU7sw.jpg
267 ms
7GJJ04oxOhg.jpg
299 ms
llOn6MRtBXc.jpg
421 ms
NptYZZGNiow.jpg
435 ms
_0cQci_pZRk.jpg
291 ms
uSZTICQeAVc.jpg
418 ms
camera_50.png
127 ms
w_logo.png
119 ms
wm
1966 ms
VXcANLwwL5J.js
72 ms
i8XO-4kv8i7.js
67 ms
print.css
123 ms
adlik
226 ms
ecolog.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
ecolog.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ecolog.by SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
RU
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecolog.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Ecolog.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.
ecolog.by
Open Graph description is not detected on the main page of Ecolog. 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: