5.4 sec in total
398 ms
4.2 sec
841 ms
Welcome to roundtable.be homepage info - get ready to check Round Table best content for Belgium right away, or after learning these important things about roundtable.be
Visit roundtable.beWe analyzed Roundtable.be page load time and found that the first response time was 398 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
roundtable.be performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.8 s
15/100
25%
Value7.3 s
28/100
10%
Value600 ms
49/100
30%
Value0.178
68/100
15%
Value7.3 s
50/100
10%
398 ms
277 ms
184 ms
7 ms
540 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 59% of them (46 requests) were addressed to the original Roundtable.be, 21% (16 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Admin.roundtable.be.
Page size can be reduced by 780.8 kB (25%)
3.1 MB
2.3 MB
In fact, the total size of Roundtable.be main page is 3.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. 50% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 29.0 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 13.9 kB, which is 41% 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 29.0 kB or 85% of the original size.
Potential reduce by 156.5 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. Round Table images are well optimized though.
Potential reduce by 458.9 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 458.9 kB or 70% of the original size.
Potential reduce by 136.4 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. Roundtable.be needs all CSS files to be minified and compressed as it can save up to 136.4 kB or 85% of the original size.
Number of requests can be reduced by 24 (39%)
61
37
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Round Table. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
roundtable.be
398 ms
bootstrap.min.css
277 ms
imgareaselect-animated.css
184 ms
jquery-ui.css
7 ms
default.css
540 ms
jquery.min.js
471 ms
jquery.mobile.custom.js
288 ms
modernizr.custom.js
342 ms
moment.min.js
446 ms
underscore.js
655 ms
jquery.cookie.js
487 ms
clndr.js
634 ms
bootstrap.min.js
738 ms
jquery.flipCounter.1.2.pack.js
660 ms
tinymce.min.js
1247 ms
default.js
713 ms
jquery.imgareaselect.min.js
821 ms
appadmin.js
846 ms
css
25 ms
css
38 ms
css
47 ms
image
2248 ms
logo_header.png
162 ms
header-bg.png
288 ms
lets-rock-s.png
199 ms
header-letsrock.png
287 ms
taalkeuze_pijl.png
282 ms
admin.png
283 ms
sleutel_login.png
334 ms
home-banner.jpg
1011 ms
aims-01.png
370 ms
aims-02.png
385 ms
aims-03.png
444 ms
aims-04.png
443 ms
home-quote-bg.jpg
688 ms
home-quote-ico.png
549 ms
carousel-image-holder.png
558 ms
sprite01.png
627 ms
RT_cares.png
728 ms
euro.png
738 ms
heart.png
751 ms
facebook.png
804 ms
linker_arm.png
868 ms
rechter_arm.png
907 ms
zones-item-bg.png
928 ms
app_store.png
1009 ms
google_play.png
1109 ms
image
1808 ms
image
2510 ms
image
1837 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
32 ms
toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff
29 ms
toadOcfmlt9b38dHJxOBGMa9awK0IKUjIWABZIchFI8.woff
113 ms
toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff
114 ms
toadOcfmlt9b38dHJxOBGFkQc6VGVFSmCnC_l7QZG60.woff
111 ms
_weQNDK6Uf40CiGFKBBUjobN6UDyHWBl620a-IRfuBk.woff
108 ms
PatuaOne-Regular.ttf
967 ms
Aller.ttf
1290 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
106 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
106 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
106 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
90 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
90 ms
footer-image.png
1041 ms
analytics.js
50 ms
grunge_counter.png
935 ms
689 ms
collect
11 ms
css
37 ms
magic.css
100 ms
jquery-1.8.2.min.js
3 ms
js
90 ms
magic.js
198 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
8 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
9 ms
boeCNmOCCh-EWFLSfVffDg.woff
8 ms
wkfQbvfT_02e2IWO3yYueQ.woff
10 ms
BVtM30trf7q_jfqYeHfjtA.woff
8 ms
roundtable.be accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
roundtable.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
Missing source maps for large first-party JavaScript
roundtable.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roundtable.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Roundtable.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.
roundtable.be
Open Graph description is not detected on the main page of Round Table. 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: