2.4 sec in total
89 ms
1.8 sec
529 ms
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.comWe 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.
haggar.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value7.8 s
3/100
25%
Value12.1 s
4/100
10%
Value8,110 ms
0/100
30%
Value0.883
3/100
15%
Value27.1 s
0/100
10%
89 ms
123 ms
50 ms
47 ms
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 size can be reduced by 268.2 kB (13%)
2.1 MB
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.
Potential reduce by 112.4 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.
Potential reduce by 0 B
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.
Potential reduce by 155.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.
Potential reduce by 93 B
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.
Number of requests can be reduced by 50 (57%)
88
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.
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
modernizr.js
19 ms
typography.css
25 ms
style.css
42 ms
style-defer.css
43 ms
homepage.css
37 ms
bv.js
35 ms
jquery-2.1.1.min.js
100 ms
jquery-ui.min.js
35 ms
svg4everybody.js
36 ms
slick.js
92 ms
jquery.validate.min.js
91 ms
jquery.stickr.min.js
90 ms
jquery.zoom.min.js
93 ms
pinch-zoom.umd.min.js
92 ms
osano.js
436 ms
common.js
101 ms
app.js
99 ms
storefront.page.js
99 ms
livechat-config.js
99 ms
livechat-config-hggr.js
98 ms
livechat.min.js
118 ms
scripts
514 ms
dwanalytics-22.2.js
118 ms
dwac-21.7.js
116 ms
gretel.min.js
38 ms
applepay.js
114 ms
01632674772
61 ms
gtm.js
99 ms
site.min.js
85 ms
4233792702.js
32 ms
Images-Show
65 ms
Nav%20Drop%20Down%20235x260-PANTS.jpg
35 ms
HoverNav_235x260.jpg
47 ms
1600592_Category_Navigation_Dropdown_Image_Tops.jpg
49 ms
Accessories_hover_1.png
51 ms
Nav%20Drop%20Down%20235x260-CLEAR.jpg
51 ms
0512-0518_1440x204.jpg
52 ms
Homepage_Hero_SummerStylesHaveArrived_Desktop.jpg
70 ms
Homepage_Text_Gearupfornewseason.jpg
104 ms
HJ80324_404.jpg
102 ms
HJ80324_404_01.jpg
70 ms
HJ80333_603.jpg
103 ms
HJ80333_603_01.jpg
106 ms
HJ80339_436.jpg
104 ms
HJ80339_436_01.jpg
105 ms
HJ80321_027.jpg
104 ms
HJ80321_027_01.jpg
106 ms
HZ70235_044.jpg
105 ms
HZ70235_044_01.jpg
107 ms
HZ70232_460.jpg
163 ms
HZ70232_460_01.jpg
107 ms
Gotham-Book.ttf
159 ms
Gotham-Medium.ttf
159 ms
Gotham-Light.ttf
159 ms
Gotham-XLight.ttf
159 ms
Gotham-Thin.ttf
159 ms
Gotham-Bold.ttf
154 ms
Gotham-Ultra.ttf
153 ms
Gotham-Black.ttf
155 ms
HD70068_400.jpg
154 ms
HD70068_400_01.jpg
154 ms
down-arrow-thicker.svg
155 ms
Homepage_Hero_CoolRightPerformancFelx_Desktop.jpg
139 ms
Homepage_Expresion_Coolright_Desktop.jpg
140 ms
Chat-Pop-Up-H-Crown-NoBackground.png
139 ms
js
77 ms
fbevents.js
207 ms
destination
170 ms
hotjar-616403.js
284 ms
ld.js
241 ms
bat.js
278 ms
utm_cookie.490dccee6d690a78b3dc382ef669b37c.js
287 ms
aZA2gq.js
641 ms
events.js
507 ms
451 ms
fnuGRRLJiZoSLg.js
506 ms
jquery-ui.min.css
141 ms
activityi;src=8156107;type=ret01;cat=land01;ord=2785302015953;npa=0;auiddc=433102313.1715660774;pscdl=noapi;frm=0;gtm=45fe45d0z876482404za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.haggar.com%2F
742 ms
livechat.min.css
257 ms
syncframe
377 ms
rdf.min.js
384 ms
spx
648 ms
modules.1a30a0a67c3c23c13060.js
646 ms
deployment.js
587 ms
cs.js
592 ms
Images-Show
188 ms
ajax-loader.gif
191 ms
pebble
480 ms
sync
532 ms
lightbox_inline.js
716 ms
main.MTExZjAwMWE5MA.js
370 ms
src=8156107;type=ret01;cat=land01;ord=2785302015953;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe45d0z876482404za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.haggar.com%2F
81 ms
s.htm
8 ms
__Analytics-Start
23 ms
haggar.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
[aria-*] attributes are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
haggar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
haggar.com
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: