Tools & Wizards About Us
woolrich.eu screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

woolrich.eu

Fall/Winter Collection: Urban Looks and Outdoors | Woolrich US

Page Load Speed

7.7 sec in total

First Response

1.1 sec

Resources Loaded

4.8 sec

Page Rendered

1.8 sec

woolrich.eu screenshot

About Website

Welcome to woolrich.eu homepage info - get ready to check Woolrich best content for Germany right away, or after learning these important things about woolrich.eu

Discover the Fall/Winter Collection: urban outerwear and apparel for the city and the outdoors.

Visit woolrich.eu

Key Findings

We analyzed Woolrich.eu page load time and found that the first response time was 1.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

woolrich.eu performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value2,710 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

woolrich.eu

1051 ms

1088 ms

app.js

28 ms

embeds-min.js

72 ms

assets.css

47 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Woolrich.eu, 21% (13 requests) were made to Woolrich.com and 6% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Woolrich.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 312.1 kB (48%)

Content Size

655.3 kB

After Optimization

343.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Woolrich.eu main page is 655.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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 299.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 268.6 kB

  • Original 299.3 kB
  • After minification 291.0 kB
  • After compression 30.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 268.6 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 3.0 kB

  • Original 78.2 kB
  • After minification 75.2 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. Woolrich images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 40.5 kB

  • Original 198.0 kB
  • After minification 197.9 kB
  • After compression 157.5 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 40.5 kB or 20% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 79.8 kB
  • After minification 79.8 kB
  • After compression 79.8 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. Woolrich.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (79%)

Requests Now

56

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

woolrich.eu

woolrich.eu

1051 ms

1088 ms

app.js

app.js

28 ms

embeds-min.js

embeds-min.js

72 ms

assets.css

assets.css

47 ms

otSDKStub.js

otSDKStub.js

37 ms

lib.js

lib.js

31 ms

ltkJS.js

ltkJS.js

42 ms

ltkClickTracking.js

ltkClickTracking.js

34 ms

ltkActivityTracking.js

ltkActivityTracking.js

419 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

42 ms

dwac-21.7.js

dwac-21.7.js

33 ms

gretel.min.js

gretel.min.js

25 ms

506333be-b10f-4d36-91a9-3447674bb26f.json

506333be-b10f-4d36-91a9-3447674bb26f.json

287 ms

gtm.js

gtm.js

339 ms

est1830.png

est1830.png

181 ms

est1830-white.png

est1830-white.png

203 ms

notify.svg

notify.svg

204 ms

check.svg

check.svg

178 ms

otBannerSdk.js

otBannerSdk.js

24 ms

Project-Icons.woff

Project-Icons.woff

648 ms

script.js

script.js

419 ms

optimize.js

optimize.js

577 ms

webloader.min.js

webloader.min.js

679 ms

fbevents.js

fbevents.js

678 ms

analytics.js

analytics.js

673 ms

conversion_async.js

conversion_async.js

671 ms

bat.js

bat.js

627 ms

core.js

core.js

644 ms

events.js

events.js

774 ms

teads-fellow.js

teads-fellow.js

572 ms

zcpt.js

zcpt.js

613 ms

ld.js

ld.js

607 ms

122922.ct.js

122922.ct.js

781 ms

site.min.js

site.min.js

767 ms

nyekZy8xxq8B8cJMdm4a.js

nyekZy8xxq8B8cJMdm4a.js

785 ms

js

js

289 ms

activityi;src=11157661;type=invmedia;cat=pixel0;ord=7215720983478;gtm=2wg9q0;auiddc=1199025200.1664444000;u1=gtm.js;u10=-;u11=-;u12=-;u13=-;u14=-;u15=-;u16=-;u17=-;u18=-;u19=-;u2=(not%20set);u20=-;u21=-;u3=(not%20set);u4=(not%20set);u5=home;u6=us;u7=en;u8=no-logged;u9=-;~oref=https%3A%2F%2Fwww.woolrich.com%2Fus%2Fen%2F

activityi;src=11157661;type=invmedia;cat=pixel0;ord=7215720983478;gtm=2wg9q0;auiddc=1199025200.1664444000;u1=gtm.js;u10=-;u11=-;u12=-;u13=-;u14=-;u15=-;u16=-;u17=-;u18=-;u19=-;u2=(not%20set);u20=-;u21=-;u3=(not%20set);u4=(not%20set);u5=home;u6=us;u7=en;u8=no-logged;u9=-;~oref=https%3A%2F%2Fwww.woolrich.com%2Fus%2Fen%2F

486 ms

4035404.js

4035404.js

174 ms

235628753608250

235628753608250

130 ms

collect

collect

399 ms

collect

collect

391 ms

main.8f82d377.js

main.8f82d377.js

62 ms

42 ms

354 ms

401 ms

collect

collect

330 ms

syncframe

syncframe

363 ms

4035404

4035404

396 ms

122 ms

collect

collect

117 ms

collect

collect

162 ms

157 ms

115 ms

src=11157661;type=invmedia;cat=pixel0;ord=7215720983478;gtm=2wg9q0;auiddc=1199025200.1664444000;u1=gtm.js;u10=-;u11=-;u12=-;u13=-;u14=-;u15=-;u16=-;u17=-;u18=-;u19=-;u2=(not%20set);u20=-;u21=-;u3=(not%20set);u4=(not%20set);u5=home;u6=us;u7=en;u8=no-logged;u9=-;~oref=https%3A%2F%2Fwww.woolrich.com%2Fus%2Fen%2F

src=11157661;type=invmedia;cat=pixel0;ord=7215720983478;gtm=2wg9q0;auiddc=1199025200.1664444000;u1=gtm.js;u10=-;u11=-;u12=-;u13=-;u14=-;u15=-;u16=-;u17=-;u18=-;u19=-;u2=(not%20set);u20=-;u21=-;u3=(not%20set);u4=(not%20set);u5=home;u6=us;u7=en;u8=no-logged;u9=-;~oref=https%3A%2F%2Fwww.woolrich.com%2Fus%2Fen%2F

71 ms

97 ms

ga-audiences

ga-audiences

116 ms

conversion.js

conversion.js

59 ms

ga-audiences

ga-audiences

69 ms

clarity.js

clarity.js

74 ms

21 ms

pebble

pebble

43 ms

Accessibility Review

woolrich.eu accessibility score

94

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-*] attributes do not match their roles

Best Practices

woolrich.eu best practices score

83

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

SEO Factors

woolrich.eu SEO score

98

Search Engine Optimization Advices

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 Woolrich.eu 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 Woolrich.eu 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

woolrich.eu

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