Tools & Wizards About Us
hortalia.net screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hortalia.net

Horticultura, jardinería, y separadores de ambiente | Hortalia

Page Load Speed

4.2 sec in total

First Response

278 ms

Resources Loaded

3.2 sec

Page Rendered

647 ms

hortalia.net screenshot

About Website

Visit hortalia.net now to see the best up-to-date Hortalia content for Spain and also check out these interesting facts you probably never knew about hortalia.net

Hortalia · Horticultura y jardinería · Separación de ambientes · Huertos urbanos · Jardineras verticales · ¡Descubre lo que te podemos ofrecer!

Visit hortalia.net

Key Findings

We analyzed Hortalia.net page load time and found that the first response time was 278 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

hortalia.net performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.106

88/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

hortalia.net

278 ms

www.hortalia.net

540 ms

style.min.css

93 ms

styles.css

181 ms

cookies-and-content-security-policy.min.css

260 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 91% of them (84 requests) were addressed to the original Hortalia.net, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Hortalia.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.3 kB (12%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hortalia.net main page is 1.5 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 730.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 94.9 kB

  • Original 120.6 kB
  • After minification 116.9 kB
  • After compression 25.7 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 94.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 730.4 kB
  • After minification 730.4 kB

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. Hortalia images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 51.2 kB

  • Original 362.0 kB
  • After minification 362.0 kB
  • After compression 310.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 51.2 kB or 14% of the original size.

CSS Optimization

-14%

Potential reduce by 44.2 kB

  • Original 323.7 kB
  • After minification 323.6 kB
  • After compression 279.5 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. Hortalia.net needs all CSS files to be minified and compressed as it can save up to 44.2 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hortalia.net

hortalia.net

278 ms

www.hortalia.net

www.hortalia.net

540 ms

style.min.css

style.min.css

93 ms

styles.css

styles.css

181 ms

cookies-and-content-security-policy.min.css

cookies-and-content-security-policy.min.css

260 ms

style.css

style.css

265 ms

woocommerce-layout.css

woocommerce-layout.css

269 ms

woocommerce.css

woocommerce.css

274 ms

trp-language-switcher.css

trp-language-switcher.css

278 ms

fancybox.css

fancybox.css

279 ms

font-awesome.min.css

font-awesome.min.css

37 ms

nickx-front.css

nickx-front.css

344 ms

dashicons.min.css

dashicons.min.css

440 ms

style.min.css

style.min.css

366 ms

font-awesome.min.css

font-awesome.min.css

368 ms

grid-system.css

grid-system.css

371 ms

style.css

style.css

609 ms

header-secondary-nav.css

header-secondary-nav.css

448 ms

simple-dropdown.css

simple-dropdown.css

456 ms

element-fancy-box.css

element-fancy-box.css

456 ms

magnific.css

magnific.css

459 ms

responsive.css

responsive.css

528 ms

woocommerce.css

woocommerce.css

541 ms

select2.css

select2.css

550 ms

style.css

style.css

551 ms

skin-material.css

skin-material.css

643 ms

js_composer.min.css

js_composer.min.css

629 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

635 ms

css

css

40 ms

breeze-prefetch-links.min.js

breeze-prefetch-links.min.js

640 ms

jquery.min.js

jquery.min.js

732 ms

jquery-migrate.min.js

jquery-migrate.min.js

692 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

703 ms

add-to-cart.min.js

add-to-cart.min.js

722 ms

js.cookie.min.js

js.cookie.min.js

724 ms

woocommerce.min.js

woocommerce.min.js

743 ms

trp-frontend-compatibility.js

trp-frontend-compatibility.js

776 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

791 ms

wc-blocks.css

wc-blocks.css

809 ms

iconsmind.css

iconsmind.css

730 ms

animate.min.css

animate.min.css

649 ms

underscore.min.js

underscore.min.js

571 ms

wp-util.min.js

wp-util.min.js

605 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

647 ms

index.js

index.js

640 ms

index.js

index.js

639 ms

js.cookie.min.js

js.cookie.min.js

687 ms

cookies-and-content-security-policy.min.js

cookies-and-content-security-policy.min.js

621 ms

cookies-and-content-security-policy-error-message.js

cookies-and-content-security-policy-error-message.js

609 ms

salient-social.js

salient-social.js

673 ms

sourcebuster.min.js

sourcebuster.min.js

697 ms

order-attribution.min.js

order-attribution.min.js

699 ms

jquery.fancybox.js

jquery.fancybox.js

692 ms

nickx.front.js

nickx.front.js

622 ms

jquery.easing.js

jquery.easing.js

618 ms

jquery.mousewheel.js

jquery.mousewheel.js

636 ms

priority.js

priority.js

681 ms

transit.js

transit.js

609 ms

waypoints.js

waypoints.js

581 ms

modernizr.js

modernizr.js

592 ms

imagesLoaded.min.js

imagesLoaded.min.js

789 ms

hoverintent.js

hoverintent.js

714 ms

magnific.js

magnific.js

712 ms

superfish.js

superfish.js

702 ms

init.js

init.js

751 ms

touchswipe.min.js

touchswipe.min.js

684 ms

select2.full.min.js

select2.full.min.js

655 ms

quick_view_actions.js

quick_view_actions.js

643 ms

flickity.min.js

flickity.min.js

624 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

623 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

605 ms

wp-polyfill.min.js

wp-polyfill.min.js

605 ms

index.js

index.js

610 ms

search.min.js

search.min.js

616 ms

js_composer_front.min.js

js_composer_front.min.js

595 ms

hortalia-svg22.svg

hortalia-svg22.svg

528 ms

hortalia-riego-1.jpg

hortalia-riego-1.jpg

722 ms

PothusExpositor-1024x576.jpg

PothusExpositor-1024x576.jpg

692 ms

Hortalia_Separadores.jpg

Hortalia_Separadores.jpg

773 ms

jardineras-hortalia.jpg

jardineras-hortalia.jpg

690 ms

Podium_3.jpg

Podium_3.jpg

882 ms

be.js

be.js

160 ms

huertos-urbanos.jpg

huertos-urbanos.jpg

644 ms

campanile-ambiente.jpg

campanile-ambiente.jpg

771 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

107 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

107 ms

L0xhDFMnlVwD4h3Lt9JWnbX3jG-2X5XHE1ofFg.ttf

L0xhDFMnlVwD4h3Lt9JWnbX3jG-2X5XHE1ofFg.ttf

135 ms

L0xhDFMnlVwD4h3Lt9JWnbX3jG-2X3LAE1ofFg.ttf

L0xhDFMnlVwD4h3Lt9JWnbX3jG-2X3LAE1ofFg.ttf

135 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

811 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

71 ms

iconsmind.ttf

iconsmind.ttf

795 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

90 ms

Accessibility Review

hortalia.net accessibility score

88

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hortalia.net best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

hortalia.net SEO score

93

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

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 Hortalia.net 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 Hortalia.net 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

hortalia.net

Open Graph data is detected on the main page of Hortalia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: