21.9 sec in total
91 ms
21.5 sec
338 ms
Visit metropol-moscow.ru now to see the best up-to-date Metropol Moscow content for Russia and also check out these interesting facts you probably never knew about metropol-moscow.ru
Отель Метрополь расположен на Театральном проезде в Москве. Рядом с отелем находятся станции метро Лубянка, Театральная и Площадь Революции. В 5 минутах ходьбы - Кремль, Красная Площадь и Большой теат...
Visit metropol-moscow.ruWe analyzed Metropol-moscow.ru page load time and found that the first response time was 91 ms and then it took 21.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
metropol-moscow.ru performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.4 s
10/100
25%
Value8.9 s
15/100
10%
Value2,270 ms
6/100
30%
Value0.251
49/100
15%
Value20.1 s
2/100
10%
91 ms
779 ms
27 ms
109 ms
498 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 22% of them (45 requests) were addressed to the original Metropol-moscow.ru, 60% (125 requests) were made to Ru-ibe.tlintegration.ru and 4% (9 requests) were made to Bf2gc.travellinecdn.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Tripadvisor.ru.
Page size can be reduced by 360.2 kB (12%)
3.0 MB
2.7 MB
In fact, the total size of Metropol-moscow.ru main page is 3.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. 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. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 68.5 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 12.0 kB, which is 14% 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 68.5 kB or 78% of the original size.
Potential reduce by 40.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. Metropol Moscow images are well optimized though.
Potential reduce by 200.9 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 200.9 kB or 12% of the original size.
Potential reduce by 50.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. Metropol-moscow.ru needs all CSS files to be minified and compressed as it can save up to 50.7 kB or 22% of the original size.
Number of requests can be reduced by 158 (79%)
200
42
The browser has sent 200 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Metropol Moscow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 113 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
metropol-moscow.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
metropol-moscow.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
metropol-moscow.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 Metropol-moscow.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 Metropol-moscow.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.
{{og_description}}
metropol-moscow.ru
Open Graph data is detected on the main page of Metropol Moscow. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: