Tools & Wizards About Us
hazeltwenty.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

hazeltwenty.com

Hazel Twenty/Lex Twenty Menswear

Page Load Speed

5.4 sec in total

First Response

120 ms

Resources Loaded

1.7 sec

Page Rendered

3.6 sec

hazeltwenty.com screenshot

About Website

Click here to check amazing Hazel Twenty content. Otherwise, check out these important facts you probably never knew about hazeltwenty.com

Visit hazeltwenty.com

Key Findings

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

Performance Metrics

hazeltwenty.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value127.3 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value30,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.229

54/100

15%

TTI (Time to Interactive)

Value86.5 s

0/100

10%

Network Requests Diagram

hazeltwenty.com

120 ms

hazeltwenty.com

555 ms

theme-bundle.polyfills.js

50 ms

theme-bundle.head_async.js

50 ms

css

44 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 10% of them (3 requests) were addressed to the original Hazeltwenty.com, 70% (21 requests) were made to Cdn11.bigcommerce.com and 7% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Hazeltwenty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (7%)

Content Size

25.3 MB

After Optimization

23.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hazeltwenty.com main page is 25.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. Only a small number of websites need less resources to load. Images take 25.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 213.0 kB

  • Original 248.4 kB
  • After minification 218.0 kB
  • After compression 35.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. This page needs HTML code to be minified as it can gain 30.5 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 213.0 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 1.5 MB

  • Original 25.0 MB
  • After minification 23.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. Hazel Twenty images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 258 B

  • Original 2.1 kB
  • After minification 2.1 kB
  • After compression 1.9 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 258 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (22%)

Requests Now

27

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hazeltwenty.com

hazeltwenty.com

120 ms

hazeltwenty.com

hazeltwenty.com

555 ms

theme-bundle.polyfills.js

theme-bundle.polyfills.js

50 ms

theme-bundle.head_async.js

theme-bundle.head_async.js

50 ms

css

css

44 ms

theme-384a5be0-1652-013d-f00a-2a329cc86482.css

theme-384a5be0-1652-013d-f00a-2a329cc86482.css

59 ms

theme-bundle.main.js

theme-bundle.main.js

334 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

19 ms

visitor_stencil.js

visitor_stencil.js

330 ms

d8568d29e4eb590456f3576d0.js

d8568d29e4eb590456f3576d0.js

542 ms

fbevents.js

fbevents.js

472 ms

welcome-2_1719432709__88211.original.png

welcome-2_1719432709__88211.original.png

282 ms

welcome.png

welcome.png

517 ms

55b164b881F6B140-F5A0-48AC-A1D3-2DF1C9FAE25E__75798.1724500908.jpg

55b164b881F6B140-F5A0-48AC-A1D3-2DF1C9FAE25E__75798.1724500908.jpg

274 ms

ab83d9e6377B4E7C-B978-4B5F-B89F-86D8C9B357EB__97407.1724500897.jpg

ab83d9e6377B4E7C-B978-4B5F-B89F-86D8C9B357EB__97407.1724500897.jpg

274 ms

4590592e1113101E-ED0B-45AD-923D-593A25DE420B__70979.1724500887.jpg

4590592e1113101E-ED0B-45AD-923D-593A25DE420B__70979.1724500887.jpg

273 ms

59aada0b8757342B-FF8F-4D69-8D15-EEB5B582E2AF__37905.1724500877.jpg

59aada0b8757342B-FF8F-4D69-8D15-EEB5B582E2AF__37905.1724500877.jpg

275 ms

d8eadeb87B693032-2A26-4E19-849C-514960E3B9EC__01835.1724178311.jpg

d8eadeb87B693032-2A26-4E19-849C-514960E3B9EC__01835.1724178311.jpg

277 ms

6ff8482fFBA6DAD7-5A9D-44B7-8428-0C98F1BA0D7B__16789.1724178297.jpg

6ff8482fFBA6DAD7-5A9D-44B7-8428-0C98F1BA0D7B__16789.1724178297.jpg

277 ms

62ea3e79C4C31D26-EB5E-4CEE-BC7B-6C5954D18606__99975.1724178238.jpg

62ea3e79C4C31D26-EB5E-4CEE-BC7B-6C5954D18606__99975.1724178238.jpg

278 ms

9501c63655952AEC-AEBF-4435-8425-F3E99BB26EEE__00084.1724178226.jpg

9501c63655952AEC-AEBF-4435-8425-F3E99BB26EEE__00084.1724178226.jpg

277 ms

bb80ec36BDF15F5F-1825-40C4-8782-030817F40EDC__12943.1724178211.jpg

bb80ec36BDF15F5F-1825-40C4-8782-030817F40EDC__12943.1724178211.jpg

283 ms

0586bcb448F1651E-2BAF-44F3-B649-052EB08A473C__89952.1724178198.jpg

0586bcb448F1651E-2BAF-44F3-B649-052EB08A473C__89952.1724178198.jpg

283 ms

copy-of-hazeltwenty-ashevillev7-asseenins.jpg

copy-of-hazeltwenty-ashevillev7-asseenins.jpg

284 ms

img-9555.jpg

img-9555.jpg

285 ms

new-location-1-.png

new-location-1-.png

285 ms

font

font

210 ms

font

font

226 ms

nobot

nobot

152 ms

index.php

index.php

120 ms

Accessibility Review

hazeltwenty.com accessibility score

97

Accessibility Issues

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

Best Practices

hazeltwenty.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hazeltwenty.com SEO score

84

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

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

hazeltwenty.com

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