Tools & Wizards About Us
inditex.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

inditex.com

Home

Page Load Speed

877 ms in total

First Response

16 ms

Resources Loaded

810 ms

Page Rendered

51 ms

inditex.com screenshot

About Website

Visit inditex.com now to see the best up-to-date Inditex content for Spain and also check out these interesting facts you probably never knew about inditex.com

Inditex is committed to empower every individual to express their own identity with the purpose of leveraging the power of fashion to make positive change in the world

Visit inditex.com

Key Findings

We analyzed Inditex.com page load time and found that the first response time was 16 ms and then it took 861 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

inditex.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.463

19/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

home

16 ms

fe2690d3045881b2.css

19 ms

661843e7f6ee8de3.css

16 ms

polyfills-5cd94c89d3acac5f.js

473 ms

webpack-5984ff2f1a6c8992.js

54 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Inditex.com and no external sources were called. The less responsive or slowest element that took the longest time to load (473 ms) belongs to the original domain Inditex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (61%)

Content Size

1.7 MB

After Optimization

670.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inditex.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 808.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 103.9 kB

  • Original 122.6 kB
  • After minification 122.6 kB
  • After compression 18.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 103.9 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 49.8 kB

  • Original 375.6 kB
  • After minification 325.8 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Inditex needs image optimization as it can save up to 49.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 554.4 kB

  • Original 808.4 kB
  • After minification 808.3 kB
  • After compression 254.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 554.4 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 326.8 kB

  • Original 399.0 kB
  • After minification 398.7 kB
  • After compression 72.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Inditex.com needs all CSS files to be minified and compressed as it can save up to 326.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (77%)

Requests Now

13

After Optimization

3

  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inditex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

home

home

16 ms

fe2690d3045881b2.css

fe2690d3045881b2.css

19 ms

661843e7f6ee8de3.css

661843e7f6ee8de3.css

16 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

473 ms

webpack-5984ff2f1a6c8992.js

webpack-5984ff2f1a6c8992.js

54 ms

framework-4556c45dd113b893.js

framework-4556c45dd113b893.js

51 ms

main-318c77f25481adc1.js

main-318c77f25481adc1.js

53 ms

_app-3ea71af6f91cc730.js

_app-3ea71af6f91cc730.js

65 ms

ee8b1517-a58790cdb5d23e2e.js

ee8b1517-a58790cdb5d23e2e.js

52 ms

513-a266646b375712ff.js

513-a266646b375712ff.js

219 ms

%5B...slug%5D-ed2a953a50013987.js

%5B...slug%5D-ed2a953a50013987.js

54 ms

_buildManifest.js

_buildManifest.js

61 ms

_ssgManifest.js

_ssgManifest.js

75 ms

_middlewareManifest.js

_middlewareManifest.js

65 ms

Accessibility Review

inditex.com accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

inditex.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inditex.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inditex.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Inditex.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

inditex.com

Open Graph description is not detected on the main page of Inditex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: