3.7 sec in total
286 ms
3.1 sec
321 ms
Click here to check amazing STIB content for Belgium. Otherwise, check out these important facts you probably never knew about stib.be
Notre service Customer Care est à votre entière disposition
Visit stib.beWe analyzed Stib.be page load time and found that the first response time was 286 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
stib.be performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value14.8 s
0/100
25%
Value17.6 s
0/100
10%
Value3,850 ms
1/100
30%
Value0.322
36/100
15%
Value31.7 s
0/100
10%
286 ms
365 ms
169 ms
416 ms
414 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Stib.be, 85% (85 requests) were made to Stib-mivb.be and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Stib-mivb.be.
Page size can be reduced by 225.2 kB (74%)
303.2 kB
78.0 kB
In fact, the total size of Stib.be main page is 303.2 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. 45% of websites need less resources to load. Javascripts take 250.0 kB which makes up the majority of the site volume.
Potential reduce by 41.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 12.3 kB, which is 24% 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 41.4 kB or 81% of the original size.
Potential reduce by 61 B
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. STIB images are well optimized though.
Potential reduce by 183.7 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 183.7 kB or 73% of the original size.
Number of requests can be reduced by 37 (39%)
95
58
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STIB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
stib.be
286 ms
index.htm
365 ms
stib-utils.js
169 ms
style.css
416 ms
jquery-1.7.1.min.js
414 ms
modernizr-2.5.3.min.js
250 ms
SpryValidationTextField.js
334 ms
SpryValidationConfirm.js
255 ms
SpryValidationSelect.js
255 ms
SpryValidationCheckbox.js
336 ms
plugins.js
681 ms
functions.js
345 ms
lightbox8.css
461 ms
popup.js
461 ms
utilities.js
461 ms
jquery.cookie.js
417 ms
jshashtable.js
420 ms
moment.js
509 ms
fr.js
428 ms
date.js
525 ms
i18next.js
586 ms
thefrontend.js
508 ms
thefrontend_mystib.js
510 ms
homecycle.js
593 ms
bg_content.jpg
214 ms
_blank.gif
129 ms
lightbox-btn-fr.gif
128 ms
teaser_locator.jpg
130 ms
eventpass.jpg
174 ms
Survey.jpg
176 ms
nav_btn_choose_language.png
128 ms
nav_btn_more_info.png
174 ms
btn_fb.png
175 ms
btn_twit.png
174 ms
btn_li.png
176 ms
btn_gplus.png
258 ms
icon_card_mySpace.png
258 ms
logo_stib.png
260 ms
HP-MNF-2016.gif
345 ms
Tram_9.jpg
536 ms
homebox_picto_subscribe.png
256 ms
app_MOBILE.gif
343 ms
content_btn_fb.png
339 ms
content_btn_twitter.png
342 ms
content_btn_mail.png
346 ms
content_btn_print.png
424 ms
Screen_FR.png
1103 ms
download_mobile_app.jpg
534 ms
footer_btn_tw.png
427 ms
footer_btn_fb.png
432 ms
footer_btn_li.png
532 ms
footer_btn_yt.png
532 ms
footer_btn_rss.png
532 ms
nav_btn_home.png
602 ms
nav_level1_sep.png
601 ms
nav_btn_search.png
605 ms
nav_bg_mySpace_closed.png
603 ms
06986_Relance_Mobib_Header_FR.jpg
941 ms
header_bg_front_new.png
693 ms
header_bg_btn_search.png
695 ms
header_bg_btn_schedule.png
689 ms
widgets.js
76 ms
gtm.js
78 ms
brusselineligita-webfont.woff
673 ms
brusseline-webfont.woff
768 ms
brusselinelig-webfont.woff
753 ms
ns.formulaires.json
669 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
52 ms
ns.formulaires.json
724 ms
header_bg_btn_map.png
724 ms
header_bg_btn_eshop.png
795 ms
homebox_btn_plus.png
797 ms
homebox_btn_go.png
796 ms
analytics.js
31 ms
hotjar-36038.js
128 ms
homebox_arrow_down.png
778 ms
syndication
102 ms
466494168638816256
248 ms
collect
61 ms
home_bg_list.png
795 ms
list_arrow_red.png
802 ms
aside_info_arrow_down.png
803 ms
bg_footer_left.jpg
806 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
28 ms
bg_footer_right.jpg
721 ms
bg_footer_main.jpg
796 ms
list_separator.png
802 ms
list_arrow.png
802 ms
footer_bg_btn_bebrussels.png
799 ms
footer_bg_btn_uitp.png
725 ms
Relance_FR.jpg
767 ms
cycle-navbutton.png
790 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
xmtoY-JF_normal.jpeg
55 ms
cycle_navigator.png
694 ms
visit-data
219 ms
jot
25 ms
print.css
88 ms
loader.gif
90 ms
stib.be accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
stib.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
stib.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stib.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Stib.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.
stib.be
Open Graph data is detected on the main page of STIB. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: