Website review, no card needed

xceramics.com logo

xceramics.com website review

Visit site (opens in a new tab)Reviewed 25 October 202648 issues · 94 checks

This review found 48 issues worth fixing on xceramics.com, 21 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.8 s1.3 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.4 s
May 30, 20262.9 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.2 s
Jul 4, 20262.6 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
110 ms64 msMay 2Oct 1776 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202686 ms
May 9, 202688 ms
May 16, 202692 ms
May 23, 202696 ms
May 30, 2026100 ms
Jun 6, 2026105 ms
Jun 13, 2026104 ms
Jun 20, 2026101 ms
Jun 27, 202696 ms
Jul 4, 202690 ms
Jul 11, 202685 ms
Jul 18, 202684 ms
Jul 25, 202681 ms
Aug 1, 202679 ms
Aug 8, 202676 ms
Aug 15, 202677 ms
Aug 22, 202678 ms
Aug 29, 202675 ms
Sep 5, 202677 ms
Sep 12, 202673 ms
Sep 19, 202671 ms
Sep 26, 202672 ms
Oct 3, 202669 ms
Oct 10, 202672 ms
Oct 17, 202676 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of xceramics.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. xceramics.com at 2.1 s2.1 s
  2. xceramics.com at 4.3 s4.3 s
  3. xceramics.com at 6.4 s6.4 s
  4. xceramics.com at 8.5 s8.5 s
  5. xceramics.com at 10.6 s10.6 s
  6. xceramics.com at 12.8 s12.8 s
  7. xceramics.com at 14.9 s14.9 s
  8. xceramics.com at 17.0 s17.0 s

Speed

13 to fix55
  • Use efficient cache lifetimes

    59.2 s · 14.1 MB

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

  • Improve image delivery

    22.0 s · 5.0 MB

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

  • Render-blocking requests

    23.1 s

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

  • Reduce unused CSS

    12.3 s · 2.0 MB

    About 2.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 12.3 s faster on a phone.

  • Reduce unused JavaScript

    4.1 s · 925 KiB

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

  • Font display

    1.9 s

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

  • Document request latency

    950 ms · 154 KiB

    The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55 (desktop: 55). Pages that score under 90 lose visitors before the first paint.

  • Reduce initial server response time

    949 ms

    Reduce initial server response time. Google estimates savings of 949 ms on a phone.

  • Google Tag Manager adds 273 ms

    273 ms

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

  • Main-thread work: 2.6 s

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

  • 1,615 HTML elements

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

  • Server response: 1.0 s

    1.0 s

    Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google Maps and Google/Doubleclick Ads and others), adding 667 KiB and 374 ms of main-thread time.

  • Minify CSS

    150 ms · 56 KiB

    56 KiB could be saved by minifying CSS.

  • Minify JavaScript

    130 ms · 24 KiB

    24 KiB could be saved by minifying JavaScript.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    28 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 23.3 s

    23.3 s

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

  • Largest Contentful Paint: 84.4 s

    84.4 s

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

  • Speed Index: 39.2 s

    39.2 s

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

  • Time to Interactive: 85.5 s

    85.5 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 7 images without width and height

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

6 checks passed
  • Real-user INP: 157 ms

    157 ms

    Real visitors wait 157 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 15% faster for real visitors

    -15%

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

  • Largest content (LCP) got 14% faster for real visitors

    -14%

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

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

  • Total Blocking Time: 36 ms

    36 ms

    Scripts block the page for only 36 ms while loading. Good is under 200 ms.

Images and page weight

6 to fix19
  • Page weight: 14.9 MB in 151 requests

    14.9 MB

    Your homepage downloads 14.9 MB in 151 requests on a phone: images 10.5 MB (53), stylesheets 2.1 MB (39) and scripts 1.9 MB (42). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    3.6 MB

    3 images are downloaded at several times the size a phone draws them, for example AGMS_36006-HL_Sample-_Edit.jpg at 2,500 px wide, shown at 288 px. Resized copies would save about 3.6 MB.

  • 22 images in older formats

    22 images (7.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.

  • 16 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    ALEXANDER_white-300x186.png 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).

  • About 4.2 g of CO₂ per visit

    4.23 g

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

Accessibility

8 to fixGoogle 7689
  • 2 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

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

  • 16 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 form fields without a label

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

  • 4 links without text

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

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • Title is short (23 characters)

    Your title is only 23 characters: “Home - X Ceramics Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Projects”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 237 internal links, 5 external

    The homepage links to 237 pages on xceramics.com and 5 external pages.

5 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “Let the Italian spectacles of exoticness make a statement of intent with their allure on behalf of your style & decor.”.

  • Canonical URL set

    The canonical URL is https://xceramics.com/.

  • Structured data in place

    Structured data found: Article, Organization, Person, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://xceramics.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,233 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 pages without a meta description

    https://xceramics.com/product-category/x-monica/wall-tiles, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x60, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm/standard-wall-20x30cm, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm/20x30cm and https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm/20x30cm-punch-wall-tiles and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages slow to respond

    https://xceramics.com/x-monica, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x60, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm/20x30cm, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-20x30cm/20x30cm-punch-wall-tiles, https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-25x40cm and https://xceramics.com/product-category/x-monica/wall-tiles/wall-tiles-25x40cm/25x40cm and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

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

  • Thin social proof

    Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

  • No opening hours

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

  • No risk reducer

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

  • About 428 words of copy

    The homepage carries about 428 words of visible text.

4 checks passed
  • 21 calls to action

    The homepage has 21 calls to action, for example “Start search”, “Contact” and “Download E-Catalog”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 11 cookies set on arrival

    11

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

  • No consent tool detected

    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.

  • 9 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at xceramics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on xceramics.com, including 22 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25