5.1 sec in total
692 ms
3.8 sec
645 ms
Welcome to greenmaster.by homepage info - get ready to check Greenmaster best content for Belarus right away, or after learning these important things about greenmaster.by
Сделаем все: от проекта до объекта! Ландшафтный дизайн загородного участка в Минске. Качественно выполним озеленение и благоустройство "под ключ". Работаем по всей Беларуси.
Visit greenmaster.byWe analyzed Greenmaster.by page load time and found that the first response time was 692 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
greenmaster.by performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.3 s
2/100
25%
Value7.1 s
31/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value9.4 s
31/100
10%
692 ms
355 ms
357 ms
364 ms
367 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 64% of them (47 requests) were addressed to the original Greenmaster.by, 12% (9 requests) were made to Cp.onicon.ru and 7% (5 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Greenmaster.by.
Page size can be reduced by 701.0 kB (36%)
2.0 MB
1.3 MB
In fact, the total size of Greenmaster.by main page is 2.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. 40% of websites need less resources to load. Images take 973.1 kB which makes up the majority of the site volume.
Potential reduce by 84.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 17.4 kB, which is 16% 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 84.9 kB or 80% of the original size.
Potential reduce by 10.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. Greenmaster images are well optimized though.
Potential reduce by 520.5 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 520.5 kB or 68% of the original size.
Potential reduce by 84.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. Greenmaster.by needs all CSS files to be minified and compressed as it can save up to 84.9 kB or 76% of the original size.
Number of requests can be reduced by 35 (53%)
66
31
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenmaster. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
greenmaster.by
692 ms
highslide.min.css
355 ms
highslide.packed.js
357 ms
flowplayer-3.2.9.min.js
364 ms
calendar.css
367 ms
ru.js
368 ms
cookie.js
366 ms
widgets.js
534 ms
calendar.packed.js
535 ms
feedback.factory.min.js
541 ms
styles.css
545 ms
highslide.css
545 ms
no_cookies_message.js
547 ms
jquery-1.7.2.min.js
1076 ms
left_menu.js
714 ms
nocopy.for.all.js
722 ms
share.js
15 ms
top100.jcn
394 ms
bg.gif
184 ms
%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80_1.jpg
188 ms
%D0%BB%D0%BE%D0%B3%D0%BE_%D1%81_%D1%82%D0%B5%D0%BB%D0%B5%D1%84%D0%BE%D0%BD%D0%BE%D0%BC.jpg
187 ms
landscape1.jpg
182 ms
Landscape-design.jpg
184 ms
Landscape-design1.jpg
185 ms
nashi-preimuschestva.jpg
732 ms
pozvonite.jpg
363 ms
%D0%9E%D1%81%D1%82%D0%B0%D0%B2%D0%B8%D1%82%D1%8C_%D0%B7%D0%B0%D1%8F%D0%B2%D0%BA%D1%83.jpg
361 ms
%D0%A1%D0%BA%D0%B0%D1%87%D0%B0%D1%82%D1%8C_%D0%BF%D1%80%D0%B5%D0%B7%D0%B5%D0%BD%D1%82%D0%B0%D1%86%D0%B8%D1%8E.jpg
361 ms
%D0%AD%D0%BA%D1%81%D0%BA%D0%BB%D1%8E%D0%B7%D0%B8%D0%B2%D0%BD%D1%8B%D0%B9_%D0%BB%D0%B0%D0%BD%D0%B4%D1%88%D0%B0%D1%84%D1%82%D0%BD%D1%8B%D0%B9_%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD.jpg
546 ms
%D0%9A%D0%B0%D0%BA-%D0%BC%D1%8B-%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D0%B0%D0%B5%D0%BC_0.jpg
553 ms
24142604_5.jpg
542 ms
24142404_5.jpg
543 ms
24142204_5.jpg
543 ms
300420152378.jpg
1450 ms
5_2.png
724 ms
%D0%B1%D0%B0%D0%BD%D0%BD%D0%B5%D1%80-%D0%BD%D0%B0-%D1%81%D0%B0%D0%B9%D1%82.jpg
725 ms
%D0%B2%D0%B0%D0%B7%D0%BE%D0%BD%D1%8B-%D1%81%D0%B0%D0%B4%D0%BE%D0%B2%D1%8B%D0%B5.jpg
725 ms
LEVEL-L01.jpg
737 ms
%D0%BA%D1%803.jpg
904 ms
kupel1.jpg
906 ms
head.jpg
1989 ms
st.gif
903 ms
men.gif
910 ms
br.gif
1075 ms
st1.gif
1078 ms
bg_search.jpg
1088 ms
men.gif
1098 ms
zoomin.cur
373 ms
foot.jpg
1232 ms
watch.js
181 ms
hit
258 ms
top100.scn
133 ms
simple_loader.js
519 ms
loader.js
305 ms
b-share.png
9 ms
zoomin.cur
1205 ms
b-share-icon.png
8 ms
b-share-popup_down__tail.png
9 ms
watch.js
465 ms
hit
129 ms
api.js
93 ms
b634db09b19572037fc1c7a7fd4d035d.js
96 ms
bootstrap.min.js
186 ms
advert.gif
95 ms
counter
261 ms
bootstrap.min.js
96 ms
onicon.site.min.css
93 ms
onicon.site.min.js
186 ms
1
90 ms
onicon.site.min.css
190 ms
26812653
92 ms
onicon.site.min.js
566 ms
hosts-2.js
382 ms
hosts-2.js
98 ms
greenmaster.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
Links do not have a discernible name
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.
greenmaster.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
greenmaster.by SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenmaster.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 Greenmaster.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.
greenmaster.by
Open Graph description is not detected on the main page of Greenmaster. 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: