Tools & Wizards About Us
ee.tommy.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ee.tommy.com

Tommy Hilfiger® EE Official Web Store - Up to 50% Off

Page Load Speed

2.6 sec in total

First Response

363 ms

Resources Loaded

1.9 sec

Page Rendered

428 ms

ee.tommy.com screenshot

About Website

Welcome to ee.tommy.com homepage info - get ready to check EE Tommy best content for United States right away, or after learning these important things about ee.tommy.com

Embrace a sophisticated, sporty style with timeless designer fashion by Tommy Hilfiger. Our heritage, reinvented for today. ✓ 60-day free returns

Visit ee.tommy.com

Key Findings

We analyzed Ee.tommy.com page load time and found that the first response time was 363 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ee.tommy.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value3,770 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

ee.tommy.com

363 ms

ruxitagentjs_ICA27Vdfghjqrux_10249220905100923.js

53 ms

8382950752.js

104 ms

94a609a89cf922df1692d4ab45eda306462d1ae9_CSS.1bcbb990.chunk.css

174 ms

5198568fc3b5fbef63917551e79d0a144269091e_CSS.61d5e13b.chunk.css

170 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 87% of them (47 requests) were addressed to the original Ee.tommy.com, 9% (5 requests) were made to Image-live.prd.b2c-coremedia.eu.pvh.cloud and 4% (2 requests) were made to D1snv67wdds0p2.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ee.tommy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 918.7 kB (39%)

Content Size

2.4 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ee.tommy.com main page is 2.4 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. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 298.1 kB

  • Original 359.7 kB
  • After minification 359.7 kB
  • After compression 61.6 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 298.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.1 MB

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. EE Tommy images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 94.6 kB

  • Original 202.6 kB
  • After minification 202.6 kB
  • After compression 108.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 94.6 kB or 47% of the original size.

CSS Optimization

-72%

Potential reduce by 526.0 kB

  • Original 732.7 kB
  • After minification 727.9 kB
  • After compression 206.7 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. Ee.tommy.com needs all CSS files to be minified and compressed as it can save up to 526.0 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (80%)

Requests Now

51

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ee.tommy.com

ee.tommy.com

363 ms

ruxitagentjs_ICA27Vdfghjqrux_10249220905100923.js

ruxitagentjs_ICA27Vdfghjqrux_10249220905100923.js

53 ms

8382950752.js

8382950752.js

104 ms

94a609a89cf922df1692d4ab45eda306462d1ae9_CSS.1bcbb990.chunk.css

94a609a89cf922df1692d4ab45eda306462d1ae9_CSS.1bcbb990.chunk.css

174 ms

5198568fc3b5fbef63917551e79d0a144269091e_CSS.61d5e13b.chunk.css

5198568fc3b5fbef63917551e79d0a144269091e_CSS.61d5e13b.chunk.css

170 ms

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34_CSS.09064556.chunk.css

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34_CSS.09064556.chunk.css

105 ms

styles.20c6fc4a.chunk.css

styles.20c6fc4a.chunk.css

124 ms

_app.b08f0193.chunk.css

_app.b08f0193.chunk.css

145 ms

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae_CSS.d5619df4.chunk.css

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae_CSS.d5619df4.chunk.css

175 ms

polyfills-d3ebdc28fc91e3276f2d.js

polyfills-d3ebdc28fc91e3276f2d.js

243 ms

main-8c45ed7b59da4b6bf985.js

main-8c45ed7b59da4b6bf985.js

223 ms

webpack-407f8842e3df63d034f0.js

webpack-407f8842e3df63d034f0.js

223 ms

framework.278e1f8c0b847b785021.js

framework.278e1f8c0b847b785021.js

223 ms

commons.8b04d1140193db32db56.js

commons.8b04d1140193db32db56.js

225 ms

94a609a89cf922df1692d4ab45eda306462d1ae9_CSS.b63f308e3379c9a1c013.js

94a609a89cf922df1692d4ab45eda306462d1ae9_CSS.b63f308e3379c9a1c013.js

120 ms

07bf4b35ca33ce90d4ac09e02c4f869ea99a204f.a08ecf609b72541a7066.js

07bf4b35ca33ce90d4ac09e02c4f869ea99a204f.a08ecf609b72541a7066.js

226 ms

5198568fc3b5fbef63917551e79d0a144269091e_CSS.81cc49b066322e96c343.js

5198568fc3b5fbef63917551e79d0a144269091e_CSS.81cc49b066322e96c343.js

224 ms

6c4bd9c08c5d53ad3e398c9daacae48c28442439.2bd7a24b10afd3a3daa6.js

6c4bd9c08c5d53ad3e398c9daacae48c28442439.2bd7a24b10afd3a3daa6.js

223 ms

d569f79b7ae3bc2715f52906701e0b8157be2d4d.7c76a193f4f3bd1c47b4.js

d569f79b7ae3bc2715f52906701e0b8157be2d4d.7c76a193f4f3bd1c47b4.js

227 ms

89bf8634f27db09931503939ecae42a3f9670925.05e4e87df0b990b13320.js

89bf8634f27db09931503939ecae42a3f9670925.05e4e87df0b990b13320.js

230 ms

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34.438f4aaaad6ecdeb9e31.js

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34.438f4aaaad6ecdeb9e31.js

228 ms

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34_CSS.62d53d8224515f39f6c9.js

17f83eadbc67e3f08d2fc12cc31cd3a0bf762f34_CSS.62d53d8224515f39f6c9.js

224 ms

22b2d263486d261ee398b179e6e83a86e4a7ff4f.4df47f39710415122369.js

22b2d263486d261ee398b179e6e83a86e4a7ff4f.4df47f39710415122369.js

228 ms

77ffa9354d3d717820c3ec4691262680df6f6b79.3391bfe0a366b01d8905.js

77ffa9354d3d717820c3ec4691262680df6f6b79.3391bfe0a366b01d8905.js

240 ms

8b184793c78cdc34f7d5d0850d1230f7c9552377.5dc8bab6fedefd6a59bf.js

8b184793c78cdc34f7d5d0850d1230f7c9552377.5dc8bab6fedefd6a59bf.js

240 ms

71893487ec563795f9a0a84bc27773decf0af4b8.3ed093c0222714aba9d4.js

71893487ec563795f9a0a84bc27773decf0af4b8.3ed093c0222714aba9d4.js

239 ms

2ebfc6370fa90ff85b33065de43eff4b666a0aea.09a5c550d2f7748638b7.js

2ebfc6370fa90ff85b33065de43eff4b666a0aea.09a5c550d2f7748638b7.js

239 ms

09fa46353be2cf23ccbff7aeb3fabac2afd67e5a.c59819aedd5a21f971ea.js

09fa46353be2cf23ccbff7aeb3fabac2afd67e5a.c59819aedd5a21f971ea.js

238 ms

b1542cc239bf56c8a14913c0a930efe682b5cf86.cb05013ef4e914e24500.js

b1542cc239bf56c8a14913c0a930efe682b5cf86.cb05013ef4e914e24500.js

276 ms

styles.265812a21aeba506a736.js

styles.265812a21aeba506a736.js

280 ms

_app-f4a7e173e319e644dfce.js

_app-f4a7e173e319e644dfce.js

279 ms

fb60d8f2eec5a6936796962d57ca6d15c11ba4a8.5fdaa1ae210ff5db70c1.js

fb60d8f2eec5a6936796962d57ca6d15c11ba4a8.5fdaa1ae210ff5db70c1.js

279 ms

1c0be7bc6196155f68a7f48409b139501d2766ac.f3b9adfdcc18a48f90f1.js

1c0be7bc6196155f68a7f48409b139501d2766ac.f3b9adfdcc18a48f90f1.js

279 ms

de07dc4994eefc7742d27e179943c8d502a36f17.3de9d507b5f135e9a105.js

de07dc4994eefc7742d27e179943c8d502a36f17.3de9d507b5f135e9a105.js

623 ms

a6ba61cd897df714775aa7e7b8c4d4b39ce38c9d.9f3b7ea12fccd00def66.js

a6ba61cd897df714775aa7e7b8c4d4b39ce38c9d.9f3b7ea12fccd00def66.js

620 ms

44ab735cae071d2bb9ec54c4ae9a316f9687c839.c7bdc5b3d5afec9709b8.js

44ab735cae071d2bb9ec54c4ae9a316f9687c839.c7bdc5b3d5afec9709b8.js

621 ms

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae.68d50d2a56ca38b8bd11.js

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae.68d50d2a56ca38b8bd11.js

626 ms

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae_CSS.558307338ad429cff0a7.js

3c00f800eca6d7bdbb0c7894bb5e2f45038f0aae_CSS.558307338ad429cff0a7.js

619 ms

ca42b1a7a6aefc7c711c4edcdeb5682dc9d2c550.dfa7574c7145235eff55.js

ca42b1a7a6aefc7c711c4edcdeb5682dc9d2c550.dfa7574c7145235eff55.js

625 ms

index-6131f444c1e1a6ccd07d.js

index-6131f444c1e1a6ccd07d.js

622 ms

_buildManifest.js

_buildManifest.js

623 ms

_ssgManifest.js

_ssgManifest.js

613 ms

NnRR43TCIB

NnRR43TCIB

608 ms

fh.js

fh.js

182 ms

ead3b3b1762c425558b60f127c30a9ff

ead3b3b1762c425558b60f127c30a9ff

207 ms

module-1-70-2732x1050px-desktop-1-.jpg

module-1-70-2732x1050px-desktop-1-.jpg

504 ms

splash-904x1416px-desktop-02.jpg

splash-904x1416px-desktop-02.jpg

501 ms

splash-904x1416px-desktop-01.jpg

splash-904x1416px-desktop-01.jpg

180 ms

splash-904x1416px-desktop-03.jpg

splash-904x1416px-desktop-03.jpg

505 ms

heart.svg

heart.svg

709 ms

basket.svg

basket.svg

706 ms

futurastd-book.woff

futurastd-book.woff

1165 ms

fh.html

fh.html

40 ms

NnRR43TCIB

NnRR43TCIB

207 ms

Accessibility Review

ee.tommy.com accessibility score

74

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 input fields do not have accessible names

High

ARIA IDs are not unique

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

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

ee.tommy.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ee.tommy.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ee.tommy.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 Ee.tommy.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

ee.tommy.com

Open Graph data is detected on the main page of EE Tommy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: