5asec.com website review

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

5 third-party services load with your homepage (Google Tag Manager, Google Maps and Google Analytics and others), adding 1.2 MB and 888 ms of main-thread time.

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

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

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

Google Tag Manager costs a phone 576 ms of main-thread work and 599 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 528 KiB of JavaScript is downloaded but never used on this page.

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

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

Google Maps costs a phone 267 ms of main-thread work and 383 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.

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

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

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 13.7 s. Good is under 3.8 s.

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

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tintorería de calidad”.

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

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

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

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

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

1 image 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' tap response (inp) went from 112 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.4 MB in 70 requests on a phone: scripts 1.1 MB (33), images 1.0 MB (18) and fonts 196 KiB (7). Under 2 MB keeps phones on slow connections fast.

9 images (736 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.

3 images further down the page (386 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 37 pages on 5asec.com and 44 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.

There is no https://www.5asec.com/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.

Your homepage links to https://www.5asec.com/en/node/14504, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and https://www.5asec.com/en all use the title “5àsec –The world’s leading dry cleaning franchise”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.5asec.com/fr has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.5asec.com/en/content/our-concept and https://www.5asec.com/en/dry-cleaning-laundry use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.5asec.com/en, whose canonical is https://www.5asec.com/en/content/homepage. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.5asec.com/en/content/join-worlds-leading-dry-cleaning-franchise and https://www.5asec.com/en/dry-cleaning-master-franchise have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot use 'in' operator to search for 'length' in true”.

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

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

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 homepage carries about 375 words of visible text.

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