Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

royalsheet.com

Royal Sheet Metal

Page Load Speed

15 sec in total

First Response

7 sec

Resources Loaded

7.7 sec

Page Rendered

307 ms

royalsheet.com screenshot

About Website

Click here to check amazing Royal Sheet content. Otherwise, check out these important facts you probably never knew about royalsheet.com

Visit royalsheet.com

Key Findings

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

Performance Metrics

royalsheet.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value51.1 s

0/100

25%

SI (Speed Index)

Value23.3 s

0/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.216

58/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

royalsheet.com

7032 ms

style.min.css

138 ms

styles.css

47 ms

settings.css

63 ms

fontello.css

48 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 79% of them (61 requests) were addressed to the original Royalsheet.com, 17% (13 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Royalsheet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (78%)

Content Size

3.2 MB

After Optimization

712.9 kB

In fact, the total size of Royalsheet.com main page is 3.2 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. 70% of websites need less resources to load. CSS take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 56.0 kB

  • Original 73.6 kB
  • After minification 72.0 kB
  • After compression 17.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. 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 56.0 kB or 76% of the original size.

Image Optimization

-13%

Potential reduce by 28.3 kB

  • Original 223.1 kB
  • After minification 194.7 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. Obviously, Royal Sheet needs image optimization as it can save up to 28.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 796.6 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 309.3 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 796.6 kB or 72% of the original size.

CSS Optimization

-90%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.7 MB
  • After compression 191.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. Royalsheet.com needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (87%)

Requests Now

61

After Optimization

8

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

Accessibility Review

royalsheet.com accessibility score

74

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

royalsheet.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

royalsheet.com 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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Royalsheet.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Royalsheet.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

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