Tools & Wizards About Us
royaltgroup.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

royaltgroup.com

Royal T Group - Home of LiHo, Nene Chicken and many F&B brands in Singapore

Page Load Speed

19.8 sec in total

First Response

1.1 sec

Resources Loaded

18.6 sec

Page Rendered

163 ms

royaltgroup.com screenshot

About Website

Visit royaltgroup.com now to see the best up-to-date Royal T Group content for Singapore and also check out these interesting facts you probably never knew about royaltgroup.com

Royal T Group is the parent company of a variety of F&B brands in Singapore, spanning more than 80 outlets in drink kiosks, cafes and restaurants island-wide.

Visit royaltgroup.com

Key Findings

We analyzed Royaltgroup.com page load time and found that the first response time was 1.1 sec and then it took 18.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

royaltgroup.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value51.8 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.609

10/100

15%

TTI (Time to Interactive)

Value10.5 s

24/100

10%

Network Requests Diagram

royaltgroup.com

1073 ms

js

55 ms

css

36 ms

bootstrap.css

458 ms

style.css

681 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original Royaltgroup.com, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (15.5 sec) belongs to the original domain Royaltgroup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 678.3 kB (6%)

Content Size

10.5 MB

After Optimization

9.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royaltgroup.com main page is 10.5 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. 45% of websites need less resources to load. Images take 9.9 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 34.3 kB

  • Original 39.1 kB
  • After minification 26.6 kB
  • After compression 4.8 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.5 kB, which is 32% 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 34.3 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 213.9 kB

  • Original 9.9 MB
  • After minification 9.6 MB

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 T Group images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 273.3 kB

  • Original 416.4 kB
  • After minification 337.9 kB
  • After compression 143.1 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 273.3 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 156.8 kB

  • Original 186.2 kB
  • After minification 163.9 kB
  • After compression 29.4 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. Royaltgroup.com needs all CSS files to be minified and compressed as it can save up to 156.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

55

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royal T Group. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

royaltgroup.com

royaltgroup.com

1073 ms

js

js

55 ms

css

css

36 ms

bootstrap.css

bootstrap.css

458 ms

style.css

style.css

681 ms

font-awesome.css

font-awesome.css

683 ms

owl.carousel.min.css

owl.carousel.min.css

686 ms

jquery.min.js

jquery.min.js

1144 ms

jquery-noconflict.js

jquery-noconflict.js

688 ms

jquery-migrate.min.js

jquery-migrate.min.js

694 ms

caption.js

caption.js

909 ms

jquery.min.js

jquery.min.js

1138 ms

jquery.min.js

jquery.min.js

28 ms

prrple.slider.js

prrple.slider.js

917 ms

owl.carousel.js

owl.carousel.js

917 ms

slick.js

slick.js

1163 ms

bootstrap.min.js

bootstrap.min.js

1140 ms

logo.png

logo.png

231 ms

Collage.jpg

Collage.jpg

1823 ms

Banner_Bornga.jpg

Banner_Bornga.jpg

1357 ms

Banner_NENE.jpg

Banner_NENE.jpg

15499 ms

Banner_Paiks.jpg

Banner_Paiks.jpg

1142 ms

Banner_GYMLT.jpg

Banner_GYMLT.jpg

1126 ms

Banner_SG.jpg

Banner_SG.jpg

1359 ms

Banner_Woo.jpg

Banner_Woo.jpg

1580 ms

Banner_wsm.jpg

Banner_wsm.jpg

1601 ms

Banner_RnF.jpg

Banner_RnF.jpg

1590 ms

Banner_SGTAGAN.jpg

Banner_SGTAGAN.jpg

2042 ms

arrow1.png

arrow1.png

1812 ms

arrow2.png

arrow2.png

1822 ms

devider.png

devider.png

1834 ms

1.png

1.png

2041 ms

2.png

2.png

2052 ms

3.png

3.png

2051 ms

4.png

4.png

2065 ms

9.png

9.png

2273 ms

10.png

10.png

2719 ms

liho.png

liho.png

2279 ms

nene-chicken.png

nene-chicken.png

2284 ms

nene.png

nene.png

2299 ms

Bornga.png

Bornga.png

2507 ms

bornga.png

bornga.png

2512 ms

our-pic1.png

our-pic1.png

2515 ms

paik-coffee.png

paik-coffee.png

2532 ms

paik-bimbim.png

paik-bimbim.png

2734 ms

paik-bimbim.png

paik-bimbim.png

2743 ms

8days.png

8days.png

2747 ms

gf.png

gf.png

2767 ms

tst.png

tst.png

2947 ms

mtj.png

mtj.png

2963 ms

footer-logo.png

footer-logo.png

2972 ms

devider2.png

devider2.png

2915 ms

bg.png

bg.png

2931 ms

font

font

17 ms

GothamBook.woff

GothamBook.woff

3174 ms

arrow3.png

arrow3.png

2067 ms

arrow4.png

arrow4.png

2064 ms

Accessibility Review

royaltgroup.com accessibility score

86

Accessibility Issues

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

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

royaltgroup.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

royaltgroup.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royaltgroup.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 Royaltgroup.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.

Social Sharing Optimization

royaltgroup.com

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