9.9 sec in total
485 ms
8.2 sec
1.2 sec
Welcome to in-green.ru homepage info - get ready to check In Green best content for Russia right away, or after learning these important things about in-green.ru
Искусственные растения (деревья и цветы) по выгодным ценам в интернет-магазине In-Green.ru. Большой каталог товаров, быстрая доставка. Звоните нам уже сегодня.
Visit in-green.ruWe analyzed In-green.ru page load time and found that the first response time was 485 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
in-green.ru performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value25.9 s
0/100
25%
Value21.0 s
0/100
10%
Value31,610 ms
0/100
30%
Value0.976
2/100
15%
Value43.9 s
0/100
10%
485 ms
1531 ms
233 ms
344 ms
573 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 54% of them (68 requests) were addressed to the original In-green.ru, 29% (37 requests) were made to Core-renderer-tiles.maps.yandex.net and 7% (9 requests) were made to Api-maps.yandex.ru. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain In-green.ru.
Page size can be reduced by 896.8 kB (12%)
7.7 MB
6.8 MB
In fact, the total size of In-green.ru main page is 7.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 643.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 165.6 kB, which is 22% 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 643.9 kB or 84% of the original size.
Potential reduce by 243.4 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. In Green images are well optimized though.
Potential reduce by 3.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.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. In-green.ru has all CSS files already compressed.
Number of requests can be reduced by 14 (12%)
114
100
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Green. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
in-green.ru
485 ms
in-green.ru
1531 ms
kernel_main_v1.css
233 ms
ui.font.opensans.min.css
344 ms
template_ffc0fe2136d55608c58e8849e5ab9e11_v1.css
573 ms
1.jpg
307 ms
84bcd53dbe974f6893c250eb9b428446.png
429 ms
e92b09b313e7ceb5d18d3b664f9840c2.jpg
446 ms
7bd962dd96a64b6d398c2788c9c8bc34.jpg
479 ms
be1476f19c0cd31ba9fb5392221f876c.jpg
403 ms
05c26ac15acc1aaeca07df263a31a463.jpg
427 ms
ea896b887c2b87ba503cd49885a49a40.jpg
455 ms
705f2aee1558303903b3ae78aa467f0d.JPG
872 ms
a03da6b46d4e66ae14f0dc6956b46f04.jpg
872 ms
55215da472a3b2059babb2040ec7e7d8.jpg
874 ms
cd793cac5ba511b5e5b2e2263584f41f.jpg
880 ms
0b3b184978c039c2417f66ba34c51cb1.jpg
880 ms
ad5fc22abf5840862451db62b829cab4.jpg
881 ms
6c6619b0d66ceca040ff1ef1568a548d.jpg
883 ms
67c38b2d1090b9429f096b6811d921a6.jpg
884 ms
8a9fbc39555ecb4562c857cad31cae12.jpg
884 ms
4c5aeb2fdd02a6d039d594f200b066f8.jpg
885 ms
cbdf360506b7a49b1c956353f7be45ce.jpg
887 ms
kernel_main_v1.js
893 ms
kernel_main_polyfill_promise_v1.js
888 ms
loadext.min.js
886 ms
extension.min.js
884 ms
jquery-1.8.3.min.js
909 ms
template_2d7602e6eb822fc5acddc02e7dc71f71_v1.js
1121 ms
jqueryui.js
224 ms
top.png
196 ms
whatsapp.svg
199 ms
40192c7609ffe2f7406fc2bd78f324a2.jpg
932 ms
acb9b9f66afd0aa2c97722098cec98c4.jpg
1815 ms
95a5102b93dea7297fc0e90bbf35d23e.jpg
915 ms
df32fa37f6c7230170383ea32851b33e.jpg
1300 ms
d9f36706071b15825cf4d1476777cd41.jpg
919 ms
c00cd86df247a3c2221d16e4db0fa7e2.jpg
974 ms
%D0%B1%D0%BE%D1%82%D0%B0%D0%BD%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B5%20%D0%BA%D0%BE%D0%BF%D0%B8%D0%B8.png
917 ms
%D0%B5%D0%B2%D1%80%D0%BE%D0%BF%D0%B5%D0%B9%D1%81%D0%BA%D0%B8%D0%B5%20%D0%BF%D0%BE%D1%81%D1%82%D0%B0%D0%B2%D1%89%D0%B8%D0%BA%D0%B8.png
920 ms
%D0%BF%D0%BE%D0%B4%D0%B1%D0%BE%D1%80%20%D0%BA%D0%B0%D1%88%D0%BF%D0%BE.png
922 ms
%D0%B4%D0%BE%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B0%20%D0%BF%D0%BE%20%D1%80%D1%84.png
925 ms
57153b7cbe7b95aa8470074f4931bf08.jpg
975 ms
a93d6484b51e5ef0340e244183f95068.jpg
975 ms
1b2025ff56ffe0f480f5dfd40fdd2d22.jpg
1034 ms
69996de40efcbf76c4d35819a4ba61a9.jpg
1178 ms
ea896b887c2b87ba503cd49885a49a40.jpg
1054 ms
705f2aee1558303903b3ae78aa467f0d.JPG
1070 ms
a03da6b46d4e66ae14f0dc6956b46f04.jpg
1024 ms
55215da472a3b2059babb2040ec7e7d8.jpg
1024 ms
cd793cac5ba511b5e5b2e2263584f41f.jpg
1037 ms
0b3b184978c039c2417f66ba34c51cb1.jpg
1118 ms
ad5fc22abf5840862451db62b829cab4.jpg
1119 ms
6c6619b0d66ceca040ff1ef1568a548d.jpg
1121 ms
67c38b2d1090b9429f096b6811d921a6.jpg
1147 ms
8a9fbc39555ecb4562c857cad31cae12.jpg
1237 ms
4c5aeb2fdd02a6d039d594f200b066f8.jpg
1228 ms
cbdf360506b7a49b1c956353f7be45ce.jpg
1230 ms
da28ba550c0ac5be4446937d2a61524c.jpg
1247 ms
fc3756482d15e4398ad04937f27c0392.jpg
1263 ms
ddd4fe75e12b6e2ae201f09e164c71a2.jpg
1341 ms
f7690940d9fcab5e57b37e00a10c429f.jpg
1348 ms
question_mark.png
1348 ms
sprite_pay_icons.png
1360 ms
fontawesome.solid.woff
1614 ms
fontawesome.regular.woff
1614 ms
fontawesome.light.woff
1543 ms
ba.js
402 ms
723 ms
tag.js
826 ms
Glyphter.woff
1050 ms
ajax_counter.php
2001 ms
bx_stat
186 ms
combine
971 ms
advert.gif
561 ms
sync_cookie_image_decide
219 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
139 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
126 ms
4965b66fe115b2f2ed500ece66514d86.cur
253 ms
77492cf358d8b12629399322926c93f2.cur
377 ms
1
133 ms
v3ig1HtAFT
733 ms
139 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
134 ms
tiles
753 ms
tiles
867 ms
tiles
994 ms
tiles
1091 ms
tiles
1240 ms
tiles
1121 ms
tiles
1132 ms
tiles
1260 ms
tiles
1231 ms
tiles
1172 ms
tiles
1215 ms
tiles
1230 ms
tiles
1294 ms
tiles
1330 ms
tiles
1344 ms
tiles
1356 ms
tiles
1362 ms
tiles
1366 ms
tiles
1414 ms
tiles
1454 ms
tiles
1470 ms
tiles
1486 ms
tiles
1496 ms
tiles
1501 ms
tiles
1535 ms
tiles
1580 ms
tiles
1596 ms
tiles
1622 ms
tiles
1630 ms
tiles
1636 ms
tiles
1654 ms
tiles
1706 ms
inception-7d288965eb52821298d43f862e861cd5d905074b.js
403 ms
v3ig1HtAFT
545 ms
tiles
1028 ms
tiles
930 ms
tiles
810 ms
tiles
722 ms
tiles
695 ms
2c3d90d4e522c1f62b6cf3e59f7a877d.png
123 ms
v3ig1HtAFT
615 ms
bundle_ru_RU.js
256 ms
in-green.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
<frame> or <iframe> elements do not have a title
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.
in-green.ru 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
Missing source maps for large first-party JavaScript
in-green.ru 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
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise In-green.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that In-green.ru 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.
in-green.ru
Open Graph description is not detected on the main page of In Green. 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: