7 sec in total
994 ms
5.6 sec
431 ms
Welcome to metarya.ru homepage info - get ready to check Metarya best content for Russia right away, or after learning these important things about metarya.ru
Преображенский храм г.Рязань Канищево
Visit metarya.ruWe analyzed Metarya.ru page load time and found that the first response time was 994 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
metarya.ru performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value6.9 s
6/100
25%
Value11.0 s
6/100
10%
Value3,410 ms
2/100
30%
Value0.224
56/100
15%
Value31.8 s
0/100
10%
994 ms
213 ms
214 ms
215 ms
326 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 41% of them (55 requests) were addressed to the original Metarya.ru, 33% (44 requests) were made to St6-21.vk.com and 5% (6 requests) were made to Vk.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Metarya.ru.
Page size can be reduced by 529.5 kB (11%)
4.8 MB
4.2 MB
In fact, the total size of Metarya.ru main page is 4.8 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. 60% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 72.0 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 72.0 kB or 45% of the original size.
Potential reduce by 22.2 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. Metarya images are well optimized though.
Potential reduce by 356.7 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 356.7 kB or 15% of the original size.
Potential reduce by 78.7 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. Metarya.ru needs all CSS files to be minified and compressed as it can save up to 78.7 kB or 15% of the original size.
Number of requests can be reduced by 82 (64%)
128
46
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Metarya. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
metarya.ru
994 ms
jdvthumbs.css
213 ms
slimbox.css
214 ms
style.css
215 ms
mootools-core.js
326 ms
core.js
219 ms
caption.js
318 ms
slimbox.js
319 ms
mootools-more.js
649 ms
blog_calendar.js
341 ms
system.css
341 ms
general.css
424 ms
template.css
425 ms
menu.css
432 ms
m_accordeon.css
438 ms
ext.js
214 ms
share.js
403 ms
Chteniya.js
309 ms
goTop.js
310 ms
goTop.css
318 ms
jquery.tap.js
320 ms
akkordeon.js
325 ms
element.js
41 ms
system.css
107 ms
openapi.318ba3d5a50b8d6990cb0284cb0e0963.js
265 ms
tag.js
1679 ms
2_1_F2FFF4FF_D2FFD4FF_0_uniques
1304 ms
270524020624_1_00001.jpg
1188 ms
5hcNYC5GYzU.jpg
1186 ms
57EWE6ORy9c_1.jpg
1537 ms
04.jpg
235 ms
svyat_nikolay.jpg
2052 ms
printButton.png
131 ms
thumb-fp-7fba3824d5627bcde00f833b85fcdca1.jpg
245 ms
thumb-fp-8c4d23cedd7772f32c60a7387c0850d7.jpg
1155 ms
thumb-fp-aa621937c897d39516a4c1c8b7b7cf52.jpg
1156 ms
thumb-fp-92ef85b070a6801142d486bfe48981f8.jpg
1185 ms
thumb-fp-148bd1c44303d23c87b9266e6729f576.jpg
1185 ms
thumb-fp-8c77eeeaf9f9b023a298876c07e6b1d6.jpg
1292 ms
thumb-fp-90d5e0136ba19b3fc488422afddfe6dd.jpg
1291 ms
thumb-fp-4d5bfd8aa55fbaaa161bac515f9ef7f9.jpg
1292 ms
thumb-fp-1b1f9a409aa7e43ffa213dadef93204b.jpg
1289 ms
thumb-fp-f79c13f0a6c95aa552395c7861fdc42c.jpg
1405 ms
thumb-fp-3d70a6779d7e5da99e0f1c57aa40d8bc.jpg
1401 ms
thumb-fp-3c45e4807df1939130b1c6ad2691fb72.jpg
1411 ms
thumb-fp-a1edb0b98d8563e622bce1c32995baaf.jpg
1408 ms
thumb-fp-4d8d15fd214d456c98cb0d0aa82e02ec.jpg
1522 ms
thumb-fp-33aa64270c3235b33ab8a44152d2e478.jpg
1522 ms
thumb-fp-2752e2bcffa492ab327120d327930857.jpg
1533 ms
thumb-fp-82ee71940e6b2c470cb9ba0a54e00ee8.jpg
1533 ms
thumb-fp-2beeff41c2609926d7027bdc1f880eae.jpg
1642 ms
livemarks.png
1642 ms
na_hram.htm
1633 ms
connect.js
1427 ms
upload.gif
913 ms
calendar1.html
1402 ms
widget_community.php
939 ms
online.php
1399 ms
icon-date.gif
1498 ms
article_separator.png
1501 ms
reformal.js
1130 ms
knopka_naverh.png
584 ms
loader_nav21098907335_3.js
449 ms
fonts_cnt.c7a76efe.css
1106 ms
lite.93f44416.css
808 ms
lang3_2.js
657 ms
polyfills.c3a1b892.js
751 ms
vkui.388c7a16.css
829 ms
xdm.js
655 ms
ui_common.54e472db.css
731 ms
react.6a15a5cc.js
904 ms
vkcom-kit.46f7449b.css
942 ms
vkcom-kit.83b486d3.js
1161 ms
vkcom-kit-icons.780e6c65.js
1012 ms
vkui.55891411.js
1159 ms
architecture-mobx.b1015542.js
1002 ms
state-management.94ab436a.js
1046 ms
audioplayer-lib.93b52d88.css
1083 ms
audioplayer-lib.3321ac20.js
1202 ms
common.e1d31bcf.js
1808 ms
7f463667.2f09ffd3.js
1178 ms
ui_common.b1037836.css
1185 ms
ui_common.cea23e66.js
1223 ms
audioplayer.7787a5d3.css
1230 ms
audioplayer.35efc358.js
1252 ms
widget_community.4978d481.css
1266 ms
5441c5ed.4aafa0df.js
1295 ms
aa3c5e05.1a400e87.js
1320 ms
likes.33883160.css
1320 ms
likes.ad9fb1a1.js
1342 ms
vkcom-kit.3d97e67b.css
1356 ms
vkcom-kit.7af88850.js
1402 ms
react.84cfd9aa.js
1432 ms
vkui.177fea38.js
1581 ms
vkcom-kit-icons.172a0099.js
1431 ms
architecture-mobx.d853b516.js
1449 ms
audioplayer-lib.85b39ca5.css
1487 ms
audioplayer-lib.67144f68.js
1595 ms
state-management.e5a289bd.js
1564 ms
c3d11fba.475e3ac7.js
1565 ms
reformal.js
251 ms
lite.bcf10ece3464fec8b554bde483fa2494.js
510 ms
dk
142 ms
widget_group.9533a7bc.css
1112 ms
i
676 ms
jquery-1.8.3.min.js
123 ms
icon.php
525 ms
share-balance.xml
266 ms
Sposobs_money2.png
227 ms
2ac48b3f60b25cc420c1ed969c32f31f
185 ms
st.php
485 ms
47994%7CaHR0cDovL21ldGFyeWEucnUv%7C%7C94503
185 ms
advert.gif
756 ms
community.be2fc20a.css
920 ms
base.ec2ae8ae.css
895 ms
0fc69f32.aea48755.js
884 ms
e7eaa3a9.0425872f.js
850 ms
57703e15.ed6fd4c4.js
885 ms
edb6ffde.69277bd5.js
1218 ms
community.640f3bc9.js
772 ms
advanced=1&href=2.ls
167 ms
is4706.jpg
532 ms
sync_cookie_image_decide
157 ms
logo_ok-widget@2x.png
137 ms
1
146 ms
U7tv36g5J4FrjAPjAB6NU03peuSOnKYAuO07SVU9yRpH_GbPZ6yZ78oyP07ICkDTlKzzOq47gjP3ap9f1lwWqZAD.jpg
460 ms
QulWsGFAn5k.png
521 ms
aPXJTgPNxzyzyLMMdqC-XdYnwbWI-kduxxPTNtQy8nSbAmIC5-P-zS-Wvi8UJEI4IgqXOMBNKB9E7IjH4GXweVF8.jpg
495 ms
YSxahwa9y7faZaYFDENsPwg033Ewa-xUFogR_qJ2xN-3nFDZh1-59968BCxX8nkSsMt_fk9cSndnnfxC1v2MjEO6.jpg
386 ms
Hqjat1Qd7toGr7LkaAfR9hF5bKShriK8TQ5ee7PtRLYIuX2Kss1clQVINqIX_Az6ML2ySQ_R.jpg
487 ms
7qTEtVYaVyp1B5UkolhFDzQgal_7VlBERpwW4QJj9OWkmorHBPjgfEYrCMJkbVg64wovnWnsKWql4BbqkL2bydOJ.jpg
581 ms
upload.gif
82 ms
WgLPGw8FY9Y.jpg
669 ms
metarya.ru accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
metarya.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
metarya.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Metarya.ru 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 Metarya.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.
metarya.ru
Open Graph description is not detected on the main page of Metarya. 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: