3.8 sec in total
1.3 sec
2.4 sec
145 ms
Click here to check amazing Odisee content for Belgium. Otherwise, check out these important facts you probably never knew about odisee.be
Sta je aan het begin van één van de spannendste avonturen van je leven en vliegen termen als bachelors, masters en leerkrediet je om de oren? Of ben j...
Visit odisee.beWe analyzed Odisee.be page load time and found that the first response time was 1.3 sec and then it took 2.6 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.
odisee.be performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value6.1 s
12/100
25%
Value8.3 s
19/100
10%
Value1,500 ms
14/100
30%
Value0
100/100
15%
Value15.6 s
6/100
10%
1252 ms
439 ms
178 ms
346 ms
366 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 60% of them (28 requests) were addressed to the original Odisee.be, 13% (6 requests) were made to Pixel.mathtag.com and 9% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Odisee.be.
Page size can be reduced by 124.1 kB (50%)
246.3 kB
122.3 kB
In fact, the total size of Odisee.be main page is 246.3 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. 40% of websites need less resources to load. Javascripts take 178.6 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.0 kB or 81% of the original size.
Potential reduce by 5.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. Obviously, Odisee needs image optimization as it can save up to 5.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 85.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 85.6 kB or 48% of the original size.
Potential reduce by 58 B
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. Odisee.be needs all CSS files to be minified and compressed as it can save up to 58 B or 26% of the original size.
Number of requests can be reduced by 33 (79%)
42
9
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odisee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.odisee.be
1252 ms
ODISEE_SCREENCSS.css
439 ms
ODISEE_HOMESCREENCSS.css
178 ms
ODISEE_RESPONSIVECSS.css
346 ms
ODISEE_FANCYBOXCSS.css
366 ms
ScfStyles.css
450 ms
css
66 ms
jquery.min.js
80 ms
jquery.easing.1.3.js
249 ms
slides.min.jquery.js
344 ms
masonry.pkgd.min.js
340 ms
dropmenu.js
426 ms
jquery.fancybox-1.3.4.pack.js
509 ms
AC_RunActiveContent.js
428 ms
swfobject.js
276 ms
js
22 ms
Odisee_pdfjpg.jpg
110 ms
demo-logo.jpg
111 ms
zoekback.gif
109 ms
zoekglas.png
108 ms
ODISEE-Nederlands-Images-transparant.gif
111 ms
Taal-select.gif
111 ms
ODISEE-Nederlands-Images-dropdown_background.gif
212 ms
Bol-vluchtelingen.png
211 ms
Streepke.gif
211 ms
(30690)-Nederlands-Footer-Social-Media-Facebook.gif
210 ms
(30690)-Nederlands-Footer-Social-Media-Youtube.gif
213 ms
(30690)-Nederlands-Footer-Social-Media-Twitter.gif
211 ms
Instagram.png
311 ms
ODISEE-Nederlands-Images-associatie_logo.gif
293 ms
widgets.js
19 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
85 ms
i.js
117 ms
analytics.js
34 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
24 ms
collect
26 ms
syndication
123 ms
511395703700979713
419 ms
511395703700979713
311 ms
js
39 ms
img
19 ms
ODISEE_PRINTCSS.css
96 ms
iframe
35 ms
img
92 ms
img
72 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
odisee.be accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
odisee.be SEO score
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
Document uses legible font sizes
NL
NL
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odisee.be 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 Odisee.be main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
odisee.be
Open Graph description is not detected on the main page of Odisee. 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: