Tools & Wizards About Us
hatley.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

hatley.com

Hatley Canada

Page Load Speed

1.7 sec in total

First Response

352 ms

Resources Loaded

1.1 sec

Page Rendered

252 ms

hatley.com screenshot

About Website

Welcome to hatley.com homepage info - get ready to check Hatley best content for Canada right away, or after learning these important things about hatley.com

Premium-quality apparel for women and kids that is crafted to be loved, outgrown and handed down.

Visit hatley.com

Key Findings

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

Performance Metrics

hatley.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value4,150 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.446

20/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

www.hatley.com

352 ms

css

29 ms

css

48 ms

styles.css

18 ms

widgets.css

34 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 79% of them (97 requests) were addressed to the original Hatley.com, 5% (6 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (352 ms) belongs to the original domain Hatley.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (41%)

Content Size

3.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hatley.com main page is 3.3 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. 75% 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 121.3 kB

  • Original 141.6 kB
  • After minification 134.3 kB
  • After compression 20.3 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 121.3 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 34.2 kB

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

JavaScript Optimization

-74%

Potential reduce by 791.6 kB

  • Original 1.1 MB
  • After minification 901.4 kB
  • After compression 272.4 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 791.6 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 398.9 kB

  • Original 468.3 kB
  • After minification 378.7 kB
  • After compression 69.4 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. Hatley.com needs all CSS files to be minified and compressed as it can save up to 398.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (65%)

Requests Now

108

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hatley.com

www.hatley.com

352 ms

css

css

29 ms

css

css

48 ms

styles.css

styles.css

18 ms

widgets.css

widgets.css

34 ms

styles.css

styles.css

43 ms

styles.css

styles.css

38 ms

cloud-zoom.css

cloud-zoom.css

34 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

36 ms

webtexgiftcards.css

webtexgiftcards.css

40 ms

slider.css

slider.css

46 ms

local.css

local.css

64 ms

hatley.css

hatley.css

76 ms

responsive.css

responsive.css

48 ms

mobile.css

mobile.css

51 ms

animation.css

animation.css

46 ms

settings.css

settings.css

60 ms

captions.css

captions.css

80 ms

prototype.js

prototype.js

85 ms

ccard.js

ccard.js

82 ms

validation.js

validation.js

82 ms

builder.js

builder.js

82 ms

effects.js

effects.js

82 ms

dragdrop.js

dragdrop.js

81 ms

controls.js

controls.js

97 ms

slider.js

slider.js

99 ms

js.js

js.js

100 ms

form.js

form.js

101 ms

translate.js

translate.js

101 ms

cookies.js

cookies.js

101 ms

ga.js

ga.js

104 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

121 ms

cloud-zoom.1.0.2.min.js

cloud-zoom.1.0.2.min.js

106 ms

jquery.noconflict.js

jquery.noconflict.js

106 ms

jquery.masonry.min.js

jquery.masonry.min.js

110 ms

jquery.ui.totop.js

jquery.ui.totop.js

112 ms

jquery.anystretch.min.js

jquery.anystretch.min.js

120 ms

css

css

31 ms

bta.js

bta.js

8 ms

options.css.php

options.css.php

140 ms

jquery.mousewheel.js

jquery.mousewheel.js

136 ms

jquery.easing.js

jquery.easing.js

123 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

119 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

119 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

119 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

119 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

117 ms

product.js

product.js

114 ms

scripts.js

scripts.js

110 ms

home.js

home.js

110 ms

slider.js

slider.js

110 ms

jquery.iosslider.js

jquery.iosslider.js

91 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

94 ms

script.js

script.js

87 ms

performance.js

performance.js

120 ms

MasterTMS.min.js

MasterTMS.min.js

111 ms

ga.js

ga.js

109 ms

gtm.js

gtm.js

111 ms

w.js

w.js

110 ms

flag_us.png

flag_us.png

156 ms

arrow_switch.png

arrow_switch.png

156 ms

promo_ribbon.png

promo_ribbon.png

164 ms

logo.png

logo.png

159 ms

icon_cart.png

icon_cart.png

157 ms

icon_fav.png

icon_fav.png

165 ms

icon_search.png

icon_search.png

165 ms

icon_warning.png

icon_warning.png

166 ms

2016.02.11-Hero-Women-english.jpg

2016.02.11-Hero-Women-english.jpg

176 ms

2016.02.18-Hero-Banner-Girls-eng.jpg

2016.02.18-Hero-Banner-Girls-eng.jpg

227 ms

2016.02.11-Hero-Boys-eng.jpg

2016.02.11-Hero-Boys-eng.jpg

171 ms

2016.02.12-Hero-Girl-en.jpg

2016.02.12-Hero-Girl-en.jpg

235 ms

selector_full.png

selector_full.png

166 ms

selector_empty.png

selector_empty.png

167 ms

2016.02-home-cta-women.jpg

2016.02-home-cta-women.jpg

169 ms

2016.02-home-cta-girls.jpg

2016.02-home-cta-girls.jpg

171 ms

2016.02-home-cta-boys.jpg

2016.02-home-cta-boys.jpg

172 ms

2016.02-home-cta-baby.jpg

2016.02-home-cta-baby.jpg

178 ms

footer_bg2.jpg

footer_bg2.jpg

180 ms

newsletter_bg.png

newsletter_bg.png

179 ms

no-pvc.png

no-pvc.png

180 ms

blog.png

blog.png

221 ms

shipping.png

shipping.png

220 ms

footer_bg.jpg

footer_bg.jpg

226 ms

facebook.png

facebook.png

222 ms

twitter.png

twitter.png

227 ms

pinterest.png

pinterest.png

228 ms

gplus.png

gplus.png

228 ms

arrow_totop.png

arrow_totop.png

153 ms

arrow_footer.png

arrow_footer.png

154 ms

country_underlined.png

country_underlined.png

156 ms

flag_us.png

flag_us.png

159 ms

flag_ca.png

flag_ca.png

160 ms

flag_uk.png

flag_uk.png

158 ms

flag_int_white.png

flag_int_white.png

158 ms

fancybox-x.png

fancybox-x.png

158 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

86 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

90 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

91 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

92 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

94 ms

JEgmtEDzc-IH8jBshQXrYA.woff

JEgmtEDzc-IH8jBshQXrYA.woff

95 ms

__utm.gif

__utm.gif

69 ms

tags

tags

88 ms

clickstream.min.js

clickstream.min.js

45 ms

conversion_async.js

conversion_async.js

77 ms

fbds.js

fbds.js

115 ms

populaire-webfont.woff

populaire-webfont.woff

97 ms

populaire-webfont.ttf

populaire-webfont.ttf

97 ms

ywft-hannah-narrow-webfont.woff

ywft-hannah-narrow-webfont.woff

109 ms

ywft-hannah-regular-webfont.woff

ywft-hannah-regular-webfont.woff

105 ms

fancybox.png

fancybox.png

91 ms

fancybox-y.png

fancybox-y.png

89 ms

fancy_close.png

fancy_close.png

102 ms

blank.gif

blank.gif

100 ms

collect

collect

103 ms

storage.luckyorange.net

storage.luckyorange.net

71 ms

63 ms

populaire-webfont.svg

populaire-webfont.svg

23 ms

41 ms

ga-audiences

ga-audiences

44 ms

print.css

print.css

18 ms

21 ms

settings.luckyorange.net

settings.luckyorange.net

20 ms

Accessibility Review

hatley.com accessibility score

88

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

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

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

High

Links do not have a discernible name

Best Practices

hatley.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hatley.com SEO score

77

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

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

High

Document doesn't have a valid hreflang

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

hatley.com

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