Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 0

    Best Practices

  • 76

    SEO

    Google-friendlier than
    35% of websites

haggar.com

Haggar Clothing | Men’s Casual Pants & Dress Pants | Haggar

Page Load Speed

2.4 sec in total

First Response

89 ms

Resources Loaded

1.8 sec

Page Rendered

529 ms

About Website

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

Haggar has been crafting comfortable and quality men's clothing since 1926. Shop our selection of men's khakis and casual pants, dress pants, suits, shirts, and big & tall clothing. See the full range...

Visit haggar.com

Key Findings

We analyzed Haggar.com page load time and found that the first response time was 89 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

haggar.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value8,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.883

3/100

15%

TTI (Time to Interactive)

Value27.1 s

0/100

10%

Network Requests Diagram

haggar.com

89 ms

www.haggar.com

123 ms

autopilot_sdk.js

50 ms

upcp-sdk-0.9.2.min.js

47 ms

upcp-sdk-bridge-1.3.4.min.js

48 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 65% of them (64 requests) were addressed to the original Haggar.com, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Analytics.tiktok.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source 8156107.fls.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 268.2 kB (13%)

Content Size

2.1 MB

After Optimization

1.8 MB

In fact, the total size of Haggar.com main page is 2.1 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 112.4 kB

  • Original 138.0 kB
  • After minification 137.8 kB
  • After compression 25.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 112.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.4 MB
  • After minification 1.4 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. Haggar images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 155.7 kB

  • Original 540.5 kB
  • After minification 539.3 kB
  • After compression 384.7 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 155.7 kB or 29% of the original size.

CSS Optimization

-0%

Potential reduce by 93 B

  • Original 39.0 kB
  • After minification 39.0 kB
  • After compression 39.0 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. Haggar.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

88

After Optimization

38

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

Accessibility Review

haggar.com accessibility score

65

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

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

[aria-*] attributes are not valid or misspelled

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

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

SEO Factors

haggar.com SEO score

76

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

High

robots.txt is not valid

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

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