Tools & Wizards About Us
royalbus.in screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

royalbus.in

Royal Travels

Page Load Speed

2.2 sec in total

First Response

162 ms

Resources Loaded

1.8 sec

Page Rendered

204 ms

royalbus.in screenshot

About Website

Click here to check amazing Royal Bus content for India. Otherwise, check out these important facts you probably never knew about royalbus.in

Royal Travels is the professional Travels dedicated to provide quality and timely service with an aim to meet the needs and desires of the customers. Royal Travels offers service with different models...

Visit royalbus.in

Key Findings

We analyzed Royalbus.in page load time and found that the first response time was 162 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

royalbus.in performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

royalbus.in

162 ms

www.royalbus.in

894 ms

jquery-lib-4f4c199de1f6be173fb7d2943bee9c97.css

167 ms

base_prod-0cea959c931a49ce779c7c6b74a559d5.css

169 ms

chosen-9f237d181c29d81e8747263bad480699.css

152 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Royalbus.in, 26% (15 requests) were made to Cdn-assets0.lin-north.ticketsimply.com and 21% (12 requests) were made to Cdn-assets2.lin-north.ticketsimply.com. The less responsive or slowest element that took the longest time to load (894 ms) belongs to the original domain Royalbus.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 858.7 kB (50%)

Content Size

1.7 MB

After Optimization

846.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royalbus.in main page is 1.7 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. 40% of websites need less resources to load. Javascripts take 806.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.6 kB

  • Original 46.7 kB
  • After minification 44.1 kB
  • After compression 10.1 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 36.6 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 62.3 kB

  • Original 662.6 kB
  • After minification 600.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. Royal Bus images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 611.4 kB

  • Original 806.2 kB
  • After minification 793.3 kB
  • After compression 194.9 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 611.4 kB or 76% of the original size.

CSS Optimization

-78%

Potential reduce by 148.5 kB

  • Original 189.6 kB
  • After minification 189.5 kB
  • After compression 41.2 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. Royalbus.in needs all CSS files to be minified and compressed as it can save up to 148.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (39%)

Requests Now

56

After Optimization

34

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal Bus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

royalbus.in

royalbus.in

162 ms

www.royalbus.in

www.royalbus.in

894 ms

jquery-lib-4f4c199de1f6be173fb7d2943bee9c97.css

jquery-lib-4f4c199de1f6be173fb7d2943bee9c97.css

167 ms

base_prod-0cea959c931a49ce779c7c6b74a559d5.css

base_prod-0cea959c931a49ce779c7c6b74a559d5.css

169 ms

chosen-9f237d181c29d81e8747263bad480699.css

chosen-9f237d181c29d81e8747263bad480699.css

152 ms

jquery-lib-21a3271d0fd62bece86915f4533dd515.js

jquery-lib-21a3271d0fd62bece86915f4533dd515.js

236 ms

ts_l10n_en-d531716cfd5c0686ba3975df27d372c5.js

ts_l10n_en-d531716cfd5c0686ba3975df27d372c5.js

140 ms

default-e36c87a2617d2a1b5564f59d2870f42d.css

default-e36c87a2617d2a1b5564f59d2870f42d.css

158 ms

alphacube-fa5b2a22e3438bb00f7d39b10a28f095.css

alphacube-fa5b2a22e3438bb00f7d39b10a28f095.css

158 ms

www_prod-2b37c4b9c9d1076607edf584a9911e2e.css

www_prod-2b37c4b9c9d1076607edf584a9911e2e.css

157 ms

debug-532b37dd0bc847e262e28d9d1b757b4f.css

debug-532b37dd0bc847e262e28d9d1b757b4f.css

157 ms

tablekit-style-d19aec0235eec3a34df95237995c72a3.css

tablekit-style-d19aec0235eec3a34df95237995c72a3.css

157 ms

jquery.fancybox-0941652ee406345972f2024a7b172767.css

jquery.fancybox-0941652ee406345972f2024a7b172767.css

157 ms

font-awesome-5b8ec28667c4b3a8c97c7f0d5e03f348.css

font-awesome-5b8ec28667c4b3a8c97c7f0d5e03f348.css

172 ms

elusive-webfont-9cdff80bb05f6ef262176598eac77ff5.css

elusive-webfont-9cdff80bb05f6ef262176598eac77ff5.css

218 ms

global.css

global.css

171 ms

public_app-6e914eb76562017485c6f550ffee1361.js

public_app-6e914eb76562017485c6f550ffee1361.js

278 ms

flexslider.css

flexslider.css

171 ms

jquery.flexslider-min-47a27d5bf4807ae2302b4f3ea89c4e41.js

jquery.flexslider-min-47a27d5bf4807ae2302b4f3ea89c4e41.js

105 ms

www_js_content.js

www_js_content.js

467 ms

print-1dfc5ffa518f48551318b72b44248a2a.css

print-1dfc5ffa518f48551318b72b44248a2a.css

95 ms

bg1.jpg

bg1.jpg

87 ms

bg_2.png

bg_2.png

138 ms

indicator-small-8d9d1090628b9000702b3c41cc54bd96.gif

indicator-small-8d9d1090628b9000702b3c41cc54bd96.gif

86 ms

fb.png

fb.png

74 ms

bus_car_packages-e02d3747c1732fa5611d5cc4fe52da03.png

bus_car_packages-e02d3747c1732fa5611d5cc4fe52da03.png

73 ms

agent.png

agent.png

73 ms

popup.jpg

popup.jpg

139 ms

indicator-94f2f6601840eca41d10b40bc5c166dd.gif

indicator-94f2f6601840eca41d10b40bc5c166dd.gif

70 ms

bus_8.png

bus_8.png

329 ms

bus_3.gif

bus_3.gif

239 ms

agent_registration-441302f30fd7fa6e6a997e27af28a270.png

agent_registration-441302f30fd7fa6e6a997e27af28a270.png

174 ms

close.png

close.png

84 ms

bus_6.gif

bus_6.gif

219 ms

bus_4.gif

bus_4.gif

153 ms

logo.png

logo.png

163 ms

bus_1.gif

bus_1.gif

231 ms

bus_2.gif

bus_2.gif

266 ms

overlay.png

overlay.png

70 ms

check.png

check.png

73 ms

ph_nos_new.png

ph_nos_new.png

102 ms

roundleft_bg.jpg

roundleft_bg.jpg

71 ms

quick_bg.png

quick_bg.png

72 ms

feature_bg.png

feature_bg.png

72 ms

bullet_icon.png

bullet_icon.png

70 ms

feature2.png

feature2.png

70 ms

feature6.png

feature6.png

74 ms

feature3.png

feature3.png

72 ms

feature4.png

feature4.png

75 ms

latest_news.png

latest_news.png

162 ms

feature1.png

feature1.png

71 ms

feature5.png

feature5.png

72 ms

chosen-sprite.png

chosen-sprite.png

69 ms

ui-bg_highlight-hard_100_f2f5f7_1x100.png

ui-bg_highlight-hard_100_f2f5f7_1x100.png

72 ms

calendar.gif

calendar.gif

71 ms

default.svg

default.svg

87 ms

bg_control_nav.png

bg_control_nav.png

38 ms

bg_direction_nav.png

bg_direction_nav.png

72 ms

Accessibility Review

royalbus.in accessibility score

90

Accessibility Issues

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

High

Document doesn't have a <title> element

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

royalbus.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

royalbus.in SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    _CHARSET

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalbus.in 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 Royalbus.in main page’s claimed encoding is _charset. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

royalbus.in

Open Graph description is not detected on the main page of Royal Bus. 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: