Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 0

    Best Practices

  • 100

    SEO

    Google-friendlier than
    95% of websites

alfheim.nl

Inspirerende vergaderlocatie - Buitenplaats de Heeserhof

Page Load Speed

20.9 sec in total

First Response

3.1 sec

Resources Loaded

17.6 sec

Page Rendered

256 ms

alfheim.nl screenshot

About Website

Welcome to alfheim.nl homepage info - get ready to check Alfheim best content right away, or after learning these important things about alfheim.nl

Buitenplaats de Heeserhof is een inspirerende vergaderlocatie midden in de natuur! Bijzonder vergaderen? Bekijk alle mogelijkheden en voorzieningen!

Visit alfheim.nl

Key Findings

We analyzed Alfheim.nl page load time and found that the first response time was 3.1 sec and then it took 17.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

alfheim.nl performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.188

65/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.alfheim.nl

3056 ms

analytics.js

39 ms

wp-emoji-release.min.js

133 ms

layerslider.css

258 ms

css

34 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 78% of them (42 requests) were addressed to the original Alfheim.nl, 7% (4 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Meetingreview.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Alfheim.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (72%)

Content Size

4.2 MB

After Optimization

1.2 MB

In fact, the total size of Alfheim.nl main page is 4.2 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. CSS take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 50.8 kB

  • Original 73.4 kB
  • After minification 71.7 kB
  • After compression 22.7 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 50.8 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 562.9 kB
  • After minification 560.4 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. Alfheim images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 809.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 334.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 809.0 kB or 71% of the original size.

CSS Optimization

-90%

Potential reduce by 2.2 MB

  • Original 2.5 MB
  • After minification 2.3 MB
  • After compression 258.2 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. Alfheim.nl needs all CSS files to be minified and compressed as it can save up to 2.2 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (67%)

Requests Now

46

After Optimization

15

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

Accessibility Review

alfheim.nl accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

alfheim.nl SEO score

100

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