Tools & Wizards About Us
hazelnut.es screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

hazelnut.es

Hazelnut – Zapatos, bolsos, pañuelos, ropa y complementos

Page Load Speed

9 sec in total

First Response

2.5 sec

Resources Loaded

6.3 sec

Page Rendered

173 ms

hazelnut.es screenshot

About Website

Click here to check amazing Hazelnut content. Otherwise, check out these important facts you probably never knew about hazelnut.es

Visit hazelnut.es

Key Findings

We analyzed Hazelnut.es page load time and found that the first response time was 2.5 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hazelnut.es performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value21.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value31.7 s

0/100

25%

SI (Speed Index)

Value26.1 s

0/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

hazelnut.es

2493 ms

style.min.css

626 ms

shortcodes.css

532 ms

default.css

611 ms

style_default.css

514 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 98% of them (115 requests) were addressed to the original Hazelnut.es, 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Hazelnut.es.

Page Optimization Overview & Recommendations

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

Content Size

8.8 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hazelnut.es main page is 8.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. 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 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 186.3 kB

  • Original 218.4 kB
  • After minification 213.2 kB
  • After compression 32.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. 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 186.3 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 236.0 kB

  • Original 4.7 MB
  • After minification 4.5 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. Hazelnut images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 951.6 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 308.8 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 951.6 kB or 75% of the original size.

CSS Optimization

-88%

Potential reduce by 2.3 MB

  • Original 2.6 MB
  • After minification 2.2 MB
  • After compression 305.3 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. Hazelnut.es needs all CSS files to be minified and compressed as it can save up to 2.3 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (73%)

Requests Now

114

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hazelnut.es

hazelnut.es

2493 ms

style.min.css

style.min.css

626 ms

shortcodes.css

shortcodes.css

532 ms

default.css

default.css

611 ms

style_default.css

style_default.css

514 ms

rtl-css.css

rtl-css.css

511 ms

header-template.css

header-template.css

643 ms

header-responsive.css

header-responsive.css

544 ms

corona.css

corona.css

918 ms

responsive-corona.css

responsive-corona.css

824 ms

woocommerce-layout.css

woocommerce-layout.css

626 ms

woocommerce.css

woocommerce.css

765 ms

xoo-wsc-fonts.css

xoo-wsc-fonts.css

715 ms

xoo-wsc-style.css

xoo-wsc-style.css

732 ms

icomoon.css

icomoon.css

854 ms

cache.skin.css

cache.skin.css

925 ms

js_composer.min.css

js_composer.min.css

1045 ms

rtwpvs.min.css

rtwpvs.min.css

878 ms

rtwpvs-tooltip.min.css

rtwpvs-tooltip.min.css

929 ms

style-editor.css

style-editor.css

964 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

990 ms

font-awesome.css

font-awesome.css

1018 ms

owl.carousel.min.css

owl.carousel.min.css

1022 ms

style.css

style.css

1235 ms

css

css

34 ms

style.css

style.css

1071 ms

default.css

default.css

996 ms

responsive.css

responsive.css

909 ms

prettyphoto.css

prettyphoto.css

911 ms

jquery.min.js

jquery.min.js

937 ms

jquery-migrate.min.js

jquery-migrate.min.js

965 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1018 ms

add-to-cart.min.js

add-to-cart.min.js

1017 ms

js.cookie.min.js

js.cookie.min.js

1060 ms

woocommerce.min.js

woocommerce.min.js

1076 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

1107 ms

underscore.min.js

underscore.min.js

1120 ms

wc-blocks.css

wc-blocks.css

919 ms

flexslider.css

flexslider.css

862 ms

public.css

public.css

891 ms

wp-util.min.js

wp-util.min.js

920 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

997 ms

xoo-wsc-main.js

xoo-wsc-main.js

928 ms

accounting.min.js

accounting.min.js

914 ms

selectWoo.full.min.js

selectWoo.full.min.js

899 ms

yith-wcan-shortcodes.min.js

yith-wcan-shortcodes.min.js

827 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

862 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

826 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

764 ms

jquery.countdown.js

jquery.countdown.js

736 ms

TimeCircles.js

TimeCircles.js

715 ms

main-elements.min.js

main-elements.min.js

701 ms

css

css

20 ms

owl.carousel.min.js

owl.carousel.min.js

723 ms

frontend.js

frontend.js

724 ms

swiper.min.js

swiper.min.js

701 ms

sourcebuster.min.js

sourcebuster.min.js

668 ms

order-attribution.min.js

order-attribution.min.js

676 ms

frontend.js

frontend.js

700 ms

rtwpvs.min.js

rtwpvs.min.js

688 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

639 ms

jquery.swipebox.js

jquery.swipebox.js

649 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

652 ms

jquery.cookie.min.js

jquery.cookie.min.js

665 ms

quick_view.js

quick_view.js

643 ms

owl.carousel.min.js

owl.carousel.min.js

632 ms

jquery.sticky.js

jquery.sticky.js

595 ms

throttle.js

throttle.js

612 ms

hover-intent.js

hover-intent.js

638 ms

greensock.js

greensock.js

665 ms

waypoints.js

waypoints.js

639 ms

parallax.js

parallax.js

628 ms

ytplayer.js

ytplayer.js

633 ms

pretty-photo.js

pretty-photo.js

661 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

656 ms

jquery.countto.js

jquery.countto.js

667 ms

jquery.smartmenus.js

jquery.smartmenus.js

533 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

536 ms

jquery.scrollto.js

jquery.scrollto.js

543 ms

custom.js

custom.js

581 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

595 ms

threesixty.min.js

threesixty.min.js

591 ms

js_composer_front.min.js

js_composer_front.min.js

588 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

588 ms

script.min.js

script.min.js

603 ms

icomoon.svg

icomoon.svg

868 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

667 ms

Woo-Side-Cart.woff

Woo-Side-Cart.woff

674 ms

LOGO-HAZELNUT-1.png

LOGO-HAZELNUT-1.png

651 ms

Banner-Inicio1.png

Banner-Inicio1.png

751 ms

Banner2s.png

Banner2s.png

647 ms

Banner-Inicio3.png

Banner-Inicio3.png

802 ms

Pantalla-inicio-CALZADO.png

Pantalla-inicio-CALZADO.png

713 ms

Pantalla-de-inicio-NUEVA-COLECCION.png

Pantalla-de-inicio-NUEVA-COLECCION.png

783 ms

6xn16ubu9_g.jpg

6xn16ubu9_g.jpg

665 ms

6xn16tzxp_g.jpg

6xn16tzxp_g.jpg

770 ms

6xn161l0w_g.jpg

6xn161l0w_g.jpg

766 ms

6xn1616ut_g.jpg

6xn1616ut_g.jpg

763 ms

6xn15fxmc_g.jpg

6xn15fxmc_g.jpg

769 ms

6xn15fnmv_g.jpg

6xn15fnmv_g.jpg

729 ms

6xn15fkkh_g.jpg

6xn15fkkh_g.jpg

751 ms

6xn1562ae_g.jpg

6xn1562ae_g.jpg

767 ms

6xn14sf2x_g.jpg

6xn14sf2x_g.jpg

765 ms

6xn14s3jt_g.jpg

6xn14s3jt_g.jpg

754 ms

6xn1553my_g.jpg

6xn1553my_g.jpg

773 ms

6xn13xdev_g-2.jpg

6xn13xdev_g-2.jpg

733 ms

6xn14b8bw_g.jpg

6xn14b8bw_g.jpg

756 ms

6xn13mf8s_g-1.jpg

6xn13mf8s_g-1.jpg

776 ms

6x20z6cpr_g.jpg

6x20z6cpr_g.jpg

763 ms

6x20z63l9_g.jpg

6x20z63l9_g.jpg

751 ms

6x20z6keb_g.jpg

6x20z6keb_g.jpg

774 ms

6x20yuwip_g-1.jpg

6x20yuwip_g-1.jpg

746 ms

6x20ytbfd_g.jpg

6x20ytbfd_g.jpg

764 ms

6x20yk8em_g.jpg

6x20yk8em_g.jpg

878 ms

logo_hazelnut_blanco-300x43.png

logo_hazelnut_blanco-300x43.png

845 ms

bg_direction_nav.png

bg_direction_nav.png

594 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

116 ms

Accessibility Review

hazelnut.es accessibility score

89

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

hazelnut.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hazelnut.es SEO score

83

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hazelnut.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Hazelnut.es 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

hazelnut.es

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