5.3 sec in total
1.2 sec
3.9 sec
259 ms
Click here to check amazing Megre content for Russia. Otherwise, check out these important facts you probably never knew about megre.ru
Звенящие Кедры России - интернет-магазин продукции родовых поместий. Узнать подробнее, посмотреть цены и купить продукцию с доставкой по России можете на сайте.
Visit megre.ruWe analyzed Megre.ru page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
megre.ru performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value17.0 s
0/100
25%
Value17.8 s
0/100
10%
Value1,460 ms
15/100
30%
Value0.274
44/100
15%
Value29.1 s
0/100
10%
1155 ms
252 ms
258 ms
262 ms
429 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 68% of them (78 requests) were addressed to the original Megre.ru, 6% (7 requests) were made to Api-maps.yandex.ru and 4% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Megre.ru.
Page size can be reduced by 1.2 MB (40%)
3.1 MB
1.9 MB
In fact, the total size of Megre.ru main page is 3.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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 172.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. 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 172.9 kB or 67% of the original size.
Potential reduce by 76.5 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. Megre images are well optimized though.
Potential reduce by 667.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 667.5 kB or 72% of the original size.
Potential reduce by 321.6 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. Megre.ru needs all CSS files to be minified and compressed as it can save up to 321.6 kB or 84% of the original size.
Number of requests can be reduced by 60 (58%)
103
43
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Megre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
megre.ru
1155 ms
kernel_main.css
252 ms
kernel_altasib.up.css
258 ms
template_6b59ad946d9eb3b1f8211e0c686b259e.css
262 ms
jquery-1.11.3.min.js
429 ms
jquery-migrate-1.2.1.min.js
266 ms
core.js
396 ms
core_ajax.js
379 ms
jquery-1.8.3.min.js
634 ms
script_jq.js
389 ms
siteheart.js
13 ms
slide.js
393 ms
modernizr.custom.js
505 ms
cssua.min.js
516 ms
jquery.cycle.min.js
525 ms
jquery.corner.min.js
522 ms
jquery.lightbox.js
556 ms
jquery.linkselect.js
658 ms
jquery.bxSlider.js
659 ms
jquery.inputlabel.min.js
660 ms
script.js
663 ms
index.css
681 ms
liMarquee.css
755 ms
jquery.liMarquee.js
759 ms
form_malsup.js
777 ms
309 ms
classie.js
776 ms
modalEffects.js
784 ms
css-filters-polyfill.js
808 ms
623 ms
ba.js
177 ms
combine.xml
790 ms
field.jpg
920 ms
logo.png
329 ms
loupe.png
136 ms
123.jpg
635 ms
800_360.jpg
643 ms
%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA4567.JPG
133 ms
VM_proiz_b.jpg
447 ms
ProductsCatalog_s.jpg
1171 ms
24494054.png
448 ms
24493952.png
523 ms
m_3821.jpg
524 ms
24494023.png
651 ms
IMG_0845.png
949 ms
Maslo_kedrovoe_250_sm.png
761 ms
kedr1.png
918 ms
%D0%9F%D0%BE%D0%B4%D1%83%D1%88%D0%BA%D0%B0.png
1036 ms
i-twitter.png
915 ms
i-facebook.png
1016 ms
i-live.png
1024 ms
i-vk.png
1025 ms
i-odnoklassniki.gif
1080 ms
i-mail.gif
1145 ms
i-instagram.gif
1152 ms
i-you.png
1153 ms
captcha.php
1243 ms
bg-sub.png
1722 ms
close-btn.png
1266 ms
podpis.png
1275 ms
top-grad.png
1257 ms
mail.png
1275 ms
basket.png
1346 ms
background.jpg
1373 ms
background.png
1383 ms
AGCenturyOldStyleCyr_Roman.ttf
1377 ms
strobile.jpg
1527 ms
price-yellow.png
1460 ms
analytics.js
48 ms
watch.js
186 ms
qzV_7mTb3N4
91 ms
sh.js
235 ms
bx_stat
241 ms
collect
10 ms
collect
63 ms
kernel_main.css
1397 ms
kernel_altasib.up.css
1405 ms
JH4kI5HABLU
84 ms
TsLyrdxYfx8
94 ms
XMg9sFRSNBQ
85 ms
9shzbEoie70
88 ms
www-embed-player-vflZsBgOl.css
70 ms
www-embed-player.js
90 ms
watch.js
463 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
77 ms
ad_status.js
55 ms
sh.js
55 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
119 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
120 ms
template_6b59ad946d9eb3b1f8211e0c686b259e.css
1215 ms
index.css
1184 ms
liMarquee.css
1209 ms
widget.js
84 ms
bot-grad.png
1146 ms
li-arrow.jpg
1147 ms
widget.js
12 ms
orange.css
15 ms
logo.png
2 ms
payment.jpg
1060 ms
21.png
1120 ms
spacer.gif
1131 ms
advert.gif
199 ms
grey_pager.png
1037 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
113 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
154 ms
4965b66fe115b2f2ed500ece66514d86.cur
266 ms
77492cf358d8b12629399322926c93f2.cur
378 ms
1
91 ms
ln-green.png
882 ms
rn-green.png
906 ms
ln-yellow.png
938 ms
rn-yellow.png
939 ms
a.html
3 ms
collect
25 ms
megre.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
ARIA input fields do not have accessible names
[role]s are not contained by their required parent element
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
Form elements do not have associated labels
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.
megre.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
megre.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 Megre.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 Megre.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.
megre.ru
Open Graph description is not detected on the main page of Megre. 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: