2.9 sec in total
585 ms
2.2 sec
94 ms
Click here to check amazing Leoz content. Otherwise, check out these important facts you probably never knew about leoz.nl
Welkom op de website van het Landelijk Expertisecentrum Onderwijszorg (LEOZ)
Visit leoz.nlWe analyzed Leoz.nl page load time and found that the first response time was 585 ms and then it took 2.3 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.
leoz.nl performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value4.6 s
35/100
25%
Value4.9 s
65/100
10%
Value410 ms
67/100
30%
Value0.224
56/100
15%
Value5.5 s
70/100
10%
585 ms
464 ms
202 ms
280 ms
203 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 97% of them (59 requests) were addressed to the original Leoz.nl, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Leoz.nl.
Page size can be reduced by 990.1 kB (78%)
1.3 MB
272.0 kB
In fact, the total size of Leoz.nl main page is 1.3 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. 25% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 16.8 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 16.8 kB or 74% of the original size.
Potential reduce by 48.5 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, Leoz needs image optimization as it can save up to 48.5 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 809.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 809.3 kB or 81% of the original size.
Potential reduce by 115.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. Leoz.nl needs all CSS files to be minified and compressed as it can save up to 115.5 kB or 86% of the original size.
Number of requests can be reduced by 27 (45%)
60
33
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Leoz. 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 7 to 1 for CSS and as a result speed up the page load time.
leoz.nl
585 ms
default.css
464 ms
SearchSkinObjectPreview.css
202 ms
skin.css
280 ms
container.css
203 ms
container.css
208 ms
portal.css
296 ms
jquery.js
916 ms
jquery-migrate.js
498 ms
jquery-ui.js
1126 ms
dnnmega.css
372 ms
WebResource.axd
427 ms
jquery.hoverIntent.min.js
386 ms
jquery.dnnmega.js
479 ms
Telerik.Web.UI.WebResource.axd
847 ms
dnn.js
516 ms
dnn.modalpopup.js
527 ms
dnn.servicesframework.js
572 ms
dnncore.js
613 ms
SearchSkinObjectPreview.js
626 ms
jquery.cycle.min.js
577 ms
Search.js
620 ms
initWidgets.js
645 ms
ga.js
14 ms
menu_extend.jpg
108 ms
menu_eind.jpg
99 ms
logo.jpg
103 ms
rootItemR1.png
127 ms
rootItemL1.png
109 ms
rootItemR2.png
135 ms
rootItemL2.png
190 ms
child-arrow.png
194 ms
rootItemR3.png
204 ms
rootItemL3.png
207 ms
rootItemR4.png
217 ms
rootItemL4.png
235 ms
search.png
282 ms
Action_16X16_Standard.png
284 ms
Title-BG-Grey2.png
312 ms
a.jpg
323 ms
logo%20semenarium.jpg
322 ms
logo%20windesheim.jpg
333 ms
__utm.gif
15 ms
Purple-Roze-TL.png
383 ms
Roze-Gradient-TR.png
384 ms
Roze-Gradient-T.png
391 ms
Roze-Gradient-BL.png
389 ms
Roze-Gradient-BR.png
399 ms
Roze-Gradient-B.png
407 ms
Yellow-Gradient-TL.png
475 ms
Yellow-Gradient-TR.png
475 ms
Yellow-Gradient-T.png
478 ms
Yellow-Gradient-BL.png
488 ms
Yellow-Gradient-BR.png
496 ms
Yellow-Gradient-B.png
506 ms
Purple-Gradient-TL.png
570 ms
Purple-Gradient-TR.png
570 ms
Purple-Gradient-T.png
573 ms
Purple-Gradient-BL.png
603 ms
Purple-Gradient-BR.png
602 ms
Purple-Gradient-B.png
604 ms
leoz.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
leoz.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
leoz.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Leoz.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 Dutch. Our system also found out that Leoz.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.
leoz.nl
Open Graph description is not detected on the main page of Leoz. 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: