4 sec in total
892 ms
2.7 sec
404 ms
Click here to check amazing Royalindiapalaceny content. Otherwise, check out these important facts you probably never knew about royalindiapalaceny.com
Visit royalindiapalaceny.comWe analyzed Royalindiapalaceny.com page load time and found that the first response time was 892 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
royalindiapalaceny.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value30.1 s
0/100
25%
Value24.7 s
0/100
10%
Value2,490 ms
4/100
30%
Value0.057
98/100
15%
Value36.9 s
0/100
10%
892 ms
44 ms
625 ms
823 ms
635 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 49% of them (64 requests) were addressed to the original Royalindiapalaceny.com, 38% (49 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Royalindiapalaceny.com.
Page size can be reduced by 1.9 MB (44%)
4.4 MB
2.5 MB
In fact, the total size of Royalindiapalaceny.com main page is 4.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 172.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 85.7 kB, which is 46% 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 172.6 kB or 93% of the original size.
Potential reduce by 37.1 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. Royalindiapalaceny images are well optimized though.
Potential reduce by 802.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 802.8 kB or 71% of the original size.
Potential reduce by 915.0 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. Royalindiapalaceny.com needs all CSS files to be minified and compressed as it can save up to 915.0 kB or 85% of the original size.
Number of requests can be reduced by 18 (29%)
63
45
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalindiapalaceny. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
royalindiapalaceny.com
892 ms
css2
44 ms
app.min.css
625 ms
fontawesome.min.css
823 ms
style.css
635 ms
quantity.css
217 ms
64 ms
44ce6a9f50.js
38 ms
bootstrap-icons.min.css
212 ms
scrollable-tabs.css
315 ms
js
60 ms
get-started
21 ms
50 ms
jquery-3.6.0.min.js
140 ms
app.min.js
732 ms
main.js
231 ms
scrollable-tabs.js
241 ms
move.min.js
308 ms
quantity.js
316 ms
css2
20 ms
css2
25 ms
webfontloader.js
49 ms
order.png
111 ms
product_details_1_1.jpg
112 ms
logo.png
109 ms
hero_bg_1_1.jpg
330 ms
hero_shape_4.png
108 ms
hero_shape_5.png
238 ms
hero_shape_6.png
239 ms
hero_shape_7.png
240 ms
hero_shape_8.png
240 ms
hero_shape_2.png
333 ms
hero_shape_3.png
332 ms
title_line.png
331 ms
dot_line.png
331 ms
dot_line_2.png
381 ms
hero_bg_1_2.jpg
431 ms
hero_bg_1_3.jpg
433 ms
hero_bg_phone_1_1.jpg
431 ms
hero_shape_2_2.png
429 ms
hero_bg_phone_1_2.jpg
432 ms
hero_bg_phone_1_3.jpg
482 ms
about_1_1.png
628 ms
title_icon.svg
534 ms
bg_shape_1.png
639 ms
6in.jpg
537 ms
7in.jpg
543 ms
8in.jpg
582 ms
9in.jpg
634 ms
10in.jpg
640 ms
red_chili.png
649 ms
why_1_1.png
683 ms
why_1_2.png
725 ms
feature_2_1.svg
733 ms
feature_2_2.svg
737 ms
quote_left.svg
741 ms
1in.jpg
719 ms
embed
207 ms
44ce6a9f50.css
29 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff
31 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8amvHZ47LTd9w_ak.woff
40 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aivHZ47LTd9w_ak.woff
71 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aOvHZ47LTd9w_ak.woff
72 ms
1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aqvHZ47LTd9w_ak.woff
72 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0UzdYPFkaVN.woff
74 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FWUUzdYPFkaVNA6w.woff
73 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FVUUzdYPFkaVNA6w.woff
73 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FU0UzdYPFkaVNA6w.woff
73 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FWkUzdYPFkaVNA6w.woff
74 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FUkUzdYPFkaVNA6w.woff
75 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0UzdYPFkaVN.woff
76 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FWUUzdYPFkaVNA6w.woff
76 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FVUUzdYPFkaVNA6w.woff
77 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FU0UzdYPFkaVNA6w.woff
78 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FWkUzdYPFkaVNA6w.woff
76 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FUkUzdYPFkaVNA6w.woff
77 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FV0UzdYPFkaVN.woff
102 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FWUUzdYPFkaVNA6w.woff
103 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FVUUzdYPFkaVNA6w.woff
103 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FU0UzdYPFkaVNA6w.woff
103 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FWkUzdYPFkaVNA6w.woff
103 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-h4-FUkUzdYPFkaVNA6w.woff
105 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FV0UzdYPFkaVN.woff
104 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FWUUzdYPFkaVNA6w.woff
104 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FVUUzdYPFkaVNA6w.woff
103 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FU0UzdYPFkaVNA6w.woff
102 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FWkUzdYPFkaVNA6w.woff
104 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FUkUzdYPFkaVNA6w.woff
105 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0UzdYPFkaVN.woff
106 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFWUUzdYPFkaVNA6w.woff
106 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFVUUzdYPFkaVNA6w.woff
105 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFU0UzdYPFkaVNA6w.woff
107 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFWkUzdYPFkaVNA6w.woff
105 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFUkUzdYPFkaVNA6w.woff
106 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0UzdYPFkaVN.woff
107 ms
font-awesome-css.min.css
18 ms
fa-brands-400.ttf
679 ms
fa-light-300.ttf
816 ms
fa-thin-100.ttf
836 ms
fa-regular-400.ttf
850 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFWUUzdYPFkaVNA6w.woff
73 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFVUUzdYPFkaVNA6w.woff
54 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFU0UzdYPFkaVNA6w.woff
40 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFWkUzdYPFkaVNA6w.woff
40 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFUkUzdYPFkaVNA6w.woff
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0UzdYPFkaVN.woff
41 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFWUUzdYPFkaVNA6w.woff
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFVUUzdYPFkaVNA6w.woff
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFU0UzdYPFkaVNA6w.woff
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFWkUzdYPFkaVNA6w.woff
39 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFUkUzdYPFkaVNA6w.woff
38 ms
BngRUXZGTXPUvIoyV6yN5-92w7CGwRuoefDo.woff
189 ms
BngMUXZGTXPUvIoyV6yN5-fN5qOr4xCC.woff
38 ms
fontawesome-webfont.woff
31 ms
fa-solid-900.ttf
1099 ms
2in.jpg
620 ms
3in.jpg
647 ms
leaf_1.png
736 ms
js
62 ms
leaf_2.png
668 ms
dot_bg_white.png
694 ms
dot_bg.png
709 ms
menu_bg_1.png
714 ms
why_bg_1.png
736 ms
feature_icon_bg.svg
761 ms
geometry.js
4 ms
search.js
18 ms
main.js
22 ms
testi_bg_1.png
741 ms
footer_bg_1.jpg
708 ms
royalindiapalaceny.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
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
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.
royalindiapalaceny.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
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
Missing source maps for large first-party JavaScript
royalindiapalaceny.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
EN
ZX
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalindiapalaceny.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 language. Our system also found out that Royalindiapalaceny.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.
royalindiapalaceny.com
Open Graph description is not detected on the main page of Royalindiapalaceny. 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: