3.1 sec in total
610 ms
2.3 sec
212 ms
Click here to check amazing Olifant content. Otherwise, check out these important facts you probably never knew about olifant.nl
Visit olifant.nlWe 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.
olifant.nl performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
610 ms
667 ms
84 ms
169 ms
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 size can be reduced by 370.0 kB (48%)
765.4 kB
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.
Potential reduce by 13.0 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.
Potential reduce by 2.7 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.
Potential reduce by 328.8 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.
Potential reduce by 25.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.
Number of requests can be reduced by 17 (55%)
31
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.
olifant.nl
610 ms
www.olifant.com
667 ms
jceutilities-220.css
84 ms
style.css
169 ms
jcemediabox.css
173 ms
style.css
172 ms
mod_jflanguageselection.css
175 ms
mootools.js
275 ms
mediaobject.js
177 ms
jceutilities-220.js
251 ms
caption.js
255 ms
jcemediabox.js
339 ms
template.css
259 ms
jquery.js
480 ms
jquery.fullbg.min.js
331 ms
yahoo.js
336 ms
animation.js
431 ms
dom.js
361 ms
event.js
520 ms
jdialog.js
420 ms
ga.js
28 ms
achtergrond-tijdelijk.jpg
444 ms
logo-DeOlifant.png
88 ms
fw_nieuwegilde.png
89 ms
spacer.gif
86 ms
foto-modern.jpg
498 ms
fw_olifantje.png
89 ms
fw_eenhoorntje.png
169 ms
transparant-zwart.png
173 ms
stippellijn.gif
177 ms
popup.html
161 ms
tooltip.html
239 ms
__utm.gif
11 ms
olifant.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
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
<html> element does not have a [lang] attribute
olifant.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
olifant.nl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
EN
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.
olifant.nl
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: