3.1 sec in total
369 ms
2.3 sec
389 ms
Click here to check amazing Hotel Royal content. Otherwise, check out these important facts you probably never knew about hotel-royal.be
Royal Hotel De Panne; the 4th generation of hoteliers welcomes you to discover De Panne and the Belgian coast. Exclusive packages!
Visit hotel-royal.beWe analyzed Hotel-royal.be page load time and found that the first response time was 369 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
hotel-royal.be performance score
name
value
score
weighting
Value1.8 s
90/100
10%
Value9.0 s
1/100
25%
Value4.6 s
71/100
10%
Value580 ms
51/100
30%
Value0
100/100
15%
Value8.0 s
42/100
10%
369 ms
518 ms
333 ms
88 ms
240 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 43% of them (30 requests) were addressed to the original Hotel-royal.be, 43% (30 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (874 ms) belongs to the original domain Hotel-royal.be.
Page size can be reduced by 55.4 kB (1%)
4.6 MB
4.6 MB
In fact, the total size of Hotel-royal.be main page is 4.6 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. 60% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 52.6 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.2 kB, which is 19% 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 52.6 kB or 81% of the original size.
Potential reduce by 2.5 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 Royal images are well optimized though.
Potential reduce by 231 B
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 92 B
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-royal.be has all CSS files already compressed.
Number of requests can be reduced by 10 (28%)
36
26
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hotel Royal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hotel-royal.be
369 ms
hotel-royal.be
518 ms
333 ms
router.js
88 ms
routing
240 ms
ratebox.bundle.js
494 ms
jquery.min.js
56 ms
frontend.js
345 ms
b973792ac5.js
60 ms
logo.svg
258 ms
phone.svg
270 ms
22d739f0f6a85340f5e63a247371a636d3225157.jpg
747 ms
029414646fff2fe2310383d0771679260d268af6.jpg
654 ms
8738c7e6d877e21e42aa89830a23a9df5addf556.jpg
656 ms
fac42501825e570e82d7d3159a66a04cbe78fe60.jpg
710 ms
336eb1c7f8a403aacd8f53331e8d403171819c73.jpg
806 ms
4fe84f24d4cf8bb9ee23fbb6d078ab11c49e63a5.jpg
612 ms
239c03fdbc75059e15c177f4e1ee2f83f7a0851a.jpg
772 ms
c0dcf86e73df7916fcaa61ab2382b04db0e8ccd6.jpg
748 ms
785260edc2e7d007ad37974bc1be076a5447a20a.jpg
748 ms
53cf1d49f5a013503f773305b86b714cf69092e2.jpg
788 ms
check.svg
837 ms
crown.png
832 ms
image_2017-06-28-17-54-48_5953d14832cbc_newsletter.jpeg
840 ms
image_2017-06-28-18-00-47_5953d2afb4e97_direct-booking-pixels.jpg
871 ms
image_2017-06-28-17-47-20_5953cf8841ca3_faq-3.jpeg
874 ms
css
58 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQUwaEQXjM.woff
39 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjN_mQ.woff
43 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4vaVQUwaEQXjN_mQ.woff
44 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5OaVQUwaEQXjN_mQ.woff
44 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B5caVQUwaEQXjN_mQ.woff
43 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4iaVQUwaEQXjN_mQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4jaVQUwaEQXjN_mQ.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4saVQUwaEQXjN_mQ.woff
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQUwaEQXjN_mQ.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQUwaEQXjN_mQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQUwaEQXjM.woff
52 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjN_mQ.woff
50 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4vaVQUwaEQXjN_mQ.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5OaVQUwaEQXjN_mQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B5caVQUwaEQXjN_mQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4iaVQUwaEQXjN_mQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4jaVQUwaEQXjN_mQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4saVQUwaEQXjN_mQ.woff
51 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQUwaEQXjN_mQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQUwaEQXjN_mQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQUwaEQXjM.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjN_mQ.woff
63 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4vaVQUwaEQXjN_mQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5OaVQUwaEQXjN_mQ.woff
62 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x5caVQUwaEQXjN_mQ.woff
63 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4iaVQUwaEQXjN_mQ.woff
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4jaVQUwaEQXjN_mQ.woff
63 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4saVQUwaEQXjN_mQ.woff
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQUwaEQXjN_mQ.woff
64 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQUwaEQXjN_mQ.woff
62 ms
analytics.js
26 ms
update.min.js
58 ms
b973792ac5.css
39 ms
collect
17 ms
font-awesome-css.min.css
21 ms
fontawesome-webfont.woff
16 ms
frontend.css
88 ms
arrow-bordered.svg
86 ms
arrow.svg
94 ms
rhr.jpg
96 ms
pointer.svg
91 ms
fax.svg
92 ms
send.svg
103 ms
hotel-royal.be 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
hotel-royal.be 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
Page has valid source maps
hotel-royal.be SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotel-royal.be 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-royal.be 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-royal.be
Open Graph data is detected on the main page of Hotel Royal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: