3.7 sec in total
89 ms
3.5 sec
115 ms
Visit hotel.wingo.com now to see the best up-to-date Hotel Wingo content for Colombia and also check out these interesting facts you probably never knew about hotel.wingo.com
Explore the world with Booking.com. Big savings on homes, hotels, flights, car rentals, taxis, and attractions – build your perfect trip on any budget.
Visit hotel.wingo.comWe analyzed Hotel.wingo.com page load time and found that the first response time was 89 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
hotel.wingo.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value3.5 s
63/100
25%
Value6.0 s
46/100
10%
Value1,050 ms
25/100
30%
Value0.002
100/100
15%
Value11.3 s
19/100
10%
89 ms
1653 ms
17 ms
20 ms
28 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Hotel.wingo.com, 84% (76 requests) were made to Cf.bstatic.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hotel.wingo.com.
Page size can be reduced by 436.5 kB (16%)
2.7 MB
2.3 MB
In fact, the total size of Hotel.wingo.com main page is 2.7 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 288.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. 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 288.5 kB or 69% of the original size.
Potential reduce by 5.7 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. Hotel Wingo 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 138.3 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. Hotel.wingo.com needs all CSS files to be minified and compressed as it can save up to 138.3 kB or 44% of the original size.
Number of requests can be reduced by 62 (75%)
83
21
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotel Wingo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
hotel.wingo.com
89 ms
hotel.wingo.com
1653 ms
cookie-banner.min.js
17 ms
2454015045ef79168d452ff4e7f30bdadff0aa81.js
20 ms
1c7a18e763aebb5ce09f31e59af1e8d8f6e925f5.css
28 ms
22870d2036e5b5667d39fb7d0c2c8e937d5d2a13.css
24 ms
308436ca26aacf6a7553e4c0cf298d0f780727a2.css
26 ms
5b5ab8ab66a5ce3092875d0725122439c4f2dfdd.css
26 ms
54fe2cfb6eeb8dbcd24c1d01e1a285ddcbe44ae4.css
26 ms
06c7fa1d9d82d53142e376e57a8b89e6c74869fc.css
22 ms
f1558a6e9832a4eb8cfe1d3d14db176bd3564335.css
27 ms
b14ffeed1466df127d194be5a63782d4eca33d2b.css
68 ms
0ae288b63736cf152c89300b0c6c4ff35db5cf68.css
82 ms
77204d4da4aa41b08b1a4062c8e66e4629550994.js
68 ms
bui-react-10.c420aaa2.css
7 ms
bui-react-10.fbd3f9fd.css
23 ms
bui-react-10.76b1441a.css
15 ms
bui-react-10.cc1a2f03.css
29 ms
client.086fb182.css
15 ms
5f127cf4.233b280c.chunk.css
22 ms
782ad794.1d8387c3.chunk.css
36 ms
css
91 ms
0acd2ada6c74d5dec978a04ea837952bdf050cd2.js
45 ms
e1e8c0e862309cb4caf3c0d5fbea48bfb8eaad42.js
45 ms
f62025e692b596dd53ecd1bd082dfd3197944c50.js
45 ms
b18b076010d5ee8178415747e3c7e6a3a6f14302.js
48 ms
1b7ad23c57ef9adf3f14622c75ac1fc03729d077.js
45 ms
f1c8c212c0149249fef02a562a6669d167bc56bc.js
47 ms
aae975495cc56436f4f59463b9ea4e594bdb102a.js
48 ms
1d69e13e40d03fc59f58d76b31735d5d8c37416a.js
47 ms
3ae2aaac8c7322f2908109b6a9e7446001225f2b.js
47 ms
8c409b90db8d2ce96d4f48a8b2eca3f43a705428.js
60 ms
layout_set_logo.png
26 ms
b2f01d4fd94cb1420fcdbbef62c06ade1026fbbd.png
23 ms
312c784f761fc4f1e315742e93b9fa10d96ea67d.jpg
24 ms
56cd199c9f53cba5ccd7667c3a1a196f95e60a10.png
23 ms
7b76b5d784449304b55bacdb5e3526741967b310.png
26 ms
c3dafe717a0b4b97e6ddd0d791e8a018d8f96310.png
25 ms
27c8d1832de6a3123b6ee45b59ae2f81b0d9d0d0.png
25 ms
f80e129541f2a952d470df2447373390f3dd4e44.png
24 ms
83ef7122074473a6566094e957ff834badb58ce6.png
28 ms
1c9191b6a3651bf030e41e99a153b64f449845ed.png
28 ms
a4b50503eda6c15773d6e61c238230eb42fb050d.png
28 ms
bb527f09bccbc2a4a742f009d936be46fae8a613.js
12 ms
bui-react-10.b7d83195.js
11 ms
bui-react-10.ffe2bb5b.js
79 ms
bui-react-10.ad5d3f46.js
15 ms
bui-react-10.a9a5a8fd.js
15 ms
bui-react-10.24230d4c.js
15 ms
bui-react-10.399bb1ba.js
86 ms
bui-react-10.d27a7a9b.js
82 ms
remoteEntry.47f3979e.client.js
82 ms
remoteEntry.80362d78.client.js
83 ms
remoteEntry.4ac216d2.client.js
82 ms
remoteEntry.887c2faa.client.js
85 ms
remoteEntry.da1cd6c3.client.js
85 ms
remoteEntry.54dee2c4.client.js
86 ms
remoteEntry.083e531b.client.js
86 ms
remoteEntry.c78a4bf4.client.js
85 ms
bui-react-10.f57b971e.js
94 ms
client.f25b5f4c.js
91 ms
4a89d2db.6c0ec4b3.chunk.js
86 ms
0a098284.ac996a30.chunk.js
86 ms
5f127cf4.8076c995.chunk.js
87 ms
782ad794.2279ec04.chunk.js
87 ms
1112ed285be95ce1db677062db0a57b279ff0ba8.js
88 ms
logo.png
87 ms
879406.jpg
67 ms
356224939.jpg
169 ms
241063304.jpg
67 ms
342826184.jpg
72 ms
844103.jpg
72 ms
d59400a9e3fb1de83d0ecf952eef4e894acabc26.png
70 ms
07ca5cacc9d77a7b50ca3c424ecd606114d9be75.svg
22 ms
fb6f63d62231f9fe552d79b5448620b2e63c726e.svg
23 ms
b2e5f2aa32b71ca0fc66aa671e4e958bcd69b7d0.svg
24 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
111 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
112 ms
ca3edd97ae7e70e02d4deab5e4f53caf934229e1.woff
93 ms
promise-7.0.4.min.js
14 ms
index.en-gb.html
729 ms
analytics.js
41 ms
logo
119 ms
js_errors
391 ms
11d2b12d25c970340e0e5c5707da66ac8223126e.js
49 ms
js_errors
419 ms
ec.js
40 ms
collect
13 ms
collect
25 ms
hotel.wingo.com 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 IDs are not unique
hotel.wingo.com 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
hotel.wingo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotel.wingo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hotel.wingo.com 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.
hotel.wingo.com
Open Graph description is not detected on the main page of Hotel Wingo. 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: