6.1 sec in total
2.3 sec
3.7 sec
152 ms
Welcome to keij.net homepage info - get ready to check Keij best content right away, or after learning these important things about keij.net
Persoonlijke website Sjors Keij
Visit keij.netWe analyzed Keij.net page load time and found that the first response time was 2.3 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
keij.net performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value5.3 s
22/100
25%
Value3.6 s
87/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
87/100
10%
2281 ms
226 ms
227 ms
243 ms
209 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 45% of them (42 requests) were addressed to the original Keij.net, 29% (27 requests) were made to Maps.google.com and 11% (10 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Keij.net.
Page size can be reduced by 614.5 kB (47%)
1.3 MB
679.5 kB
In fact, the total size of Keij.net 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. 55% of websites need less resources to load. Javascripts take 629.3 kB which makes up the majority of the site volume.
Potential reduce by 47.6 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 10.0 kB, which is 17% 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 47.6 kB or 83% of the original size.
Potential reduce by 133.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, Keij needs image optimization as it can save up to 133.4 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 415.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 415.7 kB or 66% of the original size.
Potential reduce by 17.8 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. Keij.net needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 78% of the original size.
Number of requests can be reduced by 37 (43%)
87
50
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Keij. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
keij.net
2281 ms
reset.css
226 ms
typo.css
227 ms
layout.css
243 ms
ui.totop.css
209 ms
colorbox.css
207 ms
mosaic.css
779 ms
jpreloader.css
307 ms
tip-twitter.css
306 ms
validationEngine.jquery.css
336 ms
css
23 ms
ie8-bg.png
336 ms
Facebook.png
395 ms
Google.png
399 ms
Linkedin.png
394 ms
Twitter.png
431 ms
website.jpg
985 ms
jquery.min.js
25 ms
jpreLoader.min.js
440 ms
jquery.color.js
525 ms
jquery.easing.1.3.js
438 ms
jquery.poshytip.min.js
445 ms
jquery.ui.totop.min.js
528 ms
jquery.colorbox-min.js
630 ms
mosaic.1.0.1.min.js
539 ms
jquery.validationEngine.js
737 ms
jquery.validationEngine-en.js
623 ms
js
22 ms
config.js
636 ms
custom.js
735 ms
sjors_port.jpg
1050 ms
sjors_port1.jpg
1008 ms
sjors_port2.jpg
1070 ms
brick.png
154 ms
root-bg-bottom.jpg
229 ms
root-bg2.jpg
318 ms
menu-bg3.jpg
279 ms
menu-icons.jpg
501 ms
hover-magnify.png
384 ms
contact-icons.gif
390 ms
common.js
33 ms
util.js
33 ms
geocoder.js
33 ms
map.js
30 ms
loading.gif
374 ms
controls.png
370 ms
skillbar-score-bg.jpg
407 ms
tip-twitter_arrows.gif
418 ms
ui.totop.png
606 ms
gTHiwyxi6S7iiHpqAoiE3JS3E-kSBmtLoNJPDtbj2Pk.ttf
11 ms
StaticMapService.GetMapImage
65 ms
AuthenticationService.Authenticate
174 ms
GeocodeService.Search
93 ms
onion.js
12 ms
openhand_8_8.cur
18 ms
ViewportInfoService.GetViewportInfo
67 ms
stats.js
10 ms
controls.js
8 ms
transparent.png
14 ms
css
37 ms
google4.png
26 ms
marker.js
18 ms
mapcnt6.png
22 ms
sv5.png
22 ms
tmapctrl.png
15 ms
cb_scout5.png
24 ms
tmapctrl4.png
23 ms
imgs8.png
24 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
9 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
11 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
10 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
10 ms
vt
14 ms
vt
13 ms
vt
18 ms
vt
14 ms
vt
13 ms
vt
19 ms
vt
10 ms
StaticMapService.GetMapImage
154 ms
vt
54 ms
ViewportInfoService.GetViewportInfo
44 ms
spotlight-poi.png
16 ms
vt
46 ms
vt
56 ms
vt
47 ms
vt
59 ms
vt
31 ms
vt
52 ms
vt
68 ms
vt
71 ms
vt
84 ms
vt
91 ms
keij.net 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
Form elements do not have associated labels
keij.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
keij.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keij.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Keij.net 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.
keij.net
Open Graph description is not detected on the main page of Keij. 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: