7.1 sec in total
890 ms
4.6 sec
1.6 sec
Click here to check amazing Metr 2 content for Russia. Otherwise, check out these important facts you probably never knew about metr2.pro
Интернет-магазин
Visit metr2.proWe analyzed Metr2.pro page load time and found that the first response time was 890 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
metr2.pro performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value11.0 s
0/100
25%
Value10.5 s
7/100
10%
Value3,790 ms
1/100
30%
Value0
100/100
15%
Value15.9 s
6/100
10%
890 ms
143 ms
282 ms
410 ms
412 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 83% of them (43 requests) were addressed to the original Metr2.pro, 4% (2 requests) were made to Cdn.envybox.io and 4% (2 requests) were made to Bitrix.info. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Gso.amocrm.ru.
Page size can be reduced by 287.5 kB (24%)
1.2 MB
917.0 kB
In fact, the total size of Metr2.pro main page is 1.2 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. 55% of websites need less resources to load. Javascripts take 544.8 kB which makes up the majority of the site volume.
Potential reduce by 241.8 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 44.1 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 241.8 kB or 88% of the original size.
Potential reduce by 20.3 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. Metr 2 images are well optimized though.
Potential reduce by 9.2 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 16.2 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. Metr2.pro needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 13% of the original size.
Number of requests can be reduced by 28 (57%)
49
21
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Metr 2. 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 7 to 1 for CSS and as a result speed up the page load time.
metr2.pro
890 ms
ui.design-tokens.min.css
143 ms
ui.font.opensans.min.css
282 ms
main.popup.bundle.min.css
410 ms
default_a927a3721cf03b0f3a35305a5bc4f281_v1.css
412 ms
template_885928c17391bead752fb696de123023_v1.css
696 ms
jquery-3.6.0.min.js
561 ms
speed.min.js
420 ms
lazysizes.min.js
421 ms
ls.unveilhooks.min.js
544 ms
setTheme.php
887 ms
cbk.css
743 ms
core.min.js
843 ms
kernel_main_v1.js
561 ms
dexie3.bundle.min.js
812 ms
core_ls.min.js
717 ms
core_frame_cache.min.js
716 ms
protobuf.min.js
828 ms
model.min.js
831 ms
rest.client.min.js
842 ms
pull.client.min.js
960 ms
auto_set_filter_h1.js
1007 ms
ajax.js
1008 ms
main.popup.bundle.min.js
1010 ms
template_536bd8cb22ac2505af9090e5a6dc390d_v1.js
1417 ms
default_21ab9e0bd0161a106ec4cc541ad2b0a6_v1.js
1014 ms
cbk.js
860 ms
ic72k44ku1obaeqcpvtlbin2ypo2ve8s.png
371 ms
logo.png
389 ms
I_oshkar_ola.png
397 ms
BJZtW_XXnw0_kv.jpg
411 ms
oka_314x314.jpg
439 ms
oka_m2_1.png
507 ms
021_1_1.jpg
525 ms
logo_bravo.png
535 ms
dgud.jpg
551 ms
E30u7ou_TKc.jpg
576 ms
logo2.png
642 ms
arrows.svg
492 ms
header_icons.svg
505 ms
item_icons.svg
501 ms
social.svg
485 ms
payment.svg
537 ms
ba.js
283 ms
spread.php
837 ms
tag.js
844 ms
button.js
1819 ms
photo1707149494_3_.jpeg
142 ms
print.min.css
142 ms
bx_stat
186 ms
advert.gif
577 ms
1
133 ms
metr2.pro 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.
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
Links do not have a discernible name
metr2.pro 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
metr2.pro 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metr2.pro 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 Metr2.pro 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.
metr2.pro
Open Graph data is detected on the main page of Metr 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: