Tools & Wizards About Us
royaltiles.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

royaltiles.com

Welcome to Royal Tiles

Page Load Speed

1 sec in total

First Response

170 ms

Resources Loaded

634 ms

Page Rendered

197 ms

royaltiles.com screenshot

About Website

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

Visit royaltiles.com

Key Findings

We analyzed Royaltiles.com page load time and found that the first response time was 170 ms and then it took 831 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

royaltiles.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

royaltiles.com

170 ms

style.css

69 ms

logo.jpg

74 ms

top-v-part-3.jpg

43 ms

welcome.jpg

73 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 61.4 kB (17%)

Content Size

362.2 kB

After Optimization

300.7 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Royaltiles.com main page is 362.2 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. 25% of websites need less resources to load. Images take 341.5 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 13.8 kB

  • Original 16.6 kB
  • After minification 13.3 kB
  • After compression 2.9 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 3.4 kB, which is 20% 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 13.8 kB or 83% of the original size.

Image Optimization

-13%

Potential reduce by 44.4 kB

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

CSS Optimization

-81%

Potential reduce by 3.2 kB

  • Original 4.0 kB
  • After minification 3.5 kB
  • After compression 759 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. Royaltiles.com needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (23%)

Requests Now

47

After Optimization

36

  • Images
  • CSS

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

Network Requests Diagram

royaltiles.com

royaltiles.com

170 ms

style.css

style.css

69 ms

logo.jpg

logo.jpg

74 ms

top-v-part-3.jpg

top-v-part-3.jpg

43 ms

welcome.jpg

welcome.jpg

73 ms

curve-top-line.jpg

curve-top-line.jpg

76 ms

curve-right-top.jpg

curve-right-top.jpg

75 ms

rightline.jpg

rightline.jpg

211 ms

curve-bot-line.jpg

curve-bot-line.jpg

81 ms

curve-bot-right.jpg

curve-bot-right.jpg

107 ms

green-line-1.jpg

green-line-1.jpg

114 ms

home_h.jpg

home_h.jpg

113 ms

menu_line.jpg

menu_line.jpg

111 ms

manufacturing.jpg

manufacturing.jpg

120 ms

contact.jpg

contact.jpg

145 ms

downloads.jpg

downloads.jpg

150 ms

products.jpg

products.jpg

154 ms

tiles_01.jpg

tiles_01.jpg

154 ms

tiles_02.jpg

tiles_02.jpg

193 ms

tiles_03.jpg

tiles_03.jpg

185 ms

tiles_04.jpg

tiles_04.jpg

223 ms

tiles_05.jpg

tiles_05.jpg

190 ms

tiles_06.jpg

tiles_06.jpg

190 ms

tiles_07.jpg

tiles_07.jpg

248 ms

tiles_08.jpg

tiles_08.jpg

231 ms

tiles_09.jpg

tiles_09.jpg

230 ms

tiles_10.jpg

tiles_10.jpg

269 ms

tiles_11.jpg

tiles_11.jpg

243 ms

tiles_12.jpg

tiles_12.jpg

258 ms

cat-1h.jpg

cat-1h.jpg

269 ms

cat-2.jpg

cat-2.jpg

267 ms

cat-3.jpg

cat-3.jpg

282 ms

cat-4.jpg

cat-4.jpg

285 ms

cat-5.jpg

cat-5.jpg

295 ms

cat-6.jpg

cat-6.jpg

306 ms

cat-7.jpg

cat-7.jpg

307 ms

site-viwe.jpg

site-viwe.jpg

306 ms

SITE-NAME.jpg

SITE-NAME.jpg

319 ms

cat-2h.jpg

cat-2h.jpg

39 ms

cat-3h.jpg

cat-3h.jpg

47 ms

cat-4h.jpg

cat-4h.jpg

39 ms

cat-5h.jpg

cat-5h.jpg

47 ms

cat-6h.jpg

cat-6h.jpg

44 ms

cat-7h.jpg

cat-7h.jpg

46 ms

manufacturing_h.jpg

manufacturing_h.jpg

78 ms

contact_h.jpg

contact_h.jpg

76 ms

downloads_h.jpg

downloads_h.jpg

77 ms

products_h.jpg

products_h.jpg

85 ms

Accessibility Review

royaltiles.com accessibility score

54

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.

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

royaltiles.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

royaltiles.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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

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

royaltiles.com

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