4.8 sec in total
610 ms
3.6 sec
640 ms
Click here to check amazing Hotel Not content for United States. Otherwise, check out these important facts you probably never knew about hotelnothotel.com
Visit hotelnothotel.comWe analyzed Hotelnothotel.com page load time and found that the first response time was 610 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hotelnothotel.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value11.4 s
0/100
25%
Value7.6 s
26/100
10%
Value50 ms
100/100
30%
Value1.725
0/100
15%
Value7.9 s
43/100
10%
610 ms
186 ms
37 ms
95 ms
255 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 80% of them (40 requests) were addressed to the original Hotelnothotel.com, 6% (3 requests) were made to Node.hotelchamp.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Hotelnothotel.com.
Page size can be reduced by 893.8 kB (27%)
3.3 MB
2.4 MB
In fact, the total size of Hotelnothotel.com main page is 3.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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 45.7 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 45.7 kB or 79% of the original size.
Potential reduce by 63.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. Hotel Not images are well optimized though.
Potential reduce by 358.5 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 358.5 kB or 67% of the original size.
Potential reduce by 426.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. Hotelnothotel.com needs all CSS files to be minified and compressed as it can save up to 426.3 kB or 86% of the original size.
Number of requests can be reduced by 29 (66%)
44
15
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotel Not. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.hotelnothotel.com
610 ms
OSWtgamHHn.js
186 ms
css
37 ms
social_widget.css
95 ms
grid.css
255 ms
base.css
250 ms
layout.css
289 ms
shortcodes.css
301 ms
magnific-popup.css
254 ms
mediaelementplayer.css
258 ms
eenvoud_media_enfold_child_theme.css
380 ms
custom.css
281 ms
style.css
282 ms
layerslider.css
285 ms
jquery.js
571 ms
jquery-migrate.min.js
378 ms
avia-compat.js
377 ms
greensock.js
478 ms
layerslider.kreaturamedia.jquery.js
391 ms
layerslider.transitions.js
469 ms
css
64 ms
avia.js
567 ms
shortcodes.js
570 ms
jquery.magnific-popup.min.js
479 ms
mediaelement-and-player.min.js
656 ms
wp-mediaelement.js
568 ms
comment-reply.min.js
571 ms
wp-embed.min.js
659 ms
wp-emoji-release.min.js
482 ms
style.css
385 ms
logo-nieuw.png
209 ms
facebook.png
209 ms
twitter.png
208 ms
instagram.png
209 ms
Hotel_not_Hotel-Panorama.jpg
654 ms
HNH-Panorama.jpg
1082 ms
Tram-exterieur--710x400.jpg
657 ms
Boekenkasten-exterieur-51-710x400.jpg
705 ms
Crisis_free_zone-exterieur-13-710x400.jpg
767 ms
20150510-43-710x575.jpg
944 ms
analytics.js
7 ms
collect
20 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
186 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
189 ms
node.hotelchamp.com
618 ms
skin.css
625 ms
entypo-fontello.woff
574 ms
login
94 ms
relay.html
86 ms
print.css
96 ms
hotelnothotel.com 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.
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.
hotelnothotel.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hotelnothotel.com 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
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotelnothotel.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Hotelnothotel.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.
hotelnothotel.com
Open Graph description is not detected on the main page of Hotel Not. 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: