multimax.net website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Google CDN and others), adding 1.6 MB and 1.0 s of main-thread time.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

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

About 567 KiB of JavaScript is downloaded but never used on this page.

About 113 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.

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

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

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

rebuyengine.com costs a phone 166 ms of main-thread work and 668 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.

Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need.

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

40 KiB JavaScript is shipped twice across bundles.

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

1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Bocina Inalámbrica JBL Xtreme4 | Bluetooth | Waterproof | I…”. Most of its time is resource load delay (1.9 s).

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

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

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

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

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

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

Your homepage downloads 3.3 MB in 224 requests on a phone: scripts 1.4 MB (70), other files 791 KiB (96) and fonts 565 KiB (12). Under 2 MB keeps phones on slow connections fast.

1000x1000_SIN_CTA_PREVIEW.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).

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Your title is only 27 characters: “Tienda Online de Tecnología”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“Multimax”, “Monitores” and “Impresoras HP”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 440 pages on multimax.net and 2 external pages.

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.

https://www.multimax.net/collections/ofertas, https://www.multimax.net/collections/toners, https://www.multimax.net/collections/impresion, https://www.multimax.net/collections/disco-duro-interno/disco-duro-interno, https://www.multimax.net/collections/tipo_disco-duro-externo/discos-duros-externos and https://www.multimax.net/collections/almacenamiento have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.multimax.net/collections/disco-duro-interno/disco-duro-interno, whose canonical is https://www.multimax.net/collections/disco-duro-interno. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.multimax.net/collections/ofertas, https://www.multimax.net/collections/laptops, https://www.multimax.net/collections/desktops/desktops, https://www.multimax.net/collections/monitores, https://www.multimax.net/collections/impresoras and https://www.multimax.net/collections/tintas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.multimax.net/collections/ofertas, https://www.multimax.net/collections/tintas, https://www.multimax.net/collections/impresion and https://www.multimax.net/collections/almacenamiento 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.

https://www.multimax.net/collections/tintas, https://www.multimax.net/collections/toners and https://www.multimax.net/collections/impresion took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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

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.

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