esquel.com website review

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

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

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

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

13 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.

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

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

6 third-party services load with your homepage (Facebook, Google Tag Manager and Cloudflare CDN and others), adding 476 KiB and 419 ms of main-thread time.

Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “As a knowledge-based innovation company, Esquel Group opera…”. Most of its time is element render delay (3.9 s).

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 7.0 MB in 127 requests on a phone: images 6.1 MB (52), scripts 738 KiB (38) and stylesheets 164 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

All page content should be contained by landmarks: 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.

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

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

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

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

Your title is only 12 characters: “Esquel Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

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

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 46 pages on esquel.com and 6 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 /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.

/sustainability, /information, /our-history, /sustainability-details/planet and /sustainability-details/people have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /zh-hans, whose canonical is /zh-hans/%E9%A6%96%E9%A1%B5. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/from-seed-to-shirt, /our-people, /sustainability, /integral, /information and /zh-hans and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/zh-hans and /zh-hant have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/integral, /zh-hans, /zh-hant, /our-history and /awards-certifications took over 3 s to send their HTML from our server.

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

5 images failed to load on a phone, for example https://esquel.com/.

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

6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.esquel.com/sites/all/themes/esquel/fonts/Gotham-Book.woff' from origin 'https://esquel.c…”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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

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

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

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.

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

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 1,057 words of visible text.

DMARC is set to p=none, so mail pretending to be esquel.com 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 Analytics, Google Tag Manager and Meta 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 5 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.