Tools & Wizards About Us
hortilux.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hortilux.com

LED, HPS and hybrid grow light solutions | hortilux.com

Page Load Speed

6.4 sec in total

First Response

647 ms

Resources Loaded

5.4 sec

Page Rendered

385 ms

hortilux.com screenshot

About Website

Welcome to hortilux.com homepage info - get ready to check Hortilux best content right away, or after learning these important things about hortilux.com

Hortilux offers complete grow light solutions (LED, HPS and hybrid) for international horticulture and indoor farming.

Visit hortilux.com

Key Findings

We analyzed Hortilux.com page load time and found that the first response time was 647 ms and then it took 5.8 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

hortilux.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.273

45/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

www.hortilux.com

647 ms

gtm.js

99 ms

jquery-3.6.0.min.js

41 ms

wpo-minify-header-b155dc35.min.css

271 ms

jquery.min.js

352 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 80% of them (44 requests) were addressed to the original Hortilux.com, 4% (2 requests) were made to Cdn.jsdelivr.net and 4% (2 requests) were made to Cdn.plyr.io. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Hortilux.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.7 kB (72%)

Content Size

109.6 kB

After Optimization

30.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hortilux.com main page is 109.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. HTML takes 96.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 78.6 kB

  • Original 96.3 kB
  • After minification 86.7 kB
  • After compression 17.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 78.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-1%

Potential reduce by 100 B

  • Original 7.7 kB
  • After minification 7.7 kB
  • After compression 7.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 4.0 kB
  • After minification 4.0 kB
  • After compression 4.0 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. Hortilux.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (69%)

Requests Now

51

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hortilux.com

www.hortilux.com

647 ms

gtm.js

gtm.js

99 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

41 ms

wpo-minify-header-b155dc35.min.css

wpo-minify-header-b155dc35.min.css

271 ms

jquery.min.js

jquery.min.js

352 ms

jquery-migrate.min.js

jquery-migrate.min.js

262 ms

cookie-law-info-public.js

cookie-law-info-public.js

263 ms

wpmm-featuresbox.js

wpmm-featuresbox.js

262 ms

wpmm-gridpost.js

wpmm-gridpost.js

264 ms

script.min.js

script.min.js

350 ms

objectfit.js

objectfit.js

350 ms

scripts.js

scripts.js

350 ms

slick.min.js

slick.min.js

65 ms

sticky-menu.js

sticky-menu.js

447 ms

wpmm-pricing.js

wpmm-pricing.js

447 ms

front.js

front.js

449 ms

wpo-minify-footer-3f973a37.min.css

wpo-minify-footer-3f973a37.min.css

532 ms

hooks.min.js

hooks.min.js

447 ms

i18n.min.js

i18n.min.js

447 ms

index.js

index.js

449 ms

index.js

index.js

447 ms

wpmm.js

wpmm.js

523 ms

wpcf7r-fe.js

wpcf7r-fe.js

524 ms

featuresbox-pro.js

featuresbox-pro.js

530 ms

wpmm-product-category.js

wpmm-product-category.js

530 ms

wpmm-vertical-menu.js

wpmm-vertical-menu.js

560 ms

plyr.js

plyr.js

705 ms

wpmm-videowidget.js

wpmm-videowidget.js

613 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

61 ms

local.js

local.js

622 ms

responsive-menu.js

responsive-menu.js

618 ms

lazyload.min.js

lazyload.min.js

628 ms

plyr.css

plyr.css

27 ms

slick.css

slick.css

10 ms

jquery.matchHeight.js

jquery.matchHeight.js

357 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

49 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

437 ms

plyr.polyfilled.js

plyr.polyfilled.js

20 ms

diffuser.js

diffuser.js

34 ms

prism.app-us1.com

prism.app-us1.com

92 ms

brand-logo.png

brand-logo.png

64 ms

logo_fc-e1578297540681.png

logo_fc-e1578297540681.png

94 ms

Ter-Laak-website-scaled.jpg

Ter-Laak-website-scaled.jpg

701 ms

NXTLED-1000-Middel.png

NXTLED-1000-Middel.png

585 ms

2-AndreRichard.jpeg

2-AndreRichard.jpeg

541 ms

3-realiseren-van-het-ideale-groeilichtsysteem.jpg

3-realiseren-van-het-ideale-groeilichtsysteem.jpg

441 ms

4-WIJ-HELPEN-U-MET-HET-EFFICI%C3%8BNT-INZETTEN-VAN-UW-GROEILICHT.jpg

4-WIJ-HELPEN-U-MET-HET-EFFICI%C3%8BNT-INZETTEN-VAN-UW-GROEILICHT.jpg

2736 ms

Armaturen-Strafostations_65.jpg

Armaturen-Strafostations_65.jpg

427 ms

IMG_5279-Middel.jpg

IMG_5279-Middel.jpg

602 ms

NXTLED-1400-Middel.png

NXTLED-1400-Middel.png

617 ms

Rosa-Danica-5-scaled.jpg

Rosa-Danica-5-scaled.jpg

892 ms

57-SKP_7411.jpg

57-SKP_7411.jpg

674 ms

afbeelding-1.jpg

afbeelding-1.jpg

690 ms

20210317-Hortilux-9479-Web-scaled-e1617791926824.jpg

20210317-Hortilux-9479-Web-scaled-e1617791926824.jpg

708 ms

logo-cookieyes.svg

logo-cookieyes.svg

764 ms

Accessibility Review

hortilux.com accessibility score

94

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

hortilux.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hortilux.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortilux.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 Hortilux.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

hortilux.com

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