4.5 sec in total
392 ms
3.6 sec
423 ms
Visit gillio.be now to see the best up-to-date Gillio content for United States and also check out these interesting facts you probably never knew about gillio.be
Visit gillio.beWe analyzed Gillio.be page load time and found that the first response time was 392 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.
gillio.be performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value10.6 s
0/100
25%
Value7.0 s
32/100
10%
Value790 ms
37/100
30%
Value0.367
29/100
15%
Value10.2 s
25/100
10%
392 ms
590 ms
432 ms
343 ms
172 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 75% of them (56 requests) were addressed to the original Gillio.be, 9% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Gillio.be.
Page size can be reduced by 629.6 kB (37%)
1.7 MB
1.1 MB
In fact, the total size of Gillio.be main page is 1.7 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. 65% of websites need less resources to load. Images take 982.2 kB which makes up the majority of the site volume.
Potential reduce by 32.9 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 6.4 kB, 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 32.9 kB or 78% of the original size.
Potential reduce by 55.8 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. Gillio images are well optimized though.
Potential reduce by 125.2 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 125.2 kB or 62% of the original size.
Potential reduce by 415.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. Gillio.be needs all CSS files to be minified and compressed as it can save up to 415.8 kB or 89% of the original size.
Number of requests can be reduced by 10 (16%)
63
53
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gillio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
gillio.be
392 ms
www.gillio.be
590 ms
style.css
432 ms
jquery-1.10.2.min.js
343 ms
modernizr.2.6.2.min.js
172 ms
mobile-detect.min.js
269 ms
mobile-detect-modernizr.min.js
192 ms
functions.min.js
197 ms
index.min.js
336 ms
pagehead.min.js
357 ms
classie.min.js
363 ms
css
35 ms
analytics.js
22 ms
bg.png
836 ms
loader.gif
251 ms
logo.png
252 ms
23347_910x529c.jpg
837 ms
20524_360x165c.jpg
298 ms
22959_360x165c.jpg
254 ms
20527_360x165c.jpg
499 ms
18872_161x96.png
348 ms
18873_161x96.png
385 ms
18874_161x96.png
571 ms
20188_350x193c.jpg
834 ms
20191_350x193c.jpg
833 ms
20190_350x193c.jpg
835 ms
18879_350x193c.jpg
845 ms
20192_350x193c.jpg
995 ms
20189_350x193c.jpg
1026 ms
20193_350x193c.jpg
925 ms
20194_350x193c.jpg
1127 ms
20195_350x193c.jpg
1063 ms
20196_350x193c.jpg
1114 ms
20224_350x193c.jpg
1177 ms
20197_350x193c.jpg
1351 ms
22960_350x193c.png
1389 ms
20198_450x200c.jpg
1422 ms
20199_450x200c.jpg
1361 ms
20200_450x200c.jpg
1483 ms
21548_250x250c.jpg
1450 ms
21527_250x250c.jpg
1617 ms
23286_250x250c.png
2125 ms
baseline.png
1555 ms
19776_270x137.png
1957 ms
18864_50x50.png
1633 ms
19337_50x50.png
1663 ms
21581_50x50.png
1733 ms
23211_50x50.png
1797 ms
20462_51x32.png
1811 ms
sdk.js
16 ms
widget_v2.134.js
94 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
134 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
133 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
134 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
134 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
134 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
135 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
133 ms
collect
89 ms
18862_51x32.png
1582 ms
collect
83 ms
18860_51x32.png
1652 ms
112 ms
18852_51x32.png
1670 ms
xd_arbiter.php
29 ms
xd_arbiter.php
35 ms
18859_51x32.png
1680 ms
ga-audiences
41 ms
18861_51x32.png
1665 ms
icon-cart-top.png
1686 ms
arrow-close-head.png
1628 ms
icon-check-xlarge.png
1585 ms
avatar_simple_visitor.png
59 ms
icon-error-large.png
1342 ms
aL63HcygAAVYuCCsAAA==
1 ms
gillio.be 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
Links do not have a discernible name
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.
gillio.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
gillio.be 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gillio.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 Gillio.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.
gillio.be
Open Graph description is not detected on the main page of Gillio. 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: