Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

hemelvlucht.nl

Home-2 - Hemelvlucht

Page Load Speed

2.5 sec in total

First Response

368 ms

Resources Loaded

1.9 sec

Page Rendered

241 ms

About Website

Click here to check amazing Hemelvlucht content. Otherwise, check out these important facts you probably never knew about hemelvlucht.nl

Hemelvlucht Hemelvlucht is de verzorger van de Heliumballon uitvaart in Nederland. U heeft de mogelijkheid om de as van uw dierbare met een Heliumballon te verstrooien op een hoogte van 24 kilometer...

Visit hemelvlucht.nl

Key Findings

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

Performance Metrics

hemelvlucht.nl performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

hemelvlucht.nl

368 ms

hemelvlucht.nl

522 ms

style.min.css

92 ms

20f667732c163e41889eefc0bb827747.min.css

399 ms

jquery.min.js

347 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 91% of them (10 requests) were addressed to the original Hemelvlucht.nl, 9% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (522 ms) belongs to the original domain Hemelvlucht.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.2 kB (9%)

Content Size

1.1 MB

After Optimization

954.6 kB

In fact, the total size of Hemelvlucht.nl main page is 1.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. 15% of websites need less resources to load. Images take 690.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.2 kB

  • Original 43.5 kB
  • After minification 42.4 kB
  • After compression 9.3 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 34.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 690.9 kB
  • After minification 690.9 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. Hemelvlucht images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 24.0 kB

  • Original 151.6 kB
  • After minification 151.6 kB
  • After compression 127.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 24.0 kB or 16% of the original size.

CSS Optimization

-24%

Potential reduce by 41.0 kB

  • Original 167.8 kB
  • After minification 167.8 kB
  • After compression 126.8 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. Hemelvlucht.nl needs all CSS files to be minified and compressed as it can save up to 41.0 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (38%)

Requests Now

8

After Optimization

5

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

Accessibility Review

hemelvlucht.nl accessibility score

100

Accessibility Issues

Best Practices

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

hemelvlucht.nl SEO score

93

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

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 Hemelvlucht.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 Hemelvlucht.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 Hemelvlucht. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: