systemaction.es website review

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

Klaviyo costs a phone 1.7 s of main-thread work and 3.5 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.

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

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

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

8 third-party services load with your homepage (Klaviyo, Google Tag Manager and konvoai.com and others), adding 6.2 MB and 2.3 s of main-thread time.

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

About 561 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

konvoai.com costs a phone 140 ms of main-thread work and 378 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.

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

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

About 69 KiB of CSS is downloaded but never applied on this page.

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

47 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 8.6 MB in 685 requests on a phone: other files 4.0 MB (498), images 2.4 MB (39) and scripts 1.7 MB (105). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example camisas_2_74197941-9bca-4505-a59c-9bb8345cfd3d.png at 1,795 px wide, shown at 195 px. Resized copies would save about 1.3 MB.

camisas_2_74197941-9bca-4505-a59c-9bb8345cfd3d.png weighs 798 KiB. On a phone connection a single image that size takes seconds.

1 image further down the page (91 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 2.44 g of CO₂e: 292.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

12 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 181 pages on systemaction.es and 1 external page.

/policies/shipping-policy, /collections/all, /collections/special-prices, /collections/bestsellers, /collections/new-in and /collections/activewear-collection and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/special-prices and /collections/activewear-collection have no <h1> headline, so visitors and search engines get no clear main topic.

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

10 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.

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

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.

systemaction.es 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.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

DMARC is set to p=none, so mail pretending to be systemaction.es is still delivered. Add a report address, check the reports, then move to quarantine.

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, Hotjar and Klaviyo and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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