4.4 sec in total
284 ms
3.6 sec
446 ms
Visit otys.be now to see the best up-to-date OTYS content and also check out these interesting facts you probably never knew about otys.be
OTYS is ontwikkeld voor recruiters, door recruiters, en biedt de informatie en efficiëntie die je nodig hebt om snel de beste kandidaat te plaatsen.
Visit otys.beWe analyzed Otys.be page load time and found that the first response time was 284 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
otys.be performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.4 s
20/100
25%
Value8.6 s
17/100
10%
Value1,960 ms
8/100
30%
Value0.035
100/100
15%
Value15.2 s
7/100
10%
284 ms
639 ms
250 ms
372 ms
335 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 76% of them (32 requests) were addressed to the original Otys.be, 10% (4 requests) were made to S7.addthis.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Otys.be.
Page size can be reduced by 937.2 kB (30%)
3.1 MB
2.2 MB
In fact, the total size of Otys.be main page is 3.1 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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 114.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 114.0 kB or 77% of the original size.
Potential reduce by 121.1 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. OTYS images are well optimized though.
Potential reduce by 508.7 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 508.7 kB or 67% of the original size.
Potential reduce by 193.4 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. Otys.be needs all CSS files to be minified and compressed as it can save up to 193.4 kB or 83% of the original size.
Number of requests can be reduced by 16 (44%)
36
20
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTYS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
otys.be
284 ms
www.otys.be
639 ms
globalStyling.css
250 ms
timeline.css
372 ms
style2013.css
335 ms
font-awesome.min.css
332 ms
jquery.js
502 ms
jquery.file.input.js
255 ms
smoothmenu-v.css
329 ms
smoothmenu-h.css
338 ms
jquery.smoothmenu.js
410 ms
jquery.magicSelect.js
412 ms
addthis_widget.js
57 ms
scripts2013.js
411 ms
font-awesome.css
250 ms
css
23 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
78 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
78 ms
ga.js
132 ms
bg.jpg
732 ms
logo.png
124 ms
logo2.png
125 ms
lang.png
121 ms
sidemenu_arrow_plus.png
122 ms
green-button.png
192 ms
buttonArrowG.png
190 ms
_tn_09c47abeb4b834e8.jpg
978 ms
buttonArrow.png
190 ms
_tn_53063c4ba0b79029.jpg
657 ms
_tn_8836c0928f7e7b92.jpg
574 ms
_tn_d5aa61a235f6cc22.png
982 ms
_tn_41397b79f5da4478.jpg
657 ms
_tn_a95892e8330c148d.jpg
818 ms
_tn_6cbbb163ae503bce.jpg
901 ms
flogo.png
741 ms
300lo.json
80 ms
fontawesome-webfont.woff
842 ms
fontawesome-webfont.woff
1514 ms
sh.8e5f85691f9aaa082472a194.html
62 ms
__utm.gif
45 ms
layers.e5ea973510bf60b3db41.js
7 ms
nl.js
419 ms
otys.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
otys.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otys.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
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otys.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 Otys.be 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.
otys.be
Open Graph description is not detected on the main page of OTYS. 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: