Tools & Wizards About Us
henofa.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

henofa.com

Industrieel vilt kopen voor Tuinbouw, Bouw en Technische vilten - Henofa

Page Load Speed

2.8 sec in total

First Response

294 ms

Resources Loaded

2 sec

Page Rendered

487 ms

henofa.com screenshot

About Website

Click here to check amazing Henofa content. Otherwise, check out these important facts you probably never knew about henofa.com

Industrieel vilt kopen bij een goede leverancier? Henofa is een erkende producent en leverancier van vilt en nonwoven voor o.a. de Tuinbouw en de bouw.

Visit henofa.com

Key Findings

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

Performance Metrics

henofa.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

henofa.com

294 ms

henofa.com

487 ms

css

31 ms

js_composer.min.css

184 ms

settings.css

250 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 83% of them (40 requests) were addressed to the original Henofa.com, 13% (6 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (754 ms) belongs to the original domain Henofa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 180.2 kB (9%)

Content Size

2.0 MB

After Optimization

1.8 MB

  • HTML
  • Images

In fact, the total size of Henofa.com main page is 2.0 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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 71.2 kB

  • Original 87.3 kB
  • After minification 84.1 kB
  • After compression 16.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 71.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 109.0 kB

  • Original 1.9 MB
  • After minification 1.8 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. Henofa images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 27 (71%)

Requests Now

38

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

henofa.com

henofa.com

294 ms

henofa.com

henofa.com

487 ms

css

css

31 ms

js_composer.min.css

js_composer.min.css

184 ms

settings.css

settings.css

250 ms

styles.css

styles.css

256 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

258 ms

style.min.css

style.min.css

259 ms

style.min.css

style.min.css

269 ms

style.css

style.css

278 ms

wpex-visual-composer.css

wpex-visual-composer.css

332 ms

jquery.min.js

jquery.min.js

425 ms

jquery-migrate.min.js

jquery-migrate.min.js

345 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

438 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

458 ms

js

js

54 ms

animate.min.css

animate.min.css

366 ms

vc_material.min.css

vc_material.min.css

413 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

435 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

472 ms

wp-polyfill.min.js

wp-polyfill.min.js

582 ms

hooks.min.js

hooks.min.js

576 ms

i18n.min.js

i18n.min.js

576 ms

index.js

index.js

575 ms

index.js

index.js

576 ms

wpcf7r-fe.js

wpcf7r-fe.js

576 ms

total.min.js

total.min.js

619 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

624 ms

vcex-front.min.js

vcex-front.min.js

628 ms

js_composer_front.min.js

js_composer_front.min.js

629 ms

vc-waypoints.min.js

vc-waypoints.min.js

647 ms

Over-Henofa-1-1920-1080.jpg

Over-Henofa-1-1920-1080.jpg

618 ms

HOME-2.jpg

HOME-2.jpg

626 ms

Nieuws-1.jpg

Nieuws-1.jpg

754 ms

HOME-4-1920-500x350.jpg

HOME-4-1920-500x350.jpg

292 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

69 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

201 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

202 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

201 ms

ticons-webfont.woff

ticons-webfont.woff

312 ms

vc_material.ttf

vc_material.ttf

139 ms

logonorm.png

logonorm.png

223 ms

nl.png

nl.png

219 ms

en.png

en.png

305 ms

de.png

de.png

312 ms

es.png

es.png

355 ms

Accessibility Review

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

Best Practices

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

henofa.com SEO score

98

Search Engine Optimization Advices

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

henofa.com

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