Tools & Wizards About Us
tommy.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tommy.com

Tommy Hilfiger USA

Page Load Speed

35.2 sec in total

First Response

285 ms

Resources Loaded

27.8 sec

Page Rendered

7 sec

tommy.com screenshot

About Website

Click here to check amazing Tommy content for United States. Otherwise, check out these important facts you probably never knew about tommy.com

Welcome to Tommy Hilfiger. Classic, American cool style since 1985—delivering a modern twist on tradition, reinventing the fashion icons of prep, nautical, sport and rock-n-roll for today.

Visit tommy.com

Key Findings

We analyzed Tommy.com page load time and found that the first response time was 285 ms and then it took 34.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

tommy.com performance score

0

Network Requests Diagram

tommy.com

285 ms

geo.tommy.com

191 ms

www

82 ms

thb2cus

47 ms

en

765 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tommy.com, 66% (59 requests) were made to Usa.tommy.com and 26% (23 requests) were made to Media.tommy.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Media.tommy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.3 MB (47%)

Content Size

9.2 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tommy.com main page is 9.2 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. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 126.5 kB

  • Original 150.1 kB
  • After minification 131.9 kB
  • After compression 23.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. This page needs HTML code to be minified as it can gain 18.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 126.5 kB or 84% of the original size.

Image Optimization

-11%

Potential reduce by 455.8 kB

  • Original 4.3 MB
  • After minification 3.8 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. Obviously, Tommy needs image optimization as it can save up to 455.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 3.0 MB

  • Original 4.0 MB
  • After minification 3.4 MB
  • After compression 961.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 3.0 MB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 734.3 kB

  • Original 859.4 kB
  • After minification 663.3 kB
  • After compression 125.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. Tommy.com needs all CSS files to be minified and compressed as it can save up to 734.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (81%)

Requests Now

85

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 55 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tommy.com

tommy.com

285 ms

geo.tommy.com

geo.tommy.com

191 ms

www

www

82 ms

thb2cus

thb2cus

47 ms

en

en

765 ms

normalize.css

normalize.css

803 ms

pvh.css

pvh.css

1432 ms

th.css

th.css

804 ms

webfonts.css

webfonts.css

802 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

1559 ms

jquery-ui.min.js

jquery-ui.min.js

1401 ms

jquery.cookie.js

jquery.cookie.js

1401 ms

TweenMax.min.js

TweenMax.min.js

1594 ms

hammer.min.js

hammer.min.js

1593 ms

jquery.hammer-full.min.js

jquery.hammer-full.min.js

1595 ms

dojo.js

dojo.js

1918 ms

dojodesktop-rwd.js

dojodesktop-rwd.js

1944 ms

pvh.global.js

pvh.global.js

1544 ms

th.js

th.js

1545 ms

pvh.util.js

pvh.util.js

1916 ms

th.util.js

th.util.js

1917 ms

MessageHelper.js

MessageHelper.js

1943 ms

StoreCommonUtilities.js

StoreCommonUtilities.js

1944 ms

MiniShopCartDisplay.js

MiniShopCartDisplay.js

2044 ms

CartServicesDeclaration.js

CartServicesDeclaration.js

2045 ms

CatalogEntryRecommendation.js

CatalogEntryRecommendation.js

1960 ms

video.js

video.js

2001 ms

ci.js

ci.js

1890 ms

hiddenespotcontent.css

hiddenespotcontent.css

1988 ms

HP-block-layout.css

HP-block-layout.css

1967 ms

jquery.rwdImageMaps.min.js

jquery.rwdImageMaps.min.js

2259 ms

build.min.js

build.min.js

2225 ms

cloudzoom.js

cloudzoom.js

1872 ms

jquery.productImage.js

jquery.productImage.js

1872 ms

jquery.tabs.js

jquery.tabs.js

1872 ms

pvh.fullscreen.js

pvh.fullscreen.js

1755 ms

pvh.altImages.js

pvh.altImages.js

1756 ms

ShoppingActions.js

ShoppingActions.js

1756 ms

ShoppingActionsServicesDeclaration.js

ShoppingActionsServicesDeclaration.js

1755 ms

jquery.dropkick.js

jquery.dropkick.js

1755 ms

jquery.colorSwatchImage.js

jquery.colorSwatchImage.js

1748 ms

CategoryDisplay.js

CategoryDisplay.js

1864 ms

SwatchDisplay.js

SwatchDisplay.js

1810 ms

VideoViewer.js

VideoViewer.js

2002 ms

pvh.quickView.js

pvh.quickView.js

1861 ms

ProductDisplay.js

ProductDisplay.js

1645 ms

ShoppingList.js

ShoppingList.js

1644 ms

ShoppingListServicesDeclaration.js

ShoppingListServicesDeclaration.js

1054 ms

jquery.gsap.min.js

jquery.gsap.min.js

1016 ms

jquery.overlay.js

jquery.overlay.js

1072 ms

jquery.autoSuggest.js

jquery.autoSuggest.js

915 ms

pvh.overlay.js

pvh.overlay.js

948 ms

th.miniCart.js

th.miniCart.js

890 ms

pvh.miniCart.js

pvh.miniCart.js

891 ms

pvh.tealium.js

pvh.tealium.js

889 ms

pvh.newsletter.js

pvh.newsletter.js

2191 ms

Affiliate.js

Affiliate.js

2190 ms

URLPromo.js

URLPromo.js

1820 ms

th.newsletterServicesDeclaration.js

th.newsletterServicesDeclaration.js

1819 ms

th.newsletter.js

th.newsletter.js

1794 ms

th.siteMessageBar.js

th.siteMessageBar.js

1793 ms

th.footer.js

th.footer.js

1792 ms

th.headerNav.js

th.headerNav.js

1792 ms

th.stickyHeader.js

th.stickyHeader.js

1732 ms

cd5a93fc-2bb1-48df-8982-11119cd6e270.woff

cd5a93fc-2bb1-48df-8982-11119cd6e270.woff

313 ms

entry.js

entry.js

78 ms

th.png

th.png

1328 ms

tho.png

tho.png

899 ms

bag.png

bag.png

871 ms

bag.png

bag.png

871 ms

magGlass.png

magGlass.png

871 ms

HOMEPAGE_AUG_Header%204%20slice.jpg

HOMEPAGE_AUG_Header%204%20slice.jpg

1114 ms

Gigi_02.jpg

Gigi_02.jpg

870 ms

HP_AUG_Mens_polos.jpg

HP_AUG_Mens_polos.jpg

1055 ms

HP_AUG_Accessories.jpg

HP_AUG_Accessories.jpg

1043 ms

Desktop_HP_craft.jpg

Desktop_HP_craft.jpg

1103 ms

facebook.png

facebook.png

1041 ms

twitter.png

twitter.png

1041 ms

instagram.png

instagram.png

1041 ms

tumblr.png

tumblr.png

1042 ms

pinterest.png

pinterest.png

1024 ms

youtube.png

youtube.png

1084 ms

th_white.png

th_white.png

1082 ms

backToTop.png

backToTop.png

1066 ms

loading.gif

loading.gif

1066 ms

icon_caption_box.png

icon_caption_box.png

352 ms

4bebed2e8bbbc4fb32294792b5d0403b

4bebed2e8bbbc4fb32294792b5d0403b

487 ms

utag.js

utag.js

2210 ms

blank.gif

blank.gif

1373 ms

Berling-Rmn.woff

Berling-Rmn.woff

66 ms

SEO Factors

tommy.com SEO score

0

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 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 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

tommy.com

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