Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

3.1 sec in total

First Response

610 ms

Resources Loaded

2.3 sec

Page Rendered

212 ms

olifant.nl screenshot

About Website

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

Visit olifant.nl

Key Findings

We analyzed Olifant.nl page load time and found that the first response time was 610 ms and then it took 2.5 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

olifant.nl performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

olifant.nl

610 ms

www.olifant.com

667 ms

jceutilities-220.css

84 ms

style.css

169 ms

jcemediabox.css

173 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Olifant.nl, 91% (30 requests) were made to Olifant.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (667 ms) relates to the external source Olifant.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 370.0 kB (48%)

Content Size

765.4 kB

After Optimization

395.4 kB

In fact, the total size of Olifant.nl main page is 765.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 450.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 13.0 kB

  • Original 17.3 kB
  • After minification 14.7 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 13.0 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 2.7 kB

  • Original 267.0 kB
  • After minification 264.3 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. Olifant images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 328.8 kB

  • Original 450.1 kB
  • After minification 356.4 kB
  • After compression 121.3 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 328.8 kB or 73% of the original size.

CSS Optimization

-82%

Potential reduce by 25.5 kB

  • Original 31.0 kB
  • After minification 24.4 kB
  • After compression 5.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. Olifant.nl needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (55%)

Requests Now

31

After Optimization

14

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

Accessibility Review

olifant.nl accessibility score

68

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

Document doesn't have a <title> element

Internationalization and localization

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

Impact

Issue

High

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

Best Practices

olifant.nl best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

olifant.nl SEO score

55

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olifant.nl can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Olifant.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 Olifant. 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: