Tools & Wizards About Us

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

futurefun.nl

Home - Future Fun Ballooning

Page Load Speed

2.6 sec in total

First Response

339 ms

Resources Loaded

2.1 sec

Page Rendered

204 ms

About Website

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

Key Findings

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

Performance Metrics

futurefun.nl performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value6,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

futurefun.nl

339 ms

www.futurefun.nl

377 ms

jquery.min.js

7 ms

jquery.validate.min.js

54 ms

sitemapstyler.js

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 Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (51%)

Content Size

2.0 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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.4 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 17.6 kB

  • Original 24.2 kB
  • After minification 24.0 kB
  • After compression 6.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.

Image Optimization

-6%

Potential reduce by 38.8 kB

  • Original 604.7 kB
  • After minification 566.0 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.

JavaScript Optimization

-69%

Potential reduce by 936.6 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 428.6 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 936.6 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 42.0 kB

  • Original 50.6 kB
  • After minification 43.9 kB
  • After compression 8.5 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.

Requests Breakdown

Number of requests can be reduced by 33 (45%)

Requests Now

73

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

futurefun.nl accessibility score

88

Accessibility Issues

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

<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

High

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

Best Practices

futurefun.nl best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

futurefun.nl SEO score

77

Search Engine Optimization Advices

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

Social Sharing Optimization

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: