Website review, no card needed

compumuebles.com logo

compumuebles.com website review

Visit site (opens in a new tab)Reviewed 18 October 202628 issues · 80 checks

This review found 28 issues worth fixing on compumuebles.com, 9 of them high impact, across 80 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
2.7 s1.7 sApr 25Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.3 s
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.1 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
509 ms108 msApr 25Oct 10157 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026439 ms
May 2, 2026449 ms
May 9, 2026463 ms
May 16, 2026393 ms
May 23, 2026375 ms
May 30, 2026384 ms
Jun 6, 2026358 ms
Jun 13, 2026378 ms
Jun 20, 2026400 ms
Jun 27, 2026383 ms
Jul 4, 2026352 ms
Jul 11, 2026339 ms
Jul 18, 2026349 ms
Jul 25, 2026337 ms
Aug 1, 2026317 ms
Aug 8, 2026290 ms
Aug 15, 2026270 ms
Aug 22, 2026288 ms
Aug 29, 2026297 ms
Sep 5, 2026282 ms
Sep 12, 2026212 ms
Sep 19, 2026179 ms
Sep 26, 2026162 ms
Oct 3, 2026154 ms
Oct 10, 2026157 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 compumuebles.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. compumuebles.com at 0.4 s0.4 s
  2. compumuebles.com at 0.8 s0.8 s
  3. compumuebles.com at 1.1 s1.1 s
  4. compumuebles.com at 1.5 s1.5 s
  5. compumuebles.com at 1.9 s1.9 s
  6. compumuebles.com at 2.3 s2.3 s
  7. compumuebles.com at 2.6 s2.6 s
  8. compumuebles.com at 3.0 s3.0 s

Speed

6 to fix61
  • Reduce unused JavaScript

    2.3 s · 513 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Main-thread work: 2.5 s

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

  • 2,275 HTML elements

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

  • Google CDN adds 152 ms

    152 ms

    Google CDN costs a phone 152 ms of main-thread work and 295 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.

  • Shopify adds 112 ms

    112 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Shopify and mercadopago.com and others), adding 846 KiB and 288 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Render-blocking requests

    200 ms

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

  • Improve image delivery

    50 KiB

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

  • Use efficient cache lifetimes

    40 KiB

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

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

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 11.5 s

    11.5 s

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Total Blocking Time: 384 ms

    384 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Speed Index: 3.9 s

    3.9 s

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • 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 INP: 147 ms

    147 ms

    Real visitors wait 147 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.

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 699 ms

    699 ms

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

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

    -65%

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

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

    -12%

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

2 to fix81
  • Page weight: 2.7 MB in 272 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 272 requests on a phone: scripts 1,010 KiB (73), other files 797 KiB (112) and images 584 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Mesa_de_juntas_y_rober.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 0.8 g of CO₂ per visit

    0.75 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8391
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 6 text elements with low contrast

    6 text elements don'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.

  • 5 images without alt text

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

1 to fixGoogle 9295
  • Meta description is long (292 characters)

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

  • 159 internal links, 12 external

    The homepage links to 159 pages on compumuebles.com and 12 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Compumuebles”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “⇨ Compumuebles®️ | Fabricantes Sillas y Mobiliario Corporativo”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://compumuebles.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without a meta description

    https://compumuebles.com/blogs/proyectos has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 70 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 9687
  • 13 small tap targets

    13 of 30 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 “jQuery is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No opening hours

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

  • Phone number is not tap-to-call

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

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

    The homepage carries about 310 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 3 of them by other companies (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.

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on compumuebles.com, including 11 speed issues, 1 SEO issue 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