8.8 sec in total
651 ms
7.9 sec
231 ms
Click here to check amazing Royal Plaza content for Hong Kong. Otherwise, check out these important facts you probably never knew about royalplaza.com.hk
Discover the ultimate comfort and warm hospitality at Royal Plaza Hotel. Indulge in a luxurious stay and create unforgettable memories. Book Now!
Visit royalplaza.com.hkWe analyzed Royalplaza.com.hk page load time and found that the first response time was 651 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
royalplaza.com.hk performance score
name
value
score
weighting
Value14.7 s
0/100
10%
Value30.7 s
0/100
25%
Value28.2 s
0/100
10%
Value380 ms
70/100
30%
Value1.465
0/100
15%
Value27.6 s
0/100
10%
651 ms
660 ms
1060 ms
259 ms
520 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 84% of them (56 requests) were addressed to the original Royalplaza.com.hk, 3% (2 requests) were made to Code.jquery.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Royalplaza.com.hk.
Page size can be reduced by 667.8 kB (14%)
4.9 MB
4.3 MB
In fact, the total size of Royalplaza.com.hk main page is 4.9 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. 30% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 5.5 kB, which is 17% 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 24.9 kB or 78% of the original size.
Potential reduce by 156.0 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. Royal Plaza images are well optimized though.
Potential reduce by 473.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 473.8 kB or 76% of the original size.
Potential reduce by 13.1 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. Royalplaza.com.hk needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 60% of the original size.
Number of requests can be reduced by 25 (40%)
63
38
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal Plaza. 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 as a result speed up the page load time.
royalplaza.com.hk
651 ms
www.royalplaza.com.hk
660 ms
www.royalplaza.com.hk
1060 ms
base.css
259 ms
layout.css
520 ms
jquery-ui.css
23 ms
jquery.js
1117 ms
jquery-ui.js
1564 ms
kv.js
787 ms
common.js
788 ms
bg_header.jpg
265 ms
pic_logo.png
276 ms
icon.jpg
279 ms
channel-3-0_eng.png
273 ms
icon_dot.png
270 ms
channel-4-0_eng.png
277 ms
channel-6-0_eng.png
505 ms
channel-7-0_eng.png
522 ms
channel-36-0_eng.png
546 ms
channel-5-0_eng.png
541 ms
channel-8-0_eng.png
542 ms
btn_book_1.png
549 ms
icon_left.png
764 ms
icon_right.png
781 ms
signup_hd_eng.png
813 ms
login_btn_eng.png
811 ms
signup_md_eng.png
824 ms
join_btn_eng.png
823 ms
signup_ed_eng.png
1024 ms
content-2-image_eng.png
2554 ms
content-119-image_eng.png
2353 ms
content-120-image_eng.png
2981 ms
content-121-image_eng.png
2824 ms
content-122-image_eng.png
3052 ms
content-456-image_eng.png
2982 ms
icon_left_gray.png
2621 ms
icon_right_gray.png
2824 ms
bg_pro_left.gif
2883 ms
icon_more2.png
3094 ms
content-419-left_image.jpg
3092 ms
bg_pro_right.gif
3140 ms
content-419-right_image.jpg
3249 ms
content-89-left_image.jpg
3250 ms
content-89-right_image.jpg
3319 ms
pic_hotel.jpg
3365 ms
bg_e_news.gif
3363 ms
like.php
228 ms
ga.js
75 ms
gtm.js
107 ms
ui-bg_flat_75_ffffff_40x100.png
8 ms
__utm.gif
19 ms
conversion_async.js
40 ms
37 ms
49 ms
vpc6VNjRPXV.js
65 ms
LVx-xkvaJ0b.png
67 ms
shkp_footer.php
3277 ms
bg_footer.jpg
3259 ms
TCPrintLogo2015.jpg
3257 ms
icon_e_news.png
3326 ms
icon_twitter.png
3367 ms
icon_weibo.png
3363 ms
icon_facebook.png
3268 ms
icon_more.png
3260 ms
btn_dot_active.png
3243 ms
btn_dot.png
3320 ms
shkp_logo.gif
386 ms
royalplaza.com.hk accessibility score
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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
royalplaza.com.hk 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
royalplaza.com.hk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Document doesn't have a valid hreflang
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalplaza.com.hk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Royalplaza.com.hk 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.
royalplaza.com.hk
Open Graph description is not detected on the main page of Royal Plaza. 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: