Website review, no card needed

marcimex.com logo

marcimex.com website review

Visit site (opens in a new tab)Reviewed 17 November 202661 issues · 97 checks

This review found 61 issues worth fixing on marcimex.com, 30 of them high impact, across 97 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
5.0 s4.4 sMay 30Nov 144.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.6 s
Jun 6, 20264.6 s
Jun 13, 20264.5 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.6 s
Jul 11, 20264.7 s
Jul 18, 20264.7 s
Jul 25, 20264.7 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.8 s
Aug 22, 20264.8 s
Aug 29, 20264.9 s
Sep 5, 20264.9 s
Sep 12, 20264.9 s
Sep 19, 20264.9 s
Sep 26, 20264.8 s
Oct 3, 20264.9 s
Oct 10, 20264.9 s
Oct 17, 20264.9 s
Oct 24, 20264.8 s
Oct 31, 20264.7 s
Nov 7, 20264.6 s
Nov 14, 20264.5 s
Real-visitor tap response (INP)75th percentile, phones
299 ms230 msMay 30Nov 14291 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026238 ms
Jun 6, 2026242 ms
Jun 13, 2026247 ms
Jun 20, 2026251 ms
Jun 27, 2026249 ms
Jul 4, 2026248 ms
Jul 11, 2026250 ms
Jul 18, 2026251 ms
Jul 25, 2026253 ms
Aug 1, 2026256 ms
Aug 8, 2026258 ms
Aug 15, 2026265 ms
Aug 22, 2026271 ms
Aug 29, 2026276 ms
Sep 5, 2026276 ms
Sep 12, 2026270 ms
Sep 19, 2026270 ms
Sep 26, 2026271 ms
Oct 3, 2026273 ms
Oct 10, 2026277 ms
Oct 17, 2026277 ms
Oct 24, 2026280 ms
Oct 31, 2026287 ms
Nov 7, 2026286 ms
Nov 14, 2026291 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 marcimex.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. marcimex.com at 1.3 s1.3 s
  2. marcimex.com at 2.7 s2.7 s
  3. marcimex.com at 4.0 s4.0 s
  4. marcimex.com at 5.4 s5.4 s
  5. marcimex.com at 6.7 s6.7 s
  6. marcimex.com at 8.1 s8.1 s
  7. marcimex.com at 9.4 s9.4 s
  8. marcimex.com at 10.7 s10.7 s

Speed

12 to fix9
  • Use efficient cache lifetimes

    5.3 s · 3.9 MB

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

  • Reduce unused JavaScript

    4.3 s · 2.0 MB

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

  • Improve image delivery

    2.7 s · 688 KiB

    7 images could be 688 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.

  • vtexassets.com adds 1.4 s

    1.4 s

    vtexassets.com costs a phone 1.4 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 9

    9/100

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

  • Main-thread work: 8.9 s

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

  • 5,725 HTML elements

    The page has 5,725 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 (vtexassets.com, Google Tag Manager and TikTok and others), adding 4.5 MB and 2.7 s of main-thread time.

  • Google Tag Manager adds 680 ms

    680 ms

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

    600 ms · 93 KiB

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

  • 20 long tasks on the main thread

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

  • retailrocket.net adds 129 ms

    129 ms

    retailrocket.net costs a phone 129 ms of main-thread work and 691 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.

  • Minify JavaScript

    180 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 66 KiB

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

  • Render-blocking requests

    200 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.

  • Minify CSS

    30 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 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: 25 ms

    25 ms

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

Core Web Vitals

14 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 INP: 508 ms

    508 ms

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

  • Real-user CLS: 0.81

    0.81

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

  • Largest Contentful Paint: 27.7 s

    27.7 s

    Your largest element takes 27.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner principal de home 1”.

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 43.5 s

    43.5 s

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

  • Cumulative Layout Shift: 0.716

    0.716

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

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

    +20%

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

  • 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: 1.1 s

    1.1 s

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

  • 16 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    0%

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

Images and page weight

5 to fix18
  • Page weight: 22.6 MB in 704 requests

    22.6 MB

    Your homepage downloads 22.6 MB in 704 requests on a phone: images 17.5 MB (125), other files 2.3 MB (494) and scripts 2.2 MB (68). Under 2 MB keeps phones on slow connections fast.

  • 20 images far larger than shown

    5.0 MB

    20 images are downloaded at several times the size a phone draws them, for example 31152.png at 1,200 px wide, shown at 164 px. Resized copies would save about 5.0 MB.

  • 2 images over 500 KB

    2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

  • 22 images in older formats

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

  • 24 images below the first screen load straight away

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

  • About 6.4 g of CO₂ per visit

    6.41 g

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

Accessibility

11 to fixGoogle 7483
  • 8 buttons without a name

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

  • Images must have alternative text (5 elements)

    Images must have alternative text: 5 elements on the page fail this check, rated critical by axe-core.

  • 73 tap targets too small

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

  • Hidden but focusable

    14 elements hidden from screen readers can still receive keyboard focus.

  • 4 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

    11 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. (8 elements).

1 checks passed
  • 39 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: 39 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7774
  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Compra en Marcimex.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • 5 links crawlers can't follow

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

  • 21 internal links, 2 external

    The homepage links to 21 pages on marcimex.com and 2 external pages.

4 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Compra online y recibe a domicilio a todo el país. Encuentra televisores, tecnología, refrigeración, lavadoras, electro…”.

  • Canonical URL set

    The canonical URL is https://www.marcimex.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.marcimex.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    8%

    A phone browser shows 1,045 words, but the HTML your server sends has only 88. 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.marcimex.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 fix75
  • 6 pages without a title

    https://www.marcimex.com/ferreteria-herramientas-electricas-57246/p, https://www.marcimex.com/fitness-maquinas-de-ejercicios-57621/p, https://www.marcimex.com/electrodomesticos-encimeras-54898/p, https://www.marcimex.com/electrodomesticos-lavadora-automatica-57940/p, https://www.marcimex.com/tecnologia-celulares-y-smartphones-57909-57908-57907-57906/p and https://www.marcimex.com/electromenor-air-fryer-54819/p have no <title>, so Google invents the link text in results.

  • 6 pages without a meta description

    https://www.marcimex.com/ferreteria-herramientas-electricas-57246/p, https://www.marcimex.com/fitness-maquinas-de-ejercicios-57621/p, https://www.marcimex.com/electrodomesticos-encimeras-54898/p, https://www.marcimex.com/electrodomesticos-lavadora-automatica-57940/p, https://www.marcimex.com/tecnologia-celulares-y-smartphones-57909-57908-57907-57906/p and https://www.marcimex.com/electromenor-air-fryer-54819/p have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.marcimex.com/wishlist, https://www.marcimex.com/ferreteria-herramientas-electricas-57246/p, https://www.marcimex.com/fitness-maquinas-de-ejercicios-57621/p, https://www.marcimex.com/electrodomesticos-encimeras-54898/p, https://www.marcimex.com/electrodomesticos-lavadora-automatica-57940/p and https://www.marcimex.com/tecnologia-celulares-y-smartphones-57909-57908-57907-57906/p and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.marcimex.com/wishlist and https://www.marcimex.com/novedades 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.

  • 4 pages slow to respond

    https://www.marcimex.com/electrodomesticos-encimeras-54898/p, https://www.marcimex.com/audio-y-video/tv-y-video, https://www.marcimex.com/tecnologia and https://www.marcimex.com/muebles took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 19 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.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

5 to fixGoogle 5081
  • 71 small tap targets

    71 of 126 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…”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Cannot destructure property 'store' of '(intermediate value)' as it is undefined.”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 1,045 words of copy

    The homepage carries about 1,045 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Lg shop”.

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 23 cookies set on arrival

    23

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

  • 43 other companies contacted

    Loading the homepage contacts 43 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 marcimex.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
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on marcimex.com, including 26 speed issues, 5 SEO issues and 3 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