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 392.2 kB (13%)
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 232.8 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 232.8 kB or 14% 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.
metropol-moscow.ru
91 ms
metropol-moscow.ru
779 ms
jquery-3.1.1.min.js
27 ms
js
109 ms
page_89628ad01481df5483aee7b40888d9b9_v1.css
498 ms
template_bdbff3f18f74985b9144bc2e9ea56e48_v1.css
734 ms
core.min.js
51 ms
protobuf.min.js
51 ms
model.min.js
476 ms
core_promise.min.js
48 ms
rest.client.min.js
60 ms
pull.client.min.js
62 ms
css
64 ms
slick.css
45 ms
script.js
61 ms
script.js
72 ms
jquery.arcticmodal-0.3.min.js
71 ms
jquery.cookie.js
74 ms
jquery.background-video.js
82 ms
run_video.js
83 ms
run_sliders.js
502 ms
style.css
92 ms
travelline-style.css
98 ms
email-decode.min.js
95 ms
jquery-migrate-1.2.1.min.js
107 ms
jquery-ui.min.js
109 ms
slick.min.js
666 ms
moment.js
123 ms
pikaday.js
135 ms
pikaday.jquery.js
146 ms
jquery.arcticmodal-0.3.min.js
156 ms
dynamic_adapt.js
167 ms
common.js
617 ms
WidgetEmbed-certificateOfExcellence
19883 ms
init.js
904 ms
js
89 ms
rontar_aud_async.js
788 ms
main.js
905 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
87 ms
ba.js
288 ms
loader.js
937 ms
logo-pc.svg
23 ms
i-arrow-right.svg
459 ms
ie16dpvtd8dznw561ux5iob1chm85wt8.webp
949 ms
s7t4qmqb8v0ja1fjoz19ech9quusmlfj.webp
716 ms
57lqs201wue3omzrlp5qzf5vnsmw5k6u.webp
25 ms
h18onfyc19h1sgo57rzakh4dz4brpqf6.webp
796 ms
paytype.jpg
38 ms
6f7f35n2f51uzwd577xnj9q3dccy3xqx.jpg
939 ms
o5051i2bphz3k682mc8ueb78rci7qi8h.jpg
1100 ms
j9g2fclh14521lsj688dzykz5orrhhmi.jpg
1493 ms
23369a854d98e6fd0cc256ee926b64f2.jpg
1671 ms
affaf1841df97e8d30f3da434873d1a9.png
1355 ms
font
40 ms
font
387 ms
lodash.281ba93d.js
132 ms
core-js.e8830056.js
261 ms
axios.d7e89cc3.js
392 ms
ua-parser-js.59d4b581.js
394 ms
regenerator-runtime.3d4c54f2.js
394 ms
7392.5f35be5d.js
574 ms
loader.js
670 ms
2359.bbc50663.js
132 ms
ru
158 ms
i18next.adb435bc.js
307 ms
intl-pluralrules.e2b21a71.js
131 ms
react-dom.d76592b8.js
145 ms
1095.8983fef0.js
132 ms
9450.ef0776d2.js
303 ms
5051.b1e479af.js
304 ms
4313.d05628b1.js
303 ms
raven-js.ab29d237.js
302 ms
js
50 ms
host
144 ms
2068.c983257c.js
155 ms
6315-metropol-moscow
166 ms
search-form.371d9b2f.css
134 ms
booking_form_settings
205 ms
css
154 ms
3749.f20f3ac6.js
149 ms
nearest_available_dates
219 ms
3717.e7c3e576.js
150 ms
font
302 ms
7079.21440a7a.js
131 ms
724.19b0cc40.js
150 ms
2147.777076b6.js
132 ms
8517.c173a0c1.js
131 ms
datepicker.de52d2bd.css
132 ms
popover.91f0ecda.css
149 ms
host
156 ms
arrow-back.0503c107.svg
131 ms
arrow-forward.625f989c.svg
154 ms
hotel_booking_rules
265 ms
room_type_availability_2
383 ms
room_type_availability_2
475 ms
hotel_booking_rules
311 ms
config
271 ms
tl.js
154 ms
2084.79980ed0.js
132 ms
2617.0ce97af7.js
149 ms
index.6315.gc.html
136 ms
css
134 ms
css
239 ms
preloader.c9fd88d1.js
645 ms
styles.6315.c71e66b6.css
1008 ms
app_interface.js
150 ms
libs.1220a03c.js
1401 ms
app.d946c9a3.js
1510 ms
tl-fancybox.00303422.css
131 ms
tl-fancybox.86787f99.js
298 ms
8397.a879eb8b.js
149 ms
vendors.b3952f3aec2e300b37f9.bf3.ltr.css
131 ms
Rubik-Regular.8b95c501.woff
248 ms
font
266 ms
main.682f79a3f050c20c213c.js
131 ms
vendors.a48eef0426e542251c7f.js
393 ms
ru-ru.8d7cf391.js
202 ms
custom_messages
189 ms
all.606bff0f.svg
299 ms
rooms.227c56b8.js
131 ms
rooms.ddadfdfe.js
126 ms
search-filter.573a7a70.js
134 ms
search-filter.9e645b18.js
252 ms
parameters
250 ms
6315.css
131 ms
134.7f4f6beed1a3a8daa8c7.js
146 ms
941.cf3be451678eea14c310.js
131 ms
554.1efac3d5dc28a1e00ef8.js
189 ms
473.b3952f3aec2e300b37f9.bf3.ltr.css
258 ms
473.6bee0edfaf85feaa7d62.js
260 ms
93.d67ab4061f756dc9dc90.js
282 ms
338.b3952f3aec2e300b37f9.bf3.ltr.css
325 ms
338.265d99a30d25141527ba.js
330 ms
850.b3952f3aec2e300b37f9.bf3.ltr.css
367 ms
850.b0b218b1225357d0c670.js
381 ms
44.b3952f3aec2e300b37f9.bf3.ltr.css
386 ms
44.80a736ecb657d99dc824.js
421 ms
91.b3952f3aec2e300b37f9.bf3.ltr.css
470 ms
91.f72a8523ad142172fb69.js
475 ms
51.b3952f3aec2e300b37f9.bf3.ltr.css
494 ms
51.a0bb25b00c52211f0607.js
508 ms
310.b3952f3aec2e300b37f9.bf3.ltr.css
513 ms
310.5fe8730e7f644055a8d7.js
561 ms
428.b3952f3aec2e300b37f9.bf3.ltr.css
615 ms
428.56eb905c2ce7780c87da.js
620 ms
866.b3952f3aec2e300b37f9.bf3.ltr.css
621 ms
866.6f85da9848ca9eb907bc.js
635 ms
689.b3952f3aec2e300b37f9.bf3.ltr.css
640 ms
689.ac8cb507abc0401e3398.js
701 ms
643.b3952f3aec2e300b37f9.bf3.ltr.css
761 ms
643.9a9ae8593991b2900a3c.js
765 ms
519.b3952f3aec2e300b37f9.bf3.ltr.css
747 ms
519.aeea77cfec6ff8f5010f.js
761 ms
763.d1fc52a17692b6b4f0db.js
767 ms
572.b3952f3aec2e300b37f9.bf3.ltr.css
840 ms
572.10b71e103d7419fb606f.js
876 ms
581.b3952f3aec2e300b37f9.bf3.ltr.css
851 ms
899.b3952f3aec2e300b37f9.bf3.ltr.css
829 ms
957.b3952f3aec2e300b37f9.bf3.ltr.css
802 ms
3.b3952f3aec2e300b37f9.bf3.ltr.css
775 ms
832.b3952f3aec2e300b37f9.bf3.ltr.css
855 ms
342.b3952f3aec2e300b37f9.bf3.ltr.css
836 ms
462.b3952f3aec2e300b37f9.bf3.ltr.css
847 ms
278.b3952f3aec2e300b37f9.bf3.ltr.css
786 ms
58.b3952f3aec2e300b37f9.bf3.ltr.css
811 ms
200.b3952f3aec2e300b37f9.bf3.ltr.css
811 ms
563.b3952f3aec2e300b37f9.bf3.ltr.css
857 ms
695.b3952f3aec2e300b37f9.bf3.ltr.css
827 ms
10.b3952f3aec2e300b37f9.bf3.ltr.css
831 ms
581.5d5343ce621c179bafbf.js
803 ms
317.ade219db6da1e2d73d4a.js
834 ms
899.f2d75fd23bb24318896d.js
833 ms
957.dc665c0c979e613f8faa.js
859 ms
3.1a4aa1295fccb2c984d7.js
810 ms
832.4c9d8514ab235e14b6a7.js
816 ms
342.9ad594d8edd85aab14e3.js
803 ms
5.e747a0e963a32bbad03c.js
851 ms
462.b8c6e133cfb797e6ed67.js
850 ms
278.90b1ac6a3007c700b7cb.js
845 ms
58.30a36366c7d3b30c264b.js
805 ms
200.0429d48e6a0c0ced9831.js
798 ms
173.7d69c3e997f3ae4adf39.js
803 ms
563.42b8d6b3ab21b1446c46.js
871 ms
695.1017bc37576a11af6d19.js
868 ms
10.1ee346a0b5b03c77d524.js
829 ms
booking_form_settings
886 ms
common_info
859 ms
hotel_availability
2001 ms
hotel_info
976 ms
hotel_booking_rules
190 ms
gtm.js
70 ms
js
134 ms
analytics.js
52 ms
watch.js
1 ms
bx_stat
235 ms
d_client_new.js
661 ms
sprite.symbol.svg
84 ms
main.js
67 ms
ecommerce.js
73 ms
linkid.js
72 ms
collect
21 ms
collect
17 ms
collect
5 ms
collect
11 ms
collect
19 ms
js
49 ms
ga-audiences
174 ms
ga-audiences
164 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.
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: