oasistile.com website review

20 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

About 365 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

The page has 3,156 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Klaviyo and others), adding 1.4 MB and 887 ms of main-thread time.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

13 files are served with short cache lifetimes, so returning visitors download them again (105 KiB).

A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Tag Manager costs a phone 252 ms of main-thread work and 359 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google CDN costs a phone 201 ms of main-thread work and 331 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Klaviyo costs a phone 130 ms of main-thread work and 306 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 18 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

8 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

4 KiB could be saved by minifying CSS.

Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “img”.

The page becomes fully interactive after 17.1 s. Good is under 3.8 s.

Visually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.9 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 380 ms in total while the page loads. Good is under 200 ms.

7 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 109 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.5 MB in 238 requests on a phone: images 3.0 MB (35), scripts 1.4 MB (95) and other files 636 KiB (73). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example pool8_c0b5f706-3839-4370-a53b-2b486c311170.png at 1,536 px wide, shown at 360 px. Resized copies would save about 1.2 MB.

contentonly_32.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images (527 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 1.55 g of CO₂e: 186.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 links inside paragraphs rely on colour alone to stand out.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h1 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 7 <h1> headlines (“”, “” and “Marble in motion”). One clear main headline is easier for people and search engines.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 531 pages on oasistile.com and 10 external pages.

Your homepage links to https://oasistile.com/pages/shop-by-material-old and https://oasistile.com/pages/shop-by-collection-old, which answer with an error. Visitors hit a dead end and search engines drop them.

https://oasistile.com/pages/oasis-tile-trade-program and https://oasistile.com/pages/about have no meta description, so Google writes the search snippet from whatever text it finds.

https://oasistile.com/pages/oasis-tile-trade-program, https://oasistile.com/pages/about, https://oasistile.com/collections/shop-all-tiles, https://oasistile.com/collections/glass-tiles, https://oasistile.com/collections/metal-tiles and https://oasistile.com/collections/stone-tiles and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=13007081&tm=gtm002&Ver=2&mid=7667ef2e-6017-4c3c-88cb-1f52f8ebdaf1&bo=1&sid=8b6cced0dc4a11f1889495118661f4a0&vid=8b6d05a0dc4a11f199b4c988f4c412c1&vids=1&msclkid=N&pi=91.

6 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://maxcdn.bootstrapcdn.com/font-awesome/4…”.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,394 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 19 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.