ceramictechnics.com website review

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

26 files are served with short cache lifetimes, so returning visitors download them again (26.5 MB).

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

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

About 26 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

1 long task block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.

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

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

3 third-party services load with your homepage (Cloudflare, elfsight.com and Adobe TypeKit), adding 43 KiB and 15 ms of main-thread time.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.99 (75th percentile). Good is under 0.1.

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

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

The layout shifts by 0.64 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 39.8 MB in 77 requests on a phone: images 39.0 MB (23), scripts 465 KiB (24) and other files 278 KiB (23). Under 2 MB keeps phones on slow connections fast.

10 images weigh 36.5 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example LIVING_WhiteCarrera_SpinaChevron_08x24_BladeDown-3.png at 2,560 px wide, shown at 162 px. Resized copies would save about 24.9 MB.

21 images (39.0 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.

1 image further down the page (207 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 19 characters: “Home | Stone Source”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 256 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.

The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

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

A phone browser shows 306 words, but the HTML your server sends has only 48. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

1 error was logged to the browser console while the page loaded, for example “eapps.Platform throws: "Widget "35057f13-46b8-448b-824b-e068745aabb7" can`t be initialized because WIDGET_NOT_FOUND" wi…”.

Large scripts ship without source maps.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

stonesource.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.