Tools & Wizards About Us
rigotile.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rigotile.com

Rigo Tile – Orlando and Kissimmee Florida

Page Load Speed

1.8 sec in total

First Response

205 ms

Resources Loaded

1.2 sec

Page Rendered

373 ms

rigotile.com screenshot

About Website

Visit rigotile.com now to see the best up-to-date Rigo Tile content and also check out these interesting facts you probably never knew about rigotile.com

Rigo Tile - Orlando and Kissimmee Florida

Visit rigotile.com

Key Findings

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

Performance Metrics

rigotile.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value3,090 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

rigotile.com

205 ms

js

70 ms

styles.css

123 ms

wpsm.css

154 ms

wppopups-base.css

160 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 74% of them (64 requests) were addressed to the original Rigotile.com, 7% (6 requests) were made to Google.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (437 ms) belongs to the original domain Rigotile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.5 kB (13%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rigotile.com main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 661.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 86.3 kB

  • Original 103.0 kB
  • After minification 101.5 kB
  • After compression 16.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. 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 86.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 156 B

  • Original 428.9 kB
  • After minification 428.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. Rigo Tile images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 58.8 kB

  • Original 661.4 kB
  • After minification 661.4 kB
  • After compression 602.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 43.2 kB

  • Original 217.9 kB
  • After minification 217.9 kB
  • After compression 174.7 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. Rigotile.com needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

78

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rigotile.com

rigotile.com

205 ms

js

js

70 ms

styles.css

styles.css

123 ms

wpsm.css

wpsm.css

154 ms

wppopups-base.css

wppopups-base.css

160 ms

be.min.css

be.min.css

259 ms

animations.min.css

animations.min.css

186 ms

fontawesome.min.css

fontawesome.min.css

196 ms

responsive.min.css

responsive.min.css

202 ms

mfn-local-fonts.css

mfn-local-fonts.css

184 ms

static.css

static.css

204 ms

dr.css

dr.css

214 ms

default.css

default.css

229 ms

css

css

28 ms

font-awesome.css

font-awesome.css

55 ms

rs6.css

rs6.css

109 ms

jquery.min.js

jquery.min.js

342 ms

jquery-migrate.min.js

jquery-migrate.min.js

244 ms

hooks.min.js

hooks.min.js

238 ms

wppopups.js

wppopups.js

233 ms

i18n.min.js

i18n.min.js

324 ms

index.js

index.js

324 ms

index.js

index.js

326 ms

rbtools.min.js

rbtools.min.js

155 ms

rs6.min.js

rs6.min.js

186 ms

wp-site-mapping.js

wp-site-mapping.js

325 ms

core.min.js

core.min.js

326 ms

tabs.min.js

tabs.min.js

327 ms

debouncedresize.min.js

debouncedresize.min.js

326 ms

magnificpopup.min.js

magnificpopup.min.js

328 ms

menu.min.js

menu.min.js

329 ms

visible.min.js

visible.min.js

329 ms

animations.min.js

animations.min.js

330 ms

enllax.min.js

enllax.min.js

379 ms

translate3d.min.js

translate3d.min.js

379 ms

scripts.min.js

scripts.min.js

437 ms

api.js

api.js

42 ms

wp-polyfill.min.js

wp-polyfill.min.js

437 ms

index.js

index.js

437 ms

dr.js

dr.js

436 ms

site-reviews.js

site-reviews.js

407 ms

rigo_logo.png

rigo_logo.png

168 ms

box_shadow.png

box_shadow.png

168 ms

dummy.png

dummy.png

56 ms

rigotile-25-years.png

rigotile-25-years.png

232 ms

RIGO-TILE-JOB-OPORTUNITY-1.jpg

RIGO-TILE-JOB-OPORTUNITY-1.jpg

301 ms

mapei.webp

mapei.webp

168 ms

floridatile.webp

floridatile.webp

233 ms

happytiles.webp

happytiles.webp

236 ms

masters.webp

masters.webp

236 ms

rubi.webp

rubi.webp

237 ms

southlands.webp

southlands.webp

237 ms

stones-and-more.webp

stones-and-more.webp

239 ms

proflex.webp

proflex.webp

238 ms

mosaic.webp

mosaic.webp

298 ms

merkrete.webp

merkrete.webp

298 ms

genesis.webp

genesis.webp

300 ms

embed

embed

254 ms

embed

embed

259 ms

daltile.webp

daltile.webp

255 ms

cortag.webp

cortag.webp

255 ms

baystone.webp

baystone.webp

257 ms

akua.webp

akua.webp

255 ms

mohawk-flooring.webp

mohawk-flooring.webp

255 ms

rigo-tile-mobile-cover.jpg

rigo-tile-mobile-cover.jpg

408 ms

stripes_10_w.png

stripes_10_w.png

254 ms

quote_bg.jpg

quote_bg.jpg

178 ms

icons.woff

icons.woff

315 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

65 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

65 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

67 ms

recaptcha__en.js

recaptcha__en.js

92 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

182 ms

js

js

178 ms

anchor

anchor

45 ms

styles__ltr.css

styles__ltr.css

6 ms

recaptcha__en.js

recaptcha__en.js

19 ms

geometry.js

geometry.js

71 ms

search.js

search.js

143 ms

main.js

main.js

145 ms

9JZxEp0LhtaE1v0GxppxYD-mM4N48uB2QPjHabq_eOY.js

9JZxEp0LhtaE1v0GxppxYD-mM4N48uB2QPjHabq_eOY.js

103 ms

webworker.js

webworker.js

99 ms

logo_48.png

logo_48.png

81 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

74 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

74 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

75 ms

recaptcha__en.js

recaptcha__en.js

17 ms

Accessibility Review

rigotile.com accessibility score

84

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

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

    EN

  • Encoding

    UTF-8

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

rigotile.com

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