tanzite.com website review

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.

About 294 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

YouTube costs a phone 1.1 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

28 images could be 23.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 4.0 MB and 2.9 s of main-thread time.

Google Tag Manager costs a phone 744 ms of main-thread work and 728 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.

Facebook costs a phone 362 ms of main-thread work and 230 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.

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

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

Google CDN costs a phone 160 ms of main-thread work and 349 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.

chatway.app costs a phone 136 ms of main-thread work and 423 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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.

2 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 148.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TANZITE STONEDECKS YEAR END SALE Save 15% on all Tanzite pr…”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 59.0 MB in 428 requests on a phone: images 53.4 MB (113), scripts 3.9 MB (110) and other files 810 KiB (136). Under 2 MB keeps phones on slow connections fast.

32 images weigh 42.1 MB together. On a phone connection a single image that size takes seconds.

40 images are downloaded at several times the size a phone draws them, for example IMG_8958_b7abc977-ae36-41fb-879c-1b43f4537acf.jpg at 4,032 px wide, shown at 380 px. Resized copies would save about 38.9 MB.

40 images further down the page (45.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images (6.7 MB) 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 16.72 g of CO₂e: 2006.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

6 elements hidden from screen readers can still receive keyboard focus.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

139 images have no alt text, which hurts accessibility and image search.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 86 characters, so Google will cut it off around 60: “Stone Decking & Tiling | Patio Designing | Tanzite Stonedecks USA – Tanzite StoneDecks”.

24 links have no real href, so search engines can't follow them.

Structured data found (BuildingMaterialsStore, FAQPage, HowTo and Organization) but with 2 problems, for example “Service: missing name”.

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

Your <h1> is empty.

The homepage links to 138 pages on tanzite.com and 25 external pages.

There is no https://tanzite.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://tanzite.com/collections/shop-all, https://tanzite.com/pages/stonedecks, https://tanzite.com/pages/tanzite-stone-pavers-outdoor-flooring-blocks, https://tanzite.com/pages/tanzite-indoor-flooring-blocks, https://tanzite.com/pages/why-tanzite and https://tanzite.com/pages/build-and-price-landing and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tanzite.com/pages/stonedecks, https://tanzite.com/pages/build-and-price-landing, https://tanzite.com/pages/get-3d-design and https://tanzite.com/pages/find-an-installer have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 37 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=343112512&tm=shpfy_ui&Ver=2&mid=4dddbf78-d566-44a6-91d4-4f20ae30f449&bo=1&sid=00fcf530db8111f1b5348b361d16e3a0&vid=00fd0120db8111f187c6992ecd033bd6&vids=1&msclkid=N&pi.

5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 887 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 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 22 cookies, 3 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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.