base.net website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, hcaptcha.com and Facebook and others), adding 3.6 MB and 2.6 s of main-thread time.

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

hcaptcha.com costs a phone 912 ms of main-thread work and 1.2 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.

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

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

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

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

Facebook costs a phone 253 ms of main-thread work and 283 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.

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

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

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

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

7 KiB could be saved by minifying JavaScript.

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.

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.

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

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Running: Vuelve a Correr”.

Real visitors wait 248 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 176 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.5 MB in 405 requests on a phone: scripts 3.2 MB (193), other files 838 KiB (138) and images 739 KiB (39). Under 2 MB keeps phones on slow connections fast.

BANNER-MOBILE-Futblo.jpg 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).

1 image (32 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.

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

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

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

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

ARIA dialog and alertdialog nodes should 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: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 193 characters, so Google will cut it off around 60: “Base Tu tienda de Deportes de running, futbol, fitness, moda urbana, outdoor, natación, b…”.

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

The homepage links to 406 pages on base.net and 17 external pages.

There is no /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.

/pages/devoluciones is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343166449&tm=gtm002&Ver=2&mid=eb1f9381-08e3-418b-b5dc-fc2a8a01f539&bo=1&sid=1a3a06c0da8a11f1987ae77b47d8044d&vid=1a39fa70da8a11f1b662dd4d44cb250a&vids=1&msclkid=N&pi=9.

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

2 images are served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://base.net/customer_authentication/redirect?locale=es&region_country=ES.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

base.net is registered until Feb 2027. Make sure auto-renew is on and the card on file is current.

base.net has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

base.net's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 589 words of visible text.

DMARC is set to p=none, so mail pretending to be base.net is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 22 cookies, 1 of them by other companies (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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.