2.1 sec in total
291 ms
1.5 sec
283 ms
Welcome to booking.ru homepage info - get ready to check Booking best content right away, or after learning these important things about booking.ru
Исследуйте мир с Booking.com. Выгодно бронируйте дома, отели, авиабилеты, автомобили в аренду, такси и варианты досуга. Спланируйте поездку с любым бюджетом.
Visit booking.ruWe analyzed Booking.ru page load time and found that the first response time was 291 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
booking.ru performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value18.2 s
0/100
25%
Value11.5 s
5/100
10%
Value9,400 ms
0/100
30%
Value0
100/100
15%
Value41.1 s
0/100
10%
291 ms
699 ms
19 ms
20 ms
28 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Booking.ru, 94% (118 requests) were made to Cf.bstatic.com and 2% (2 requests) were made to T-cf.bstatic.com. The less responsive or slowest element that took the longest time to load (699 ms) relates to the external source Booking.com.
Page size can be reduced by 709.8 kB (17%)
4.3 MB
3.6 MB
In fact, the total size of Booking.ru main page is 4.3 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. Only a small number of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 547.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 547.9 kB or 74% of the original size.
Potential reduce by 13.8 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. Booking images are well optimized though.
Potential reduce by 4.0 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 144.0 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. Booking.ru needs all CSS files to be minified and compressed as it can save up to 144.0 kB or 31% of the original size.
Number of requests can be reduced by 104 (84%)
124
20
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Booking. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
booking.ru
291 ms
index.ru.html
699 ms
cookie-banner.min.js
19 ms
2454015045ef79168d452ff4e7f30bdadff0aa81.js
20 ms
d38a9d874d4c4bac6c489442cef0c7135425d51c.css
28 ms
22870d2036e5b5667d39fb7d0c2c8e937d5d2a13.css
26 ms
308436ca26aacf6a7553e4c0cf298d0f780727a2.css
26 ms
5b5ab8ab66a5ce3092875d0725122439c4f2dfdd.css
23 ms
f1558a6e9832a4eb8cfe1d3d14db176bd3564335.css
23 ms
cbee9157fcbcf162230935e5de55dfcd9e5d0bbe.css
67 ms
77204d4da4aa41b08b1a4062c8e66e4629550994.js
27 ms
bui-react-10.c420aaa2.css
35 ms
bui-react-10.fbd3f9fd.css
29 ms
bui-react-10.cc1a2f03.css
22 ms
bui-react-10.76b1441a.css
16 ms
client.086fb182.css
27 ms
97a643cd.36b9d962.chunk.css
13 ms
ace575b5.3ea391aa.chunk.css
40 ms
f141039c.de63d3a6.chunk.css
42 ms
9214bfa8.76fa4945.chunk.css
42 ms
f41dcaf5.5f39ca2c.chunk.css
41 ms
6b631c3f.181f477f.chunk.css
42 ms
63bff8e9.90b5ddad.chunk.css
43 ms
59306dc3.04fde248.chunk.css
44 ms
5f127cf4.233b280c.chunk.css
44 ms
782ad794.1d8387c3.chunk.css
45 ms
282e5b08.6944de76.chunk.css
46 ms
5b1239aa.f23cee9d.chunk.css
46 ms
2c6b580e.08a40216.chunk.css
46 ms
95a17449.5d55300b.chunk.css
53 ms
7943e0ea.901fff5f.chunk.css
47 ms
d8454389.6c5951cd.chunk.css
48 ms
c8637181.a07c7242.chunk.css
51 ms
ce4afa91.927ca964.chunk.css
49 ms
d9560671.b4c80676.chunk.css
49 ms
b9a82cb8.51b772b4.chunk.css
48 ms
cf2b0303.07149e19.chunk.css
51 ms
dc32f6b7.87b74b4f.chunk.css
54 ms
18cad957.74a6c7f6.chunk.css
53 ms
8067d7e4.74a6c7f6.chunk.css
52 ms
09fb2abd.0a49e52d.chunk.css
55 ms
da3d7717.02102274.chunk.css
54 ms
ebf8c3e3.6f0a5d8c.chunk.css
55 ms
3c29a897.9ece6ffb.chunk.css
56 ms
0d919837.c55d3a4b.chunk.css
57 ms
27bbaa9c.64c45311.chunk.css
59 ms
7e8161ba.6575fef7.chunk.css
56 ms
0acd2ada6c74d5dec978a04ea837952bdf050cd2.js
53 ms
e1e8c0e862309cb4caf3c0d5fbea48bfb8eaad42.js
49 ms
f62025e692b596dd53ecd1bd082dfd3197944c50.js
48 ms
fbcae784d6892aa3fae4c1e15c28b5c3283ca1fe.js
44 ms
1b7ad23c57ef9adf3f14622c75ac1fc03729d077.js
39 ms
dc47e909267b003253e56f08c6b6f6fe39a91317.js
40 ms
aae975495cc56436f4f59463b9ea4e594bdb102a.js
39 ms
1d69e13e40d03fc59f58d76b31735d5d8c37416a.js
37 ms
3ae2aaac8c7322f2908109b6a9e7446001225f2b.js
40 ms
8c409b90db8d2ce96d4f48a8b2eca3f43a705428.js
40 ms
bb527f09bccbc2a4a742f009d936be46fae8a613.js
65 ms
bui-react-10.ffe2bb5b.js
69 ms
bui-react-10.97917490.js
64 ms
bui-react-10.a9a5a8fd.js
68 ms
bui-react-10.24230d4c.js
66 ms
bui-react-10.399bb1ba.js
66 ms
bui-react-10.d27a7a9b.js
66 ms
remoteEntry.c51ff7ef.client.js
67 ms
b9a82cb8.012ceaba.chunk.js
67 ms
cf2b0303.aa365769.chunk.js
65 ms
dc32f6b7.2afd97aa.chunk.js
67 ms
remoteEntry.80362d78.client.js
68 ms
remoteEntry.4ac216d2.client.js
67 ms
18cad957.31ce4ff5.chunk.js
66 ms
8067d7e4.34e34b47.chunk.js
65 ms
remoteEntry.7043292f.client.js
66 ms
09fb2abd.5c5b9c81.chunk.js
67 ms
remoteEntry.da1cd6c3.client.js
66 ms
da3d7717.44130389.chunk.js
64 ms
ebf8c3e3.cfad0be8.chunk.js
65 ms
3c29a897.1dd3a2ac.chunk.js
66 ms
remoteEntry.d40e531c.client.js
65 ms
0d919837.a86b9b77.chunk.js
67 ms
remoteEntry.083e531b.client.js
65 ms
Ru@3x.png
108 ms
363658458.jpeg
203 ms
184698944.png
105 ms
bh_aw_cpg_main_image.b4347622.png
208 ms
27bbaa9c.c5aacec8.chunk.js
53 ms
GeniusGenericGiftBox.png
200 ms
350960127.jpeg
203 ms
remoteEntry.c78a4bf4.client.js
55 ms
7e8161ba.d55ad923.chunk.js
54 ms
bui-react-10.f57b971e.js
97 ms
client.384587f2.js
83 ms
4a89d2db.6c0ec4b3.chunk.js
54 ms
0a098284.ac996a30.chunk.js
54 ms
97a643cd.01d32545.chunk.js
79 ms
ace575b5.5802e43a.chunk.js
92 ms
f141039c.6efdff7f.chunk.js
96 ms
9214bfa8.8488bf3c.chunk.js
94 ms
f41dcaf5.16101826.chunk.js
71 ms
6b631c3f.a0188197.chunk.js
69 ms
63bff8e9.f5f16a6e.chunk.js
67 ms
59306dc3.8579a61a.chunk.js
160 ms
5f127cf4.27b63a1e.chunk.js
162 ms
782ad794.2279ec04.chunk.js
160 ms
282e5b08.96ed4ed2.chunk.js
159 ms
5b1239aa.2b26ba81.chunk.js
158 ms
2c6b580e.7b50450c.chunk.js
160 ms
95a17449.e8a50ec7.chunk.js
160 ms
7943e0ea.45b8f14b.chunk.js
161 ms
d8454389.1296e0f1.chunk.js
160 ms
c8637181.1bf1e47b.chunk.js
158 ms
ce4afa91.c6cb5ba6.chunk.js
160 ms
d9560671.9b83e9a0.chunk.js
157 ms
b700d9e3067c1186a3364012df4fe1c48ae6da44.png
158 ms
976919.jpg
166 ms
977409.jpg
160 ms
977437.jpg
162 ms
976708.jpg
159 ms
976884.jpg
158 ms
27c8d1832de6a3123b6ee45b59ae2f81b0d9d0d0.png
156 ms
f80e129541f2a952d470df2447373390f3dd4e44.png
157 ms
83ef7122074473a6566094e957ff834badb58ce6.png
159 ms
1c9191b6a3651bf030e41e99a153b64f449845ed.png
158 ms
a4b50503eda6c15773d6e61c238230eb42fb050d.png
158 ms
d59400a9e3fb1de83d0ecf952eef4e894acabc26.png
157 ms
promise-7.0.4.min.js
5 ms
booking.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 have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
booking.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
Missing source maps for large first-party JavaScript
booking.ru SEO score
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 Booking.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 Booking.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.
booking.ru
Open Graph data is detected on the main page of Booking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: