Access splesj.nl. Waterspeelpark Splesj in Hoeven

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

splesj.nl

286 ms

splesj

562 ms

molecaten.min.css

339 ms

molecaten.min.js

622 ms

analytics.js

4 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Splesj.nl, 17% (19 requests) were made to Cdn03.molecaten.nl and 16% (18 requests) were made to Cdn02.molecaten.nl. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cdn03.molecaten.nl.

Content Size

3.1 MB

After Optimization

2.5 MB

In fact, the total size of Splesj.nl main page is 3.1 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 62.0 kB

Original 75.7 kB
After minification 68.9 kB
After compression 13.8 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 62.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 72.0 kB

Original 2.2 MB
After minification 2.2 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. Splesj images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 447.8 kB

Original 729.9 kB
After minification 723.3 kB
After compression 282.0 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 447.8 kB or 61% of the original size.

CSS Optimization

-79%

Potential reduce by 64.3 kB

Original 81.6 kB
After minification 81.4 kB
After compression 17.3 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. Splesj.nl needs all CSS files to be minified and compressed as it can save up to 64.3 kB or 79% of the original size.

Requests Now

105

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

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

splesj.nl

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Waterspeelpark Splesj in Hoeven | Een spetterend dagje uit

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

splesj.nl

splesj

molecaten.min.css

molecaten.min.js

analytics.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

splesj.nl

splesj

molecaten.min.css

molecaten.min.js

analytics.js

WebResource.axd

ScriptResource.axd

ScriptResource.axd

1-Splesj

2-Splesj

4a-Splesj

4-Splesj

6-Splesj

9c-Splesj

9-Splesj

Splesj-airtrampoline

Splesj-Fast4Fun-zwembad-spraypark

Splesj-Sidewinder-1

Splesj-Spraypark-ligweide

Splesj-Spraypark-Watertuin-2

Splesj-Spraypark-Watertuin-5

Splesj-Spraypark-Watertuin-6

Splesj-SuperCrater-2

Splesj-SuperCrater-3a

Splesj-WildWaterRiverRide-2

Splesj-WildWaterRiverRide-3

Nederland-kaart-met-pins-klein.jpg

LK-Wie-werkt-bij-2015.JPG

brochure_cover_2016-klein.jpg

9b-Splesj

Splesj-duikbassin

Splesj-Fast4Fun-3

Splesj-Fast4Fun-4

Splesj-Sidewinder-2

Splesj-Sidewinder-3

Splesj-Spraypark-1a

Splesj-Vijver-2

Splesj-WildWaterRiverRide-1a

Splesj-Fast4Fun-5

Splesj-glijbanen-zwembad-3

Splesj-glijbanen-zwembad-4

Splesj-Spraypark-3

Splesj-Spraypark-3a