Tools & Wizards About Us
royalr.com screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

royalr.com

Sanitary fittings, brass cable glands, earthing accessories, brass neutral link manufacturer

Page Load Speed

4.5 sec in total

First Response

894 ms

Resources Loaded

3.5 sec

Page Rendered

83 ms

royalr.com screenshot

About Website

Welcome to royalr.com homepage info - get ready to check Royalr best content right away, or after learning these important things about royalr.com

Royal Recycling Industries - We manufacture and export sanitary fittings, brass cable glands, earthing accessories and brass neutral link.

Visit royalr.com

Key Findings

We analyzed Royalr.com page load time and found that the first response time was 894 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

royalr.com performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

royalr.com

894 ms

royalr.com

869 ms

royal_main.css

218 ms

top1.gif

221 ms

top2.jpg

657 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that all of those requests were addressed to Royalr.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Royalr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.2 kB (5%)

Content Size

169.6 kB

After Optimization

160.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Royalr.com main page is 169.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 158.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 8.1 kB

  • Original 10.8 kB
  • After minification 9.6 kB
  • After compression 2.7 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 1.2 kB, which is 11% 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 8.1 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 1.1 kB

  • Original 158.4 kB
  • After minification 157.4 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. Royalr images are well optimized though.

CSS Optimization

-14%

Potential reduce by 52 B

  • Original 379 B
  • After minification 379 B
  • After compression 327 B

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. Royalr.com needs all CSS files to be minified and compressed as it can save up to 52 B or 14% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

  • Images
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Royalr. According to our analytics all requests are already optimized.

Network Requests Diagram

royalr.com

royalr.com

894 ms

royalr.com

royalr.com

869 ms

royal_main.css

royal_main.css

218 ms

top1.gif

top1.gif

221 ms

top2.jpg

top2.jpg

657 ms

top3.gif

top3.gif

660 ms

topmenubg.jpg

topmenubg.jpg

656 ms

topbg1.jpg

topbg1.jpg

663 ms

bvqi_logo.jpg

bvqi_logo.jpg

662 ms

topbg.gif

topbg.gif

666 ms

top4.jpg

top4.jpg

1105 ms

top5.jpg

top5.jpg

1089 ms

topdbg.jpg

topdbg.jpg

882 ms

bullet3.gif

bullet3.gif

881 ms

top1bg.jpg

top1bg.jpg

880 ms

top6.jpg

top6.jpg

888 ms

prod-menu.jpg

prod-menu.jpg

1114 ms

1.jpg

1.jpg

1119 ms

2.jpg

2.jpg

1120 ms

3.jpg

3.jpg

1116 ms

4.jpg

4.jpg

1313 ms

5.jpg

5.jpg

1326 ms

6.jpg

6.jpg

1337 ms

7.jpg

7.jpg

1347 ms

8.jpg

8.jpg

1340 ms

9.jpg

9.jpg

1346 ms

10.jpg

10.jpg

1533 ms

bg.jpg

bg.jpg

1546 ms

Accessibility Review

royalr.com accessibility score

64

Accessibility Issues

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

<object> elements do not have alternate text

Best Practices

royalr.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

royalr.com SEO score

58

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

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalr.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 Royalr.com main page’s claimed encoding is windows-1252. 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

royalr.com

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