Tools & Wizards About Us
joho.nl screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

joho.nl

JoHo: voor werken in het buitenland tot backpacken en emigratie tot vrijwilligerswerk | World of JoHo

Page Load Speed

2.8 sec in total

First Response

389 ms

Resources Loaded

2.2 sec

Page Rendered

199 ms

joho.nl screenshot

About Website

Welcome to joho.nl homepage info - get ready to check Jo Ho best content for Netherlands right away, or after learning these important things about joho.nl

Visit joho.nl

Key Findings

We analyzed Joho.nl page load time and found that the first response time was 389 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

joho.nl performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

joho.nl

389 ms

joho.nl

435 ms

gtag.js

294 ms

superfish.css

282 ms

ajax-progress.module.css

283 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 83% of them (62 requests) were addressed to the original Joho.nl, 7% (5 requests) were made to Use.fontawesome.com and 5% (4 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (976 ms) belongs to the original domain Joho.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.4 kB (26%)

Content Size

1.2 MB

After Optimization

860.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Joho.nl main page is 1.2 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. Javascripts take 666.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 54.3 kB

  • Original 72.5 kB
  • After minification 70.1 kB
  • After compression 18.2 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 54.3 kB or 75% of the original size.

Image Optimization

-18%

Potential reduce by 20.2 kB

  • Original 110.4 kB
  • After minification 90.3 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. Obviously, Jo Ho needs image optimization as it can save up to 20.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 6.8 kB

  • Original 666.5 kB
  • After minification 666.3 kB
  • After compression 659.7 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

-70%

Potential reduce by 218.1 kB

  • Original 310.2 kB
  • After minification 308.9 kB
  • After compression 92.1 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. Joho.nl needs all CSS files to be minified and compressed as it can save up to 218.1 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (91%)

Requests Now

69

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

joho.nl

joho.nl

389 ms

joho.nl

joho.nl

435 ms

gtag.js

gtag.js

294 ms

superfish.css

superfish.css

282 ms

ajax-progress.module.css

ajax-progress.module.css

283 ms

align.module.css

align.module.css

285 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

285 ms

fieldgroup.module.css

fieldgroup.module.css

286 ms

container-inline.module.css

container-inline.module.css

378 ms

clearfix.module.css

clearfix.module.css

376 ms

details.module.css

details.module.css

377 ms

hidden.module.css

hidden.module.css

398 ms

item-list.module.css

item-list.module.css

397 ms

js.module.css

js.module.css

396 ms

nowrap.module.css

nowrap.module.css

539 ms

position-container.module.css

position-container.module.css

537 ms

progress.module.css

progress.module.css

539 ms

reset-appearance.module.css

reset-appearance.module.css

540 ms

resize.module.css

resize.module.css

540 ms

sticky-header.module.css

sticky-header.module.css

541 ms

system-status-counter.css

system-status-counter.css

595 ms

system-status-report-counters.css

system-status-report-counters.css

595 ms

system-status-report-general-info.css

system-status-report-general-info.css

593 ms

tabledrag.module.css

tabledrag.module.css

594 ms

tablesort.module.css

tablesort.module.css

593 ms

tree-child.module.css

tree-child.module.css

592 ms

views.module.css

views.module.css

683 ms

addtoany.css

addtoany.css

687 ms

extlink.css

extlink.css

685 ms

paragraphs.unpublished.css

paragraphs.unpublished.css

683 ms

node.css

node.css

684 ms

style.min.css

style.min.css

781 ms

style.css

style.css

976 ms

img-fluid.css

img-fluid.css

775 ms

roboto.css

roboto.css

775 ms

css

css

49 ms

all.css

all.css

53 ms

messages-white.css

messages-white.css

778 ms

affix.css

affix.css

777 ms

all.js

all.js

146 ms

v4-shims.js

v4-shims.js

69 ms

page.js

page.js

44 ms

jquery.min.js

jquery.min.js

957 ms

once.min.js

once.min.js

594 ms

nl_1eWM1AnGD2r7bAgZ272KnoeThiP5AL8dVzu2mXXoRUM.js

nl_1eWM1AnGD2r7bAgZ272KnoeThiP5AL8dVzu2mXXoRUM.js

600 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

600 ms

drupal.js

drupal.js

600 ms

drupal.init.js

drupal.init.js

686 ms

addtoany.js

addtoany.js

640 ms

js

js

80 ms

google_analytics.js

google_analytics.js

603 ms

bootstrap.min.js

bootstrap.min.js

604 ms

barrio.js

barrio.js

669 ms

custom.js

custom.js

670 ms

extlink.js

extlink.js

677 ms

fa-solid-900.woff

fa-solid-900.woff

12 ms

fa-regular-400.woff

fa-regular-400.woff

10 ms

apbct-functions.js

apbct-functions.js

674 ms

apbct-public.js

apbct-public.js

534 ms

statistics.js

statistics.js

536 ms

superfish.js

superfish.js

616 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

617 ms

sfsmallscreen.js

sfsmallscreen.js

634 ms

supposition.js

supposition.js

585 ms

supersubs.js

supersubs.js

575 ms

superfish.js

superfish.js

583 ms

affix.js

affix.js

653 ms

wereldkaart_hangmat.nl_met_joho_voetjes_1200x200px_png.png

wereldkaart_hangmat.nl_met_joho_voetjes_1200x200px_png.png

747 ms

wereldstage_klein.jpg

wereldstage_klein.jpg

764 ms

logo_vrijwilligwereldwijd_vrijwilligerswerk_buitenland.png

logo_vrijwilligwereldwijd_vrijwilligerswerk_buitenland.png

730 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

19 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

25 ms

sm.25.html

sm.25.html

17 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

36 ms

icons.38.svg.js

icons.38.svg.js

66 ms

Accessibility Review

joho.nl accessibility score

95

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

joho.nl 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

joho.nl SEO score

80

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

joho.nl

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