sending.es website review

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

42 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.

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

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

Your mobile performance score is 62 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

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

3 images could be 534 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

6 third-party services load with your homepage (Google Tag Manager, Clarity and LinkedIn Ads and others), adding 581 KiB and 362 ms of main-thread time.

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

Polyfills for old browsers add 7 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.

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

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

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Rapidez, Flexibilidad, Proactividad, Seguridad”. Most of its time is element render delay (6.2 s).

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

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

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

3 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-24, real Chrome visitors' tap response (inp) went from 115 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.6 MB in 165 requests on a phone: media 8.7 MB (2), images 1.4 MB (35) and scripts 1.1 MB (76). Under 2 MB keeps phones on slow connections fast.

prueba1.jpg weighs 537 KiB. On a phone connection a single image that size takes seconds.

12 images (975 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example prueba1.jpg at 1,200 px wide, shown at 290 px. Resized copies would save about 255 KiB.

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

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

The homepage links to 55 pages on sending.es and 10 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://www.sending.es/delegaciones, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.sending.es/clientes is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://www.sending.es/ca, https://www.sending.es/en, https://www.sending.es/fr, https://www.sending.es/de and https://www.sending.es/pt-pt and 3 others all use the title “Sending | Transporte Urgente y Logística”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.sending.es/area-comercial, https://www.sending.es/servicios, https://www.sending.es/sectores, https://www.sending.es/clientes, https://www.sending.es/actualidad and https://www.sending.es/localiza-tu-envio have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sending.es/ca, https://www.sending.es/en, https://www.sending.es/fr, https://www.sending.es/de, https://www.sending.es/pt-pt and https://www.sending.es/nl and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.sending.es/ca, https://www.sending.es/en, https://www.sending.es/fr, https://www.sending.es/de, https://www.sending.es/pt-pt and https://www.sending.es/nl and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sending.es/ca, https://www.sending.es/en, https://www.sending.es/fr, https://www.sending.es/de, https://www.sending.es/pt-pt and https://www.sending.es/nl and 6 others took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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.

The homepage has only about 137 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (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 4 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.