Tools & Wizards About Us
nemotile.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nemotile.com

Home | Nemo Tile + Stone

Page Load Speed

3.7 sec in total

First Response

376 ms

Resources Loaded

2.1 sec

Page Rendered

1.1 sec

nemotile.com screenshot

About Website

Welcome to nemotile.com homepage info - get ready to check Nemo Tile best content for United States right away, or after learning these important things about nemotile.com

A trusted advisor in tile and stone. Shop our vast array of porcelain, ceramic, and natural stone tiles online or visit one of our showrooms.

Visit nemotile.com

Key Findings

We analyzed Nemotile.com page load time and found that the first response time was 376 ms and then it took 3.3 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

nemotile.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value18.8 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value26.1 s

0/100

10%

Network Requests Diagram

nemotile.com

376 ms

d033a9b88bc5d8964ace1aeeb69ab8d9.min.css

125 ms

styles-l.min.css

248 ms

logo.svg

185 ms

ico-search.svg

216 ms

Our browser made a total of 153 requests to load all elements on the main page. We found that 84% of them (128 requests) were addressed to the original Nemotile.com, 14% (21 requests) were made to Prod-nemotile.s3.us-west-1.amazonaws.com and 1% (1 request) were made to Chimpstatic.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Prod-nemotile.s3.us-west-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 829.5 kB (12%)

Content Size

6.9 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nemotile.com main page is 6.9 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. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 442.1 kB

  • Original 477.6 kB
  • After minification 449.0 kB
  • After compression 35.4 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 442.1 kB or 93% of the original size.

Image Optimization

-5%

Potential reduce by 273.5 kB

  • Original 6.0 MB
  • After minification 5.8 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. Nemo Tile images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

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

CSS Optimization

-82%

Potential reduce by 111.0 kB

  • Original 135.8 kB
  • After minification 24.8 kB
  • After compression 24.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. Nemotile.com needs all CSS files to be minified and compressed as it can save up to 111.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 107 (74%)

Requests Now

145

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nemotile.com

nemotile.com

376 ms

d033a9b88bc5d8964ace1aeeb69ab8d9.min.css

d033a9b88bc5d8964ace1aeeb69ab8d9.min.css

125 ms

styles-l.min.css

styles-l.min.css

248 ms

logo.svg

logo.svg

185 ms

ico-search.svg

ico-search.svg

216 ms

MainLuceBanner-min-opti.jpg

MainLuceBanner-min-opti.jpg

601 ms

require.min.js

require.min.js

200 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

197 ms

mixins.min.js

mixins.min.js

196 ms

requirejs-config.min.js

requirejs-config.min.js

361 ms

8176c1fd0799323350e3eb6e8.js

8176c1fd0799323350e3eb6e8.js

26 ms

polyfill.min.js

polyfill.min.js

27 ms

CelineBanner4_1.jpg

CelineBanner4_1.jpg

621 ms

MobileCeline.jpg

MobileCeline.jpg

479 ms

YasmineBanner2.jpg

YasmineBanner2.jpg

621 ms

MOBILEYasmineBanner_1.jpg

MOBILEYasmineBanner_1.jpg

497 ms

Park_Avenue_Porcelain_Banner-min-optimize.jpg

Park_Avenue_Porcelain_Banner-min-optimize.jpg

622 ms

Leon_Arabescato_24x48_RS_01-min-optimize.jpg

Leon_Arabescato_24x48_RS_01-min-optimize.jpg

622 ms

KoriFeatured.jpg

KoriFeatured.jpg

638 ms

KoriFeaturedMobile.jpg

KoriFeaturedMobile.jpg

668 ms

FeaturedLeon1_2.jpg

FeaturedLeon1_2.jpg

686 ms

APOLLOFEATURED.jpg

APOLLOFEATURED.jpg

704 ms

MOBILEAPOLLO.jpg

MOBILEAPOLLO.jpg

700 ms

StoneProgramBanner3.jpg

StoneProgramBanner3.jpg

700 ms

05_Craftmenship_LDCMobile.jpg

05_Craftmenship_LDCMobile.jpg

774 ms

Contact.jpg

Contact.jpg

749 ms

Contact_1.jpg

Contact_1.jpg

772 ms

ico-login.svg

ico-login.svg

359 ms

ico-cart.svg

ico-cart.svg

360 ms

nemo-logo.svg

nemo-logo.svg

361 ms

ico-facebook.svg

ico-facebook.svg

362 ms

ico-instagram.svg

ico-instagram.svg

364 ms

ico-pinterest.svg

ico-pinterest.svg

363 ms

ico-twitter.svg

ico-twitter.svg

365 ms

Opus2.jpg

Opus2.jpg

511 ms

DylanNewCollections3.jpg

DylanNewCollections3.jpg

517 ms

MasaiTrendingTiles3.jpg

MasaiTrendingTiles3.jpg

528 ms

CoveTerraSustainable3.jpg

CoveTerraSustainable3.jpg

566 ms

Showroom_Ambient-5216_copy.jpg

Showroom_Ambient-5216_copy.jpg

603 ms

roboto-regular.woff

roboto-regular.woff

83 ms

roboto-medium.woff

roboto-medium.woff

83 ms

roboto-bold.woff

roboto-bold.woff

129 ms

neuehaasdisplayroman.woff

neuehaasdisplayroman.woff

181 ms

neuehaasdisplaylight.woff

neuehaasdisplaylight.woff

182 ms

neuehaasdisplaymedium.woff

neuehaasdisplaymedium.woff

183 ms

fbevents.js

fbevents.js

30 ms

jquery.min.js

jquery.min.js

156 ms

common.min.js

common.min.js

155 ms

dataPost.min.js

dataPost.min.js

191 ms

bootstrap.min.js

bootstrap.min.js

192 ms

app.min.js

app.min.js

192 ms

form-key-provider.min.js

form-key-provider.min.js

192 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

192 ms

theme.min.js

theme.min.js

184 ms

gtm.js

gtm.js

87 ms

hide.min.js

hide.min.js

211 ms

empty_cart_button.min.js

empty_cart_button.min.js

222 ms

domReady.min.js

domReady.min.js

225 ms

amscroll.min.js

amscroll.min.js

186 ms

jquery-mixin.min.js

jquery-mixin.min.js

63 ms

template.min.js

template.min.js

64 ms

confirm.min.js

confirm.min.js

68 ms

widget.min.js

widget.min.js

87 ms

main.min.js

main.min.js

83 ms

bootstrap.min.js

bootstrap.min.js

83 ms

text.min.js

text.min.js

119 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

121 ms

mage.min.js

mage.min.js

124 ms

types.min.js

types.min.js

134 ms

layout.min.js

layout.min.js

135 ms

wrapper.min.js

wrapper.min.js

87 ms

underscore.min.js

underscore.min.js

123 ms

translate.min.js

translate.min.js

127 ms

modal.min.js

modal.min.js

128 ms

knockout.min.js

knockout.min.js

122 ms

knockout-es5.min.js

knockout-es5.min.js

121 ms

engine.min.js

engine.min.js

123 ms

bootstrap.min.js

bootstrap.min.js

157 ms

observable_array.min.js

observable_array.min.js

162 ms

bound-nodes.min.js

bound-nodes.min.js

162 ms

scripts.min.js

scripts.min.js

174 ms

version.min.js

version.min.js

174 ms

js-translation.json

js-translation.json

155 ms

main.min.js

main.min.js

166 ms

registry.min.js

registry.min.js

170 ms

console-logger.min.js

console-logger.min.js

166 ms

modal-popup.html

modal-popup.html

132 ms

modal-slide.html

modal-slide.html

131 ms

modal-custom.html

modal-custom.html

147 ms

key-codes.min.js

key-codes.min.js

174 ms

core.min.js

core.min.js

179 ms

z-index.min.js

z-index.min.js

180 ms

observable_source.min.js

observable_source.min.js

171 ms

renderer.min.js

renderer.min.js

171 ms

knockout-repeat.min.js

knockout-repeat.min.js

157 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

183 ms

resizable.min.js

resizable.min.js

185 ms

i18n.min.js

i18n.min.js

186 ms

scope.min.js

scope.min.js

195 ms

range.min.js

range.min.js

196 ms

mage-init.min.js

mage-init.min.js

219 ms

keyboard.min.js

keyboard.min.js

241 ms

optgroup.min.js

optgroup.min.js

245 ms

after-render.min.js

after-render.min.js

247 ms

autoselect.min.js

autoselect.min.js

253 ms

datepicker.min.js

datepicker.min.js

254 ms

events.min.js

events.min.js

280 ms

outer_click.min.js

outer_click.min.js

298 ms

fadeVisible.min.js

fadeVisible.min.js

302 ms

collapsible.min.js

collapsible.min.js

306 ms

staticChecked.min.js

staticChecked.min.js

310 ms

simple-checked.min.js

simple-checked.min.js

311 ms

bind-html.min.js

bind-html.min.js

343 ms

tooltip.min.js

tooltip.min.js

358 ms

color-picker.min.js

color-picker.min.js

362 ms

arrays.min.js

arrays.min.js

314 ms

compare.min.js

compare.min.js

317 ms

misc.min.js

misc.min.js

318 ms

objects.min.js

objects.min.js

354 ms

strings.min.js

strings.min.js

367 ms

template.min.js

template.min.js

370 ms

local.min.js

local.min.js

375 ms

logger.min.js

logger.min.js

365 ms

entry-factory.min.js

entry-factory.min.js

366 ms

console-output-handler.min.js

console-output-handler.min.js

392 ms

formatter.min.js

formatter.min.js

373 ms

message-pool.min.js

message-pool.min.js

371 ms

levels-pool.min.js

levels-pool.min.js

379 ms

logger-utils.min.js

logger-utils.min.js

366 ms

data.min.js

data.min.js

366 ms

disable-selection.min.js

disable-selection.min.js

392 ms

focusable.min.js

focusable.min.js

373 ms

form.min.js

form.min.js

372 ms

ie.min.js

ie.min.js

374 ms

keycode.min.js

keycode.min.js

367 ms

labels.min.js

labels.min.js

368 ms

jquery-patch.min.js

jquery-patch.min.js

392 ms

plugin.min.js

plugin.min.js

373 ms

safe-active-element.min.js

safe-active-element.min.js

372 ms

safe-blur.min.js

safe-blur.min.js

373 ms

scroll-parent.min.js

scroll-parent.min.js

367 ms

tabbable.min.js

tabbable.min.js

370 ms

unique-id.min.js

unique-id.min.js

392 ms

class.min.js

class.min.js

373 ms

loader.min.js

loader.min.js

376 ms

async.min.js

async.min.js

371 ms

tooltip.html

tooltip.html

320 ms

spectrum.min.js

spectrum.min.js

322 ms

tinycolor.min.js

tinycolor.min.js

370 ms

entry.min.js

entry.min.js

302 ms

moment.min.js

moment.min.js

251 ms

dom-observer.min.js

dom-observer.min.js

62 ms

bindings.min.js

bindings.min.js

63 ms

Accessibility Review

nemotile.com accessibility score

90

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-hidden="true"] elements contain focusable descendents

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

nemotile.com SEO score

92

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

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

nemotile.com

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