Website review, no card needed

iperceramica.it logo

iperceramica.it website review

Visit site (opens in a new tab)Reviewed 31 October 202648 issues · 98 checks

This review found 48 issues worth fixing on iperceramica.it, 21 of them high impact, across 98 checks. The most urgent: improve image delivery. 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
2.4 s2.0 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
634 ms155 msMay 9Oct 24484 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026210 ms
May 16, 2026221 ms
May 23, 2026235 ms
May 30, 2026249 ms
Jun 6, 2026236 ms
Jun 13, 2026227 ms
Jun 20, 2026223 ms
Jun 27, 2026219 ms
Jul 4, 2026229 ms
Jul 11, 2026245 ms
Jul 18, 2026256 ms
Jul 25, 2026261 ms
Aug 1, 2026266 ms
Aug 8, 2026262 ms
Aug 15, 2026264 ms
Aug 22, 2026306 ms
Aug 29, 2026311 ms
Sep 5, 2026413 ms
Sep 12, 2026572 ms
Sep 19, 2026473 ms
Sep 26, 2026579 ms
Oct 3, 2026521 ms
Oct 10, 2026474 ms
Oct 17, 2026473 ms
Oct 24, 2026484 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 iperceramica.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. iperceramica.it at 1.5 s1.5 s
  2. iperceramica.it at 3.1 s3.1 s
  3. iperceramica.it at 4.6 s4.6 s
  4. iperceramica.it at 6.2 s6.2 s
  5. iperceramica.it at 7.7 s7.7 s
  6. iperceramica.it at 9.3 s9.3 s
  7. iperceramica.it at 10.8 s10.8 s
  8. iperceramica.it at 12.4 s12.4 s

Speed

11 to fix10
  • Improve image delivery

    3.3 s · 2.3 MB

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

  • Reduce unused JavaScript

    1.8 s · 1.9 MB

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

  • Main-thread work: 12.6 s

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

  • Mobile performance score: 10

    10/100

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

  • 9,409 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, adiacent.space and goresponsa.com and others), adding 3.3 MB and 1.4 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    250 ms · 881 KiB

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

  • Google Tag Manager adds 925 ms

    925 ms

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

  • Reduce unused CSS

    750 ms · 208 KiB

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

  • goresponsa.com adds 88 ms

    88 ms

    goresponsa.com costs a phone 88 ms of main-thread work and 2.0 MB 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.

  • Minify JavaScript

    150 ms · 32 KiB

    32 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    150 ms

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 69 ms

    69 ms

    Your server sent the HTML in 69 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 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 INP: 747 ms

    747 ms

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

  • Largest Contentful Paint: 20.5 s

    20.5 s

    Your largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Offerte del mese Iperceramica”.

  • Total Blocking Time: 6.0 s

    6.0 s

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

  • Time to Interactive: 38.4 s

    38.4 s

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

  • Cumulative Layout Shift: 0.883

    0.883

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Tap response (INP) got 122% slower for real visitors

    +122%

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

  • Real-user TTFB: 808 ms

    808 ms

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

  • 23 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

Images and page weight

3 to fix45
  • Page weight: 7.7 MB in 152 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 152 requests on a phone: scripts 3.5 MB (57), images 3.3 MB (50) and other files 383 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    homepage-ottobre-2026-it.jpg weighs 801 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (863 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.

  • About 2.2 g of CO₂ per visit

    2.17 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 8286
  • 64 text elements with low contrast

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

  • 6 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (8 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 3 links without text

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (16 elements).

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 8588
  • No H1 headline

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

  • 7 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 221 internal links, 13 external

    The homepage links to 221 pages on iperceramica.it and 13 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Leader in Italia per pavimenti, rivestimenti, sanitari, e arredo bagno. Scopri punti vendita, cataloghi, prezzi e offer…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Pavimenti, Rivestimenti, Sanitari e Arredo Bagno | IPERCERAMICA”.

  • Canonical URL set

    The canonical URL is https://www.iperceramica.it/.

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://www.iperceramica.it/asset/sitemap-index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.iperceramica.it/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.

3 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

3 to fix85
  • 4 pages without a meta description

    https://www.iperceramica.it/RESTOrderCalculate, https://www.iperceramica.it/it/ita/ordini-telefonici, https://www.iperceramica.it/it/ita/prezzi-sconti-artigiani-imprese-progettisti and https://www.iperceramica.it/it/ita/promo-sconto-iva-ottobre-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.iperceramica.it/it/ita/ordini-telefonici, whose canonical is https://www.iperceramica.it/it/ita/ordina-con-noi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.iperceramica.it/RESTOrderCalculate, https://www.iperceramica.it/it/ita/promo-sconto-iva-ottobre-2026, https://www.iperceramica.it/it/ita/offerte-del-mese and https://www.iperceramica.it/it/ita/negozi have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.iperceramica.it/RESTOrderCalculate has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://www.iperceramica.it/it/ita/gres-porcellanato took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 7785
  • 14 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://cdn.iperceramica.it/asset/images/menu/sconto-iva.ver?1793427718323' from origin 'https://ww…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • No opening hours

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

  • No map or directions link

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

  • 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 767 words of copy

    The homepage carries about 767 words of visible text.

4 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

  • 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

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

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 iperceramica.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Azure

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 iperceramica.it, including 22 speed issues, 2 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