Website review, no card needed

decorceramica.com logo

decorceramica.com website review

Visit site (opens in a new tab)Reviewed 30 October 202654 issues · 90 checks

This review found 54 issues worth fixing on decorceramica.com, 19 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
4.4 s3.7 sMay 9Oct 244.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20263.9 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.8 s
Aug 8, 20263.8 s
Aug 15, 20263.9 s
Aug 22, 20264.0 s
Aug 29, 20264.2 s
Sep 5, 20264.3 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
336 ms261 msMay 9Oct 24282 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026289 ms
May 16, 2026284 ms
May 23, 2026283 ms
May 30, 2026291 ms
Jun 6, 2026301 ms
Jun 13, 2026313 ms
Jun 20, 2026322 ms
Jun 27, 2026325 ms
Jul 4, 2026327 ms
Jul 11, 2026327 ms
Jul 18, 2026322 ms
Jul 25, 2026321 ms
Aug 1, 2026321 ms
Aug 8, 2026316 ms
Aug 15, 2026314 ms
Aug 22, 2026309 ms
Aug 29, 2026294 ms
Sep 5, 2026284 ms
Sep 12, 2026276 ms
Sep 19, 2026270 ms
Sep 26, 2026273 ms
Oct 3, 2026271 ms
Oct 10, 2026274 ms
Oct 17, 2026281 ms
Oct 24, 2026282 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 decorceramica.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. decorceramica.com at 1.0 s1.0 s
  2. decorceramica.com at 2.1 s2.1 s
  3. decorceramica.com at 3.1 s3.1 s
  4. decorceramica.com at 4.2 s4.2 s
  5. decorceramica.com at 5.2 s5.2 s
  6. decorceramica.com at 6.3 s6.3 s
  7. decorceramica.com at 7.3 s7.3 s
  8. decorceramica.com at 8.4 s8.4 s

Speed

15 to fix23
  • Reduce unused JavaScript

    3.3 s · 880 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Document request latency

    1.1 s

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

  • Reduce initial server response time

    1.1 s

    Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

  • Mobile performance score: 23

    23/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and ZenDesk and others), adding 3.2 MB and 1.7 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 380 KiB

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

  • vtexassets.com adds 673 ms

    673 ms

    vtexassets.com costs a phone 673 ms of main-thread work and 1.7 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.

  • Improve image delivery

    350 ms · 373 KiB

    7 images could be 373 KiB 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.

  • Reduce unused CSS

    450 ms · 69 KiB

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

  • Legacy JavaScript

    450 ms · 57 KiB

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

  • Google Tag Manager adds 450 ms

    450 ms

    Google Tag Manager costs a phone 450 ms of main-thread work and 525 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: 3.5 s

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

  • ZenDesk adds 195 ms

    195 ms

    ZenDesk costs a phone 195 ms of main-thread work and 428 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.

  • Server response: 1.2 s

    1.2 s

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

  • 13 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

Core Web Vitals

13 to fix0
  • 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 CLS: 0.74

    0.74

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

  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Piso Laminado Estilo Madera”.

  • Time to Interactive: 20.8 s

    20.8 s

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

  • Cumulative Layout Shift: 0.683

    0.683

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

  • Speed Index: 9.5 s

    9.5 s

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

  • Total Blocking Time: 643 ms

    643 ms

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 257 ms

    257 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 841 ms

    841 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

Images and page weight

2 to fix75
  • Page weight: 3.5 MB in 154 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 154 requests on a phone: scripts 2.4 MB (68), images 660 KiB (26) and HTML 170 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    43 KiB

    1 image is downloaded at several times the size a phone draws it, for example 72ccd8f6-e07f-4275-a6a0-84540836407c___bf8107cab769be7b66d55 at 1,128 px wide, shown at 328 px. Resized copies would save about 43 KiB.

  • 2 images in older formats

    2 images (108 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.

  • 1 image below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

7 to fixGoogle 8790
  • 9 buttons without a name

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

  • 5 text elements with low contrast

    5 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)

    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 (4 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 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.

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

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 16 internal links, 1 external

    The homepage links to 16 pages on decorceramica.com and 1 external page.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Porcelanato, pisos y paredes para Baños y Cocinas. Distribuidor exclusivo de Porcelanosa y Kohler. Más de 34 años y 30 …”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Decorceramica | Porcelanato, Baños y Cocinas en Colombia”.

  • Canonical URL set

    The canonical URL is https://www.decorceramica.com/.

  • 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.decorceramica.com/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    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.

  • Some text only appears after JavaScript runs

    52%

    The HTML your server sends has 90 of the 172 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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

Other pages

3 to fix86
  • 4 linked pages hidden from search

    https://www.decorceramica.com/457, https://www.decorceramica.com/448, https://www.decorceramica.com/451 and https://www.decorceramica.com/450 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 8 pages share a meta description

    https://www.decorceramica.com/457, https://www.decorceramica.com/448, https://www.decorceramica.com/451, https://www.decorceramica.com/450, https://www.decorceramica.com/ducha-telefono-ecoflow-cromo/p and https://www.decorceramica.com/griferia-lvm-mc-baja-stalst-gunmetal/p and 2 others use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.decorceramica.com/cocinas, https://www.decorceramica.com/novedades and https://www.decorceramica.com/ofertas-mes have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.decorceramica.com/revestimientos-duros, https://www.decorceramica.com/banos and https://www.decorceramica.com/revestimientos-blandos have 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.

  • 6 pages slow to respond

    https://www.decorceramica.com/novedades, https://www.decorceramica.com/ofertas-mes, https://www.decorceramica.com/457, https://www.decorceramica.com/448, https://www.decorceramica.com/450 and https://www.decorceramica.com/ducha-telefono-ecoflow-cromo/p took over 3 s to send their HTML from our server.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 18 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • No social proof

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

  • No direct contact details

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

  • Only about 172 words

    The homepage has only about 172 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 decorceramica.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager | Hotjar
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on decorceramica.com, including 28 speed issues, 3 SEO issues and 5 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