Report Summary

  • 0

    Performance

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

hanes.com

Comfortable Clothing Since 1901 | Hanes

Page Load Speed

2.8 sec in total

First Response

37 ms

Resources Loaded

2.3 sec

Page Rendered

464 ms

hanes.com screenshot

About Website

Visit hanes.com now to see the best up-to-date Hanes content for United States and also check out these interesting facts you probably never knew about hanes.com

Shop America's first name in comfort with clothing for the whole family. Find shirts, underwear, socks and more! Free shipping with online orders over $60.

Visit hanes.com

Key Findings

We analyzed Hanes.com page load time and found that the first response time was 37 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

hanes.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value29.2 s

0/100

10%

TBT (Total Blocking Time)

Value18,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.702

0/100

15%

TTI (Time to Interactive)

Value55.5 s

0/100

10%

Network Requests Diagram

www.hanes.com

37 ms

hanes

157 ms

dojo.js

30 ms

StoreCommonUtilities.js

22 ms

hanes.min.js

80 ms

Our browser made a total of 265 requests to load all elements on the main page. We found that 35% of them (93 requests) were addressed to the original Hanes.com, 14% (36 requests) were made to Curations-imaging.nexus.bazaarvoice.com and 6% (16 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (587 ms) relates to the external source Curations-imaging.nexus.bazaarvoice.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (30%)

Content Size

10.8 MB

After Optimization

7.6 MB

In fact, the total size of Hanes.com main page is 10.8 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. 85% 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 6.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 378.6 kB

  • Original 426.7 kB
  • After minification 277.4 kB
  • After compression 48.1 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 149.3 kB, which is 35% 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 378.6 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 171.3 kB

  • Original 6.9 MB
  • After minification 6.7 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. Hanes images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 2.1 MB

  • Original 2.8 MB
  • After minification 2.5 MB
  • After compression 739.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 2.1 MB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 610.5 kB

  • Original 717.6 kB
  • After minification 660.5 kB
  • After compression 107.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. Hanes.com needs all CSS files to be minified and compressed as it can save up to 610.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 120 (50%)

Requests Now

242

After Optimization

122

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

Accessibility Review

hanes.com accessibility score

82

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

[role]s do not have all required [aria-*] attributes

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.

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

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

hanes.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

hanes.com SEO score

83

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanes.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 Hanes.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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