fullsand.com website review

24 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and getbutton.io and others), adding 4.9 MB and 618 ms of main-thread time.

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

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

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

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

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

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

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

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

Desktop scores 81 but mobile only 48. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nueva Playera Fisher Fullsand para hombre con protección so…”.

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

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

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

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

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

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

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

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

Your homepage downloads 7.2 MB in 357 requests on a phone: images 4.3 MB (41), scripts 1.5 MB (111) and other files 1.0 MB (184). Under 2 MB keeps phones on slow connections fast.

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

16 images are downloaded at several times the size a phone draws them, for example NANO-BLOCK-FINAL_54e365d4-b9dd-47ea-9b06-fcfe6bc31faa.jpg at 1,242 px wide, shown at 374 px. Resized copies would save about 1.1 MB.

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

Banner-Cel_4_241eb11b-93c1-4148-9087-10a762f6b53f.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 (78 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.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

35 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 16 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 on the page fail this check, rated moderate by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “Fullsand® Tienda Online | Ropa con Protección Solar y Trajes de Baño”.

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

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 243 pages on fullsand.com and 12 external pages.

/pages/suscribete, /blogs/compra-en-linea-y-recoger-en-tienda, /collections/lo-nuevo and /collections/playeras-fisher-para-hombre-con-prteccion-solar have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/suscribete and /blogs/fullsand have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Requests the notification permission on page load.

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://instagram.com/fullsand.

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.

fullsand.com 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.

fullsand.com'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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 639 words of visible text.

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 TikTok 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 14 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.