Website review, no card needed

multicenter.com logo

multicenter.com website review

Visit site (opens in a new tab)Reviewed 20 November 202633 issues · 63 checks

This review found 33 issues worth fixing on multicenter.com, 13 of them high impact, across 63 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.8 s3.7 sMay 30Nov 143.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.5 s
Jun 20, 20264.5 s
Jun 27, 20264.3 s
Jul 4, 20264.3 s
Jul 11, 20264.2 s
Jul 18, 20264.3 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.7 s
Aug 15, 20264.5 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20264.3 s
Oct 24, 20264.1 s
Oct 31, 20264.1 s
Nov 7, 20263.9 s
Nov 14, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
259 ms194 msMay 30Nov 14206 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026235 ms
Jun 6, 2026239 ms
Jun 13, 2026244 ms
Jun 20, 2026251 ms
Jun 27, 2026235 ms
Jul 4, 2026233 ms
Jul 11, 2026229 ms
Jul 18, 2026231 ms
Jul 25, 2026242 ms
Aug 1, 2026233 ms
Aug 8, 2026223 ms
Aug 15, 2026208 ms
Aug 22, 2026202 ms
Aug 29, 2026204 ms
Sep 5, 2026205 ms
Sep 12, 2026213 ms
Sep 19, 2026205 ms
Sep 26, 2026202 ms
Oct 3, 2026204 ms
Oct 10, 2026203 ms
Oct 17, 2026205 ms
Oct 24, 2026204 ms
Oct 31, 2026203 ms
Nov 7, 2026201 ms
Nov 14, 2026206 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

6 to fix0
  • Fails Core Web Vitals for real visitors

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user INP: 214 ms

    214 ms

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

  • Real-user CLS: 0.18

    0.18

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

2 checks passed
  • Tap response (INP) got 14% faster for real visitors

    -14%

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

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

    -15%

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

Images and page weight

2 to fix63
  • Page weight: 5.7 MB

    5.7 MB

    Your homepage downloads 5.7 MB on a phone, 2.0 MB of it images (34%). Under 2 MB keeps phones on slow connections fast.

  • 27 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (30 KiB) is 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 1.6 g of CO₂ per visit

    1.62 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

7 to fix89
  • 89 buttons without a name

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

  • 19 tap targets too small

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 28 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 (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail 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.

2 checks passed
  • Every image has alt text

    All 123 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fix79
  • 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 XML sitemap

    No XML sitemap at https://www.multicenter.com.bo/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 182 internal links, 6 external

    The homepage links to 182 pages on multicenter.com and 6 external pages.

4 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Descubrí en Tienda Multicenter todo para tu hogar. Muebles, Tecnología, Decoración y más. Transformá tu espacio con nos…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Tienda Multicenter Online: ¡Juntos, hacemos de tu casa un hogar!”.

  • Canonical URL set

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

  • robots.txt in place

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

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    26%

    A phone browser shows 2,827 words, but the HTML your server sends has only 723. 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.

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

  • No llms.txt

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

6 to fix60
  • 1 page without a title

    https://www.multicenter.com/refrigerador-side-by-side-647l-con-instaview%E2%84%A2/p has no <title>, so Google invents the link text in results.

  • 4 linked pages hidden from search

    https://www.multicenter.com/658, https://www.multicenter.com/753, https://www.multicenter.com/673 and https://www.multicenter.com/614 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://www.multicenter.com/multicard and https://www.multicenter.com/multipuntos all use the title “Tienda Multicenter Online: ¡Juntos, hacemos de tu casa un hogar!”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.multicenter.com/multicard, https://www.multicenter.com/multipuntos, https://www.multicenter.com/658, https://www.multicenter.com/753, https://www.multicenter.com/673 and https://www.multicenter.com/614 and 9 others use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.multicenter.com/s, whose canonical is https://www.multicenter.com/s?map=ft. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.multicenter.com/multicard, https://www.multicenter.com/multipuntos, https://www.multicenter.com/s and https://www.multicenter.com/refrigerador-side-by-side-647l-con-instaview%E2%84%A2/p have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.multicenter.com/multipuntos, https://www.multicenter.com/refrigerador-side-by-side-647l-con-instaview%E2%84%A2/p and https://www.multicenter.com/mesa-plegable/p 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.

  • 2 pages slow to respond

    https://www.multicenter.com/s and https://www.multicenter.com/mesa-portatil-multiuso/p took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

Best practices

1 to fix93
  • 4 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    713 of 741 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • About 2,827 words of copy

    The homepage carries about 2,827 words of visible text.

  • Urgency cues

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

1 checks passed
  • Analytics in place

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 16 cookies set on arrival

    16

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 multicenter.com, 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 | Hotjar
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on multicenter.com, including 6 speed issues, 4 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