2.6 sec in total
339 ms
2.1 sec
204 ms
Click here to check amazing Future Fun content. Otherwise, check out these important facts you probably never knew about futurefun.nl
Een ballonvaart maken in Gelderland boven Achterhoek, of ballonvaren waar je maar wilt in Nederland. Met een ballonvaart ontdek je de regio op een bijzondere manier.
Visit futurefun.nlWe analyzed Futurefun.nl page load time and found that the first response time was 339 ms and then it took 2.3 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.
futurefun.nl performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.0 s
13/100
25%
Value8.4 s
18/100
10%
Value6,530 ms
0/100
30%
Value0.019
100/100
15%
Value17.5 s
4/100
10%
339 ms
377 ms
7 ms
54 ms
89 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 57% of them (46 requests) were addressed to the original Futurefun.nl, 12% (10 requests) were made to Maps.googleapis.com and 9% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (936 ms) belongs to the original domain Futurefun.nl.
Page size can be reduced by 1.0 MB (50%)
2.0 MB
1.0 MB
In fact, the total size of Futurefun.nl 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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 17.6 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 17.6 kB or 73% of the original size.
Potential reduce by 38.8 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. Future Fun images are well optimized though.
Potential reduce by 907.5 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 907.5 kB or 68% of the original size.
Potential reduce by 42.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. Futurefun.nl needs all CSS files to be minified and compressed as it can save up to 42.0 kB or 83% of the original size.
Number of requests can be reduced by 33 (45%)
73
40
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Fun. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
futurefun.nl
339 ms
www.futurefun.nl
377 ms
jquery.min.js
7 ms
jquery.validate.min.js
54 ms
sitemapstyler.js
89 ms
sitemapstyler.css
185 ms
base64.js
182 ms
site.js
183 ms
prettyPhoto.css
185 ms
css
26 ms
jquery.prettyPhoto.js
176 ms
jquery.nivo.slider.pack.js
177 ms
default.css
262 ms
nivo-slider.css
264 ms
template_css.css
270 ms
p7gs.css
268 ms
logo-facebook.png
109 ms
logo-twitter.png
110 ms
flag-nl.png
111 ms
flag-de.png
109 ms
ballon.png
179 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjc4LmpwZw==.jpg
356 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjc5LmpwZw==.jpg
355 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjgwLmpwZw==.jpg
355 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjgxLmpwZw==.jpg
576 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjgyLmpwZw==.jpg
366 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjgzLmpwZw==.jpg
577 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjg1LmpwZw==.jpg
588 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjExMy5iNjU5LmpwZWc=.jpg
615 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjExNC5lZjNhLmpwZWc=.jpg
616 ms
crop_580_280_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19nYWxsZXJ5LmZpbGVuYW1lLjExNS5kMGYyLmpwZWc=.jpg
631 ms
all.js
226 ms
maps
104 ms
background-site.jpg
581 ms
header.jpg
608 ms
menu-active.png
636 ms
background-maincontent.gif
636 ms
left-right_back.jpg
684 ms
bottom_left.jpg
683 ms
loading.gif
684 ms
thumb_160_0_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19iYW5uZXIuZmlsZW5hbWUuNTguY2QyNi5qcGVn.jpg
933 ms
thumb_160_0_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19iYW5uZXIuZmlsZW5hbWUuNjIuYTFhZi5qcGVn.jpg
932 ms
thumb_160_0_Li4vZ2Z4L3VzZXJpbWcvaXByb2Ntc19iYW5uZXIuZmlsZW5hbWUuOC44YWExLmpwZWc=.jpg
931 ms
logo-knvvl.png
933 ms
logo-pbn.png
934 ms
bottom_right.jpg
935 ms
footer.jpg
936 ms
Zd2E9abXLFGSr9G3YK2MsFzqCfRpIA3W6ypxnPISCPA.woff
41 ms
ga.js
37 ms
www.futurefun.nl
875 ms
overlay.png
874 ms
arrows.png
877 ms
bullets.png
875 ms
__utm.gif
19 ms
embed
37 ms
js
49 ms
init_embed.js
30 ms
109 ms
xd_arbiter.php
200 ms
xd_arbiter.php
355 ms
common.js
7 ms
util.js
29 ms
streetview.js
28 ms
google_white4.png
27 ms
marker.js
24 ms
imagery_viewer.js
21 ms
controls.js
99 ms
GeoPhotoService.GetMetadata
214 ms
transparent.png
51 ms
css
83 ms
geocoder.js
20 ms
sv4.png
41 ms
openhand_8_8.cur
57 ms
cbk
125 ms
GeoPhotoService.GetMetadata
52 ms
mapcnt6.png
35 ms
tmapctrl.png
34 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
18 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
22 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
25 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
26 ms
futurefun.nl accessibility score
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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
futurefun.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
futurefun.nl SEO score
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurefun.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 Futurefun.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.
futurefun.nl
Open Graph description is not detected on the main page of Future Fun. 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: