Website review, no card needed

inditex.com logo

inditex.com website review

Visit site (opens in a new tab)Reviewed 26 October 202640 issues · 79 checks

This review found 40 issues worth fixing on inditex.com, 16 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.9 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.2 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
137 ms121 msMay 2Oct 17128 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026128 ms
May 9, 2026127 ms
May 16, 2026128 ms
May 23, 2026129 ms
May 30, 2026131 ms
Jun 6, 2026132 ms
Jun 13, 2026133 ms
Jun 20, 2026133 ms
Jun 27, 2026134 ms
Jul 4, 2026135 ms
Jul 11, 2026135 ms
Jul 18, 2026133 ms
Jul 25, 2026130 ms
Aug 1, 2026127 ms
Aug 8, 2026123 ms
Aug 15, 2026125 ms
Aug 22, 2026126 ms
Aug 29, 2026127 ms
Sep 5, 2026128 ms
Sep 12, 2026126 ms
Sep 19, 2026125 ms
Sep 26, 2026124 ms
Oct 3, 2026125 ms
Oct 10, 2026127 ms
Oct 17, 2026128 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of inditex.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. inditex.com at 0.6 s0.6 s
  2. inditex.com at 1.2 s1.2 s
  3. inditex.com at 1.8 s1.8 s
  4. inditex.com at 2.4 s2.4 s
  5. inditex.com at 3.1 s3.1 s
  6. inditex.com at 3.7 s3.7 s
  7. inditex.com at 4.3 s4.3 s
  8. inditex.com at 4.9 s4.9 s

Speed

8 to fix33
  • Reduce unused JavaScript

    2.8 s · 559 KiB

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

  • Font display

    1.4 s

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 33

    33/100

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

  • Improve image delivery

    975 KiB

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

  • Use efficient cache lifetimes

    600 ms · 122 KiB

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

  • Legacy JavaScript

    300 ms · 23 KiB

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

  • Google Tag Manager adds 129 ms

    129 ms

    Google Tag Manager costs a phone 129 ms of main-thread work and 305 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 on the page

    6 third-party services load with your homepage (Google Tag Manager, Optanon and jQuery CDN and others), adding 752 KiB and 267 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    21 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.6 s

    A phone's processor spends 1.6 s on main-thread work while loading, 690 ms of it running JavaScript. That is comfortably low.

  • Server response: 26 ms

    26 ms

    Your server sent the HTML in 26 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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-user CLS: 1.00

    1.00

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

  • Cumulative Layout Shift: 1.484

    1.484

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

  • Largest Contentful Paint: 15.8 s

    15.8 s

    Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “INDITEX”.

  • Time to Interactive: 16.1 s

    16.1 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

2 checks passed
  • Real-user INP: 125 ms

    125 ms

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

  • Total Blocking Time: 20 ms

    20 ms

    Scripts block the page for only 20 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.8 MB in 85 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 85 requests on a phone: images 1.1 MB (21), scripts 1.1 MB (29) and fonts 255 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    74 KiB

    1 image is downloaded at several times the size a phone draws it, for example Counter_2K.jpg at 2,562 px wide, shown at 390 px. Resized copies would save about 74 KiB.

  • 2 images in older formats

    2 images (164 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.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8993
  • 35 tap targets too small

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

  • Frames without titles

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

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9273
  • Title is short (14 characters)

    Your title is only 14 characters: “INDITEX | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (167 characters)

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

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.inditex.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at inditex.com/robots.txt, the first file search crawlers ask for.

  • 76 internal links, 4 external

    The homepage links to 76 pages on inditex.com and 4 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

    The canonical URL is https://www.inditex.com/itxcomweb/us/en/home.

AI search readiness

1 to fix81
  • No Organization structured data

    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.

  • No llms.txt

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

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (356 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.inditex.com/itxcomweb/us/en/home and https://www.inditex.com/itxcomweb/us/es/home all use the title “INDITEX | Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.inditex.com/itxcomweb/us/en/sustainability, https://www.inditex.com/itxcomweb/us/en/investors/corporate-governance/shareholder-structure, https://www.inditex.com/itxcomweb/us/en/press/news and https://www.inditex.com/itxcomweb/us/en/info/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.inditex.com/itxcomweb/us/en/talent/life-at-inditex and https://www.inditex.com/itxcomweb/us/en/talent/teams use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://www.inditex.com/itxcomweb/us/en/group/leadership, https://www.inditex.com/itxcomweb/us/en/brands and https://www.inditex.com/itxcomweb/us/en/sustainability took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8185
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

  • No direct contact details

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

  • No form on the homepage

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

  • No risk reducer

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

  • About 286 words of copy

    The homepage carries about 286 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Join Us”, “Contact” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at inditex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

Company

Employees
161,281
Founded
1985
Headquarters
Arteixo

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on inditex.com, including 18 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25