3.4 sec in total
306 ms
2.9 sec
169 ms
Click here to check amazing Underside content for Belgium. Otherwise, check out these important facts you probably never knew about underside.be
Underside vous accompagne tout au long de vos projets de transformation digitale, de la phase de réflexion au développement et au déploiement de vos solutions.
Visit underside.beWe analyzed Underside.be page load time and found that the first response time was 306 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
underside.be performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value10.2 s
0/100
25%
Value12.1 s
4/100
10%
Value1,910 ms
8/100
30%
Value0.071
96/100
15%
Value17.9 s
4/100
10%
306 ms
905 ms
180 ms
184 ms
277 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Underside.be, 7% (4 requests) were made to F.vimeocdn.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain Underside.be.
Page size can be reduced by 406.3 kB (51%)
804.6 kB
398.2 kB
In fact, the total size of Underside.be main page is 804.6 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. 35% of websites need less resources to load. Javascripts take 356.6 kB which makes up the majority of the site volume.
Potential reduce by 19.4 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 3.5 kB, which is 14% 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 19.4 kB or 80% of the original size.
Potential reduce by 11.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. Underside images are well optimized though.
Potential reduce by 231.8 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 231.8 kB or 65% of the original size.
Potential reduce by 143.5 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. Underside.be needs all CSS files to be minified and compressed as it can save up to 143.5 kB or 86% of the original size.
Number of requests can be reduced by 27 (59%)
46
19
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Underside. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
underside.be
306 ms
905 ms
node.css
180 ms
defaults.css
184 ms
system.css
277 ms
system-menus.css
188 ms
user.css
188 ms
views.css
271 ms
style.css
456 ms
jquery.js
746 ms
scrolltomin.js
279 ms
cufon-yui.js
466 ms
Myriad_Pro_400.font.js
725 ms
cufon-replace.js
364 ms
facebox.css
373 ms
facebox.js
456 ms
widgets.js
5 ms
ga.js
46 ms
background_square.png
94 ms
bottom_bar.png
94 ms
banner2.jpg
205 ms
underside-logo.png
310 ms
underside.png
95 ms
index.php
103 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
43 ms
a1.gif
146 ms
menu-expanded.png
145 ms
a4.gif
145 ms
bg-cont.gif
177 ms
closelabel.gif
272 ms
loading.gif
272 ms
tl.png
270 ms
b.png
275 ms
tr.png
275 ms
bl.png
277 ms
br.png
329 ms
91076184
92 ms
__utm.gif
44 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.fr.html
12 ms
index.css
257 ms
sliderkit-site.css
258 ms
sliderkit-core.css
305 ms
jquery-1.3.min.js
572 ms
jquery.sliderkit.1.5.1.js
482 ms
jquery.easing.1.3.min.js
343 ms
jquery.mousewheel.min.js
344 ms
player.js
83 ms
player.css
69 ms
ga.js
83 ms
vuid.min.js
83 ms
proxy.html
55 ms
470600159.jpg
110 ms
__utm.gif
45 ms
jot
89 ms
img1.png
184 ms
img2.png
276 ms
img3.png
281 ms
img4.png
188 ms
underside.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
Image elements do not have [alt] attributes
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
underside.be 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
Browser errors were logged to the console
Page has valid source maps
underside.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Underside.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Underside.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.
underside.be
Open Graph description is not detected on the main page of Underside. 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: