8.1 sec in total
674 ms
7.2 sec
262 ms
Welcome to royale-bintang.com homepage info - get ready to check Royale Bintang best content for Malaysia right away, or after learning these important things about royale-bintang.com
4-Star Hotel in KL…
Visit royale-bintang.comWe analyzed Royale-bintang.com page load time and found that the first response time was 674 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
royale-bintang.com performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value18.2 s
0/100
25%
Value18.3 s
0/100
10%
Value320 ms
76/100
30%
Value0.203
61/100
15%
Value17.3 s
4/100
10%
674 ms
1230 ms
1312 ms
763 ms
759 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 95% of them (57 requests) were addressed to the original Royale-bintang.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Query.yahooapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Royale-bintang.com.
Page size can be reduced by 793.9 kB (17%)
4.6 MB
3.8 MB
In fact, the total size of Royale-bintang.com 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. 20% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 25.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 13% 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 25.5 kB or 82% of the original size.
Potential reduce by 11.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. Royale Bintang images are well optimized though.
Potential reduce by 716.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 716.8 kB or 82% of the original size.
Potential reduce by 40.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. Royale-bintang.com needs all CSS files to be minified and compressed as it can save up to 40.1 kB or 80% of the original size.
Number of requests can be reduced by 36 (62%)
58
22
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royale Bintang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
royale-bintang.com
674 ms
www.royale-bintang.com
1230 ms
jquery-ui-1.10.3.custom.min.css
1312 ms
css.css
763 ms
general.css
759 ms
weather.css
517 ms
jMenu.jquery.css
533 ms
nivo-slider.css
765 ms
style.css
775 ms
colorbox.css
1078 ms
jquery-v1.9.1.js
2518 ms
jquery-v1.10.3.ui.js
2783 ms
jquery.simpleWeather-2.2.min.js
1031 ms
jMenu.jquery.js
1314 ms
jquery.nivo.slider.js
1542 ms
captify.tiny.js
1342 ms
jcarousellite_1.0.1.pack.js
1554 ms
g_analytics.js
1571 ms
jquery.jcarousel.min.js
1609 ms
jquery.placeholder.js
1553 ms
wr_widgetcontrol.js
1845 ms
jquery.colorbox.js
1860 ms
ga.js
68 ms
header_bg.jpg
259 ms
yql
72 ms
RBKL_logo.png
252 ms
PDPA_icon.png
248 ms
phone_icon.png
268 ms
map_icon.png
260 ms
camera_icon.png
252 ms
video_icon.png
456 ms
career_icon.png
492 ms
fb_icon.png
499 ms
RBKL-QR-code_60px.jpg
501 ms
home_img01.jpg
2103 ms
home_img02.jpg
2153 ms
home_img03.jpg
2008 ms
home_img04.jpg
1503 ms
home_img05.jpg
1296 ms
home_img06.jpg
1283 ms
home_img07.jpg
2048 ms
prev_btn.png
1564 ms
home_promo01.jpg
1762 ms
home_promo02.jpg
1831 ms
home_promo03.jpg
2022 ms
home_promo04.jpg
2101 ms
home_promo05.jpg
2283 ms
next_btn.png
2294 ms
popup_mobile_app.jpg
2323 ms
overlay.png
2375 ms
controls.png
2369 ms
border.png
2449 ms
loading_background.png
2585 ms
loading.gif
2548 ms
www.royale-bintang.com
2574 ms
__utm.gif
15 ms
widgetMidcap.png
259 ms
input-shadow.png
254 ms
error_arrow_sprite.png
248 ms
calendar_icon.png
269 ms
royale-bintang.com 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
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
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.
royale-bintang.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
royale-bintang.com SEO score
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 Royale-bintang.com 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 Royale-bintang.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.
royale-bintang.com
Open Graph description is not detected on the main page of Royale Bintang. 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: