3.5 sec in total
260 ms
3.1 sec
166 ms
Visit exki.be now to see the best up-to-date EXKi content for Belgium and also check out these interesting facts you probably never knew about exki.be
Longing for a tasty and healthy vegetarian or vegan dish, or one without gluten? Plenty of choice thanks to EXKi’s sustainable cuisine inspired by plants.
Visit exki.beWe analyzed Exki.be page load time and found that the first response time was 260 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
exki.be performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.1 s
0/100
25%
Value15.8 s
0/100
10%
Value1,720 ms
10/100
30%
Value0.054
98/100
15%
Value28.7 s
0/100
10%
260 ms
808 ms
83 ms
168 ms
164 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 91% of them (30 requests) were addressed to the original Exki.be, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Exki.be.
Page size can be reduced by 145.8 kB (64%)
229.1 kB
83.2 kB
In fact, the total size of Exki.be main page is 229.1 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. 25% of websites need less resources to load. CSS take 146.5 kB which makes up the majority of the site volume.
Potential reduce by 4.1 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 788 B, which is 15% 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 4.1 kB or 78% of the original size.
Potential reduce by 18.6 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, EXKi needs image optimization as it can save up to 18.6 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 123.1 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. Exki.be needs all CSS files to be minified and compressed as it can save up to 123.1 kB or 84% of the original size.
Number of requests can be reduced by 18 (60%)
30
12
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EXKi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for CSS and as a result speed up the page load time.
exki.be
260 ms
www.exki.be
808 ms
system.base.css
83 ms
system.menus.css
168 ms
system.messages.css
164 ms
system.theme.css
166 ms
date.css
166 ms
datepicker.1.7.css
782 ms
field.css
1783 ms
node.css
243 ms
search.css
245 ms
user.css
245 ms
views.css
246 ms
ctools.css
324 ms
genpass.css
324 ms
ipad.css
409 ms
grid.css
406 ms
facebookpopup.css
408 ms
isotope.css
408 ms
jquery.mCustomScrollbar.css
485 ms
jquery.fancybox-1.3.4.css
486 ms
ga.js
23 ms
body-bg.jpg
166 ms
logo.png
96 ms
language-BE.jpg
96 ms
language-FR.jpg
95 ms
language-IT.jpg
94 ms
language-LB.jpg
94 ms
language-NL.jpg
177 ms
language-US.jpg
176 ms
bluehigd-webfont.woff
238 ms
__utm.gif
13 ms
collect
67 ms
exki.be 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
Buttons do not have an accessible name
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
exki.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
Missing source maps for large first-party JavaScript
exki.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exki.be 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 Exki.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.
exki.be
Open Graph description is not detected on the main page of EXKi. 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: