4.5 sec in total
400 ms
3.7 sec
373 ms
Visit kayee.nl now to see the best up-to-date Kayee content and also check out these interesting facts you probably never knew about kayee.nl
Need help on your Sitecore projects? Are you searching for a Senior Sitecore Architect and 15x Sitecore MVP (2010-2024)? Contact me!
Visit kayee.nlWe analyzed Kayee.nl page load time and found that the first response time was 400 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.
kayee.nl performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value9.0 s
1/100
25%
Value11.1 s
6/100
10%
Value80 ms
99/100
30%
Value0.005
100/100
15%
Value14.0 s
10/100
10%
400 ms
1098 ms
287 ms
285 ms
476 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 78% of them (46 requests) were addressed to the original Kayee.nl, 12% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Kayee.nl.
Page size can be reduced by 1.2 MB (60%)
2.1 MB
827.9 kB
In fact, the total size of Kayee.nl main page is 2.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. 60% of websites need less resources to load. CSS take 762.1 kB which makes up the majority of the site volume.
Potential reduce by 57.7 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 57.7 kB or 80% of the original size.
Potential reduce by 9.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. Kayee images are well optimized though.
Potential reduce by 517.4 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 517.4 kB or 72% of the original size.
Potential reduce by 641.2 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. Kayee.nl needs all CSS files to be minified and compressed as it can save up to 641.2 kB or 84% of the original size.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kayee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
kayee.nl
400 ms
www.kayee.nl
1098 ms
style.min.css
287 ms
styles.css
285 ms
font-awesome-legacy.min.css
476 ms
grid-system.css
381 ms
style.css
661 ms
element-highlighted-text.css
296 ms
element-icon-list.css
378 ms
element-wpb-column-border.css
379 ms
cf7.css
392 ms
css
28 ms
responsive.css
566 ms
skin-material.css
478 ms
menu-dynamic.css
478 ms
js_composer.min.css
581 ms
salient-dynamic-styles.css
755 ms
css
38 ms
jquery.min.js
670 ms
jquery-migrate.min.js
571 ms
js
63 ms
style-non-critical.css
579 ms
jquery.fancybox.css
580 ms
core.css
583 ms
slide-out-right-material.css
661 ms
slide-out-right-hover.css
731 ms
index.js
732 ms
index.js
732 ms
jquery.easing.min.js
732 ms
jquery.mousewheel.min.js
785 ms
priority.js
785 ms
transit.min.js
785 ms
waypoints.js
785 ms
imagesLoaded.min.js
785 ms
hoverintent.min.js
786 ms
jquery.fancybox.js
878 ms
anime.min.js
877 ms
superfish.js
877 ms
init.js
1047 ms
touchswipe.min.js
876 ms
comment-reply.min.js
944 ms
js_composer_front.min.js
788 ms
kayee-logo-328x80.png
285 ms
sitecore-xmcloud-certification-developer-badge-150x150.png
285 ms
Sitecore_MVP_logo_2019.jpg
300 ms
kayee-heineken-bottles.jpeg
624 ms
js
82 ms
analytics.js
78 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
85 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
108 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
127 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
127 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
126 ms
fontawesome-webfont.svg
393 ms
icomoon.woff
204 ms
collect
32 ms
fontawesome-webfont.woff
96 ms
kayee.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
kayee.nl 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
kayee.nl 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 Kayee.nl 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 Kayee.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.
kayee.nl
Open Graph data is detected on the main page of Kayee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: