ottotiles.com website review

Calendly costs a phone 1.4 s of main-thread work and 3.2 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 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Calendly, Stripe and Hubspot and others), adding 4.1 MB and 2.1 s of main-thread time.

About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 1.4 MB of JavaScript is downloaded but never used on this page.

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

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

16 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Stripe costs a phone 323 ms of main-thread work and 303 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.

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

Shopify costs a phone 89 ms of main-thread work and 316 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.

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

16 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Your homepage downloads 13.2 MB in 230 requests on a phone: media 5.4 MB (1), scripts 2.8 MB (90) and images 2.7 MB (56). Under 2 MB keeps phones on slow connections fast.

terrena_collection-header.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).

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

8 buttons have no accessible name, so screen readers announce just “button”.

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

7 tap targets are too small or too close together to hit reliably with a finger.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

5 visible links have no text or label, so screen readers cannot say where they go.

Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 236 pages on ottotiles.com and 4 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://ottotiles.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://ottotiles.com/collections/kit-kat-zellige-tiles, https://ottotiles.com/collections/in-stock, https://ottotiles.com/pages/trade-program and https://ottotiles.com/pages/faq have no meta description, so Google writes the search snippet from whatever text it finds.

https://ottotiles.com/pages/trade-program has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'prepend')”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 5 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies (measured from a US location before any click).

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