Tools & Wizards About Us
cache.net-a-porter.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

cache.net-a-porter.com

NET-A-PORTER | Luxury Fashion, Beauty & Lifestyle for Women

Page Load Speed

13.4 sec in total

First Response

1.1 sec

Resources Loaded

9.7 sec

Page Rendered

2.6 sec

cache.net-a-porter.com screenshot

About Website

Click here to check amazing Cache NET A PORTER content for Japan. Otherwise, check out these important facts you probably never knew about cache.net-a-porter.com

Incredible fashion for incredible women. Shop our edit of women's fashion, beauty and lifestyle from over 800 of the world's top brands at NET-A-PORTER.

Visit cache.net-a-porter.com

Key Findings

We analyzed Cache.net-a-porter.com page load time and found that the first response time was 1.1 sec and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

cache.net-a-porter.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value12,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value40.3 s

0/100

10%

Network Requests Diagram

1080 ms

nap-sifu-01353d6a.css

66 ms

345ea68c511096fed569d5ea9b5f4896f2d72a3d52657

328 ms

nap-sifu-en-27b2acb9.js

704 ms

nap_home.js

304 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cache.net-a-porter.com, 5% (3 requests) were made to Connect.facebook.net and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Net-a-porter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 879.3 kB (68%)

Content Size

1.3 MB

After Optimization

404.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cache.net-a-porter.com main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 953.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 834.4 kB

  • Original 953.8 kB
  • After minification 952.6 kB
  • After compression 119.3 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 834.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 163.4 kB
  • After minification 163.4 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. Cache NET A PORTER images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 44.6 kB

  • Original 165.6 kB
  • After minification 165.5 kB
  • After compression 121.0 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 44.6 kB or 27% of the original size.

CSS Optimization

-19%

Potential reduce by 242 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.1 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. Cache.net-a-porter.com needs all CSS files to be minified and compressed as it can save up to 242 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (61%)

Requests Now

46

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1080 ms

nap-sifu-01353d6a.css

nap-sifu-01353d6a.css

66 ms

345ea68c511096fed569d5ea9b5f4896f2d72a3d52657

345ea68c511096fed569d5ea9b5f4896f2d72a3d52657

328 ms

nap-sifu-en-27b2acb9.js

nap-sifu-en-27b2acb9.js

704 ms

nap_home.js

nap_home.js

304 ms

106c18bb

106c18bb

62 ms

styles.e1d82849.chunk.css

styles.e1d82849.chunk.css

61 ms

raygun.min.js

raygun.min.js

654 ms

gtm.js

gtm.js

1026 ms

R4ER9-P3HDX-YEVEY-55HHF-MEUYZ

R4ER9-P3HDX-YEVEY-55HHF-MEUYZ

1635 ms

w800_q80.jpg

w800_q80.jpg

415 ms

w800_q80.jpg

w800_q80.jpg

415 ms

w800_q80.jpg

w800_q80.jpg

782 ms

w800_q80.jpg

w800_q80.jpg

783 ms

w0.png

w0.png

782 ms

w0.svg

w0.svg

780 ms

w0.png

w0.png

1102 ms

w0.png

w0.png

1075 ms

polyfills-b7550c429e2fc829f6c9.js

polyfills-b7550c429e2fc829f6c9.js

1031 ms

webpack-deeeca48fd6e88836e20.js

webpack-deeeca48fd6e88836e20.js

1031 ms

commons.22b59dcc74c8b98177c7.js

commons.22b59dcc74c8b98177c7.js

1009 ms

main-d424e8e2a95c23552611.js

main-d424e8e2a95c23552611.js

1004 ms

_app-abfeb05529683e16cd19.js

_app-abfeb05529683e16cd19.js

1349 ms

framework.b8f3eb8bcaae4060f23f.js

framework.b8f3eb8bcaae4060f23f.js

1347 ms

ee1a1c0b4955f7c92da6c0dbade9023bd2e9621e.3a69215f6048893c6d8d.js

ee1a1c0b4955f7c92da6c0dbade9023bd2e9621e.3a69215f6048893c6d8d.js

1424 ms

304976e94ca847f3bb0a250946435ccce194ad29.ced07edaabeb306fe88a.js

304976e94ca847f3bb0a250946435ccce194ad29.ced07edaabeb306fe88a.js

1348 ms

e06c18c421964aaca7ce23f1aca39c425f31a9a0.0abe02a964c9fa07cc2a.js

e06c18c421964aaca7ce23f1aca39c425f31a9a0.0abe02a964c9fa07cc2a.js

1348 ms

styles.c056747f73d48367ab74.js

styles.c056747f73d48367ab74.js

1307 ms

NAPHomepage-42602094efba13e3c74b.js

NAPHomepage-42602094efba13e3c74b.js

1422 ms

_buildManifest.js

_buildManifest.js

1422 ms

_ssgManifest.js

_ssgManifest.js

1441 ms

wpIndex_min.js

wpIndex_min.js

1019 ms

lZwwYdEE

lZwwYdEE

1083 ms

sec-3-8.css

sec-3-8.css

1019 ms

sec-cpt-3-8.js

sec-cpt-3-8.js

1082 ms

akkuratproregular-0f24c307.woff

akkuratproregular-0f24c307.woff

1079 ms

akkuratprobold-ebe74ab2.woff

akkuratprobold-ebe74ab2.woff

1074 ms

SackersGothicStd-Heavy-74b7643d.woff

SackersGothicStd-Heavy-74b7643d.woff

677 ms

chronicledisplay-2ce9327c.woff

chronicledisplay-2ce9327c.woff

693 ms

chronicledisplaylight-55c81ded.woff

chronicledisplaylight-55c81ded.woff

691 ms

instagram-44c80a3b.svg

instagram-44c80a3b.svg

331 ms

logo-jcb-03bd433f.svg

logo-jcb-03bd433f.svg

309 ms

logo-applepay-17b063c5.svg

logo-applepay-17b063c5.svg

418 ms

logo-klarna-b0ce03f5.svg

logo-klarna-b0ce03f5.svg

300 ms

logo-unionpay-ea3ed1e2.svg

logo-unionpay-ea3ed1e2.svg

355 ms

gtm.js

gtm.js

355 ms

lZwwYdEE

lZwwYdEE

875 ms

tag.js

tag.js

899 ms

config.json

config.json

933 ms

lZwwYdEE

lZwwYdEE

2532 ms

fbevents.js

fbevents.js

488 ms

yorb.min.js

yorb.min.js

2357 ms

https:/

https:/

15 ms

lZwwYdEE

lZwwYdEE

2103 ms

watch.js

watch.js

45 ms

identity.js

identity.js

216 ms

1727590610797308

1727590610797308

204 ms

Accessibility Review

cache.net-a-porter.com accessibility score

68

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cache.net-a-porter.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

cache.net-a-porter.com SEO score

84

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cache.net-a-porter.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cache.net-a-porter.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

cache.net-a-porter.com

Open Graph description is not detected on the main page of Cache NET A PORTER. 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: