Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

janvis.nl

Jan Vis Entertainment ★ Hét adres voor artiesten en evenementen

Page Load Speed

4.5 sec in total

First Response

279 ms

Resources Loaded

3.1 sec

Page Rendered

1.1 sec

janvis.nl screenshot

About Website

Visit janvis.nl now to see the best up-to-date Jan Vis content for Netherlands and also check out these interesting facts you probably never knew about janvis.nl

Wilt u een artiest inhuren, een evenement organiseren of entertainment boeken? Jan Vis Entertainment heeft sinds 1963 geschikt entertainment voor ieder evenement!

Visit janvis.nl

Key Findings

We analyzed Janvis.nl page load time and found that the first response time was 279 ms and then it took 4.2 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

janvis.nl performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

janvis.nl

279 ms

janvis.nl

389 ms

www.janvis.nl

284 ms

www.janvis.nl

506 ms

app.css

205 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 81% of them (39 requests) were addressed to the original Janvis.nl, 6% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Janvis.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 489.6 kB (6%)

Content Size

8.4 MB

After Optimization

7.9 MB

In fact, the total size of Janvis.nl main page is 8.4 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 8.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 31.1 kB

  • Original 37.2 kB
  • After minification 23.8 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.1 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 426.6 kB

  • Original 8.1 MB
  • After minification 7.7 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. Jan Vis images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 32.0 kB

  • Original 183.8 kB
  • After minification 183.8 kB
  • After compression 151.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 32.0 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 38 B

  • Original 52.1 kB
  • After minification 52.1 kB
  • After compression 52.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. Janvis.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (18%)

Requests Now

38

After Optimization

31

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

Accessibility Review

janvis.nl accessibility score

100

Accessibility Issues

Best Practices

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

SEO Factors

janvis.nl SEO score

97

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

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