3.6 sec in total
502 ms
2.5 sec
531 ms
Click here to check amazing Nextride content for China. Otherwise, check out these important facts you probably never knew about nextride.be
Timetable for this lineOnline Timetables - TEC and STIB. Check online timetables. Current disruptions. NextRide - On iPhone, Android, Windows Phone & the web. Free.
Visit nextride.beWe analyzed Nextride.be page load time and found that the first response time was 502 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.
nextride.be performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value1.0 s
100/100
25%
Value1.1 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.0 s
100/100
10%
502 ms
387 ms
125 ms
110 ms
157 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 65% of them (42 requests) were addressed to the original Nextride.be, 8% (5 requests) were made to Maps.googleapis.com and 6% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (713 ms) belongs to the original domain Nextride.be.
Page size can be reduced by 230.8 kB (32%)
722.7 kB
491.9 kB
In fact, the total size of Nextride.be main page is 722.7 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. 60% of websites need less resources to load. Javascripts take 545.4 kB which makes up the majority of the site volume.
Potential reduce by 22.3 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 7.3 kB, which is 25% 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 22.3 kB or 78% of the original size.
Potential reduce by 586 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. Nextride images are well optimized though.
Potential reduce by 152.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 152.8 kB or 28% of the original size.
Potential reduce by 55.2 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. Nextride.be needs all CSS files to be minified and compressed as it can save up to 55.2 kB or 85% of the original size.
Number of requests can be reduced by 37 (70%)
53
16
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nextride. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
nextride.be
502 ms
nextride.be
387 ms
timetables
125 ms
jquery.min.js
110 ms
jquery-ui.min.js
157 ms
jquery.transit.min.js
156 ms
menu.css
198 ms
timetables.css
365 ms
component.css
283 ms
angular-socialshare.min.css
288 ms
modernizr.js
394 ms
angular.min.js
194 ms
angular-route.min.js
195 ms
angular-locale_en.js
599 ms
angular-easyfb.min.js
231 ms
angular-socialshare.min.js
308 ms
angularjs-viewhead.js
306 ms
js
193 ms
ngAutocomplete.js
359 ms
angular-local-storage.min.js
185 ms
angular-localize.js
370 ms
angular-timer.min.js
483 ms
angulartics.js
482 ms
angulartics-ga.js
483 ms
twitter-timeline.js
484 ms
widgets.js
221 ms
jquery.countdown.min.js
477 ms
helper.js
477 ms
app.js
713 ms
disruption.js
474 ms
description.js
509 ms
analytics.js
113 ms
fbds.js
112 ms
logoTagless.svg
104 ms
schedules.svg
106 ms
planner.svg
108 ms
disruptions.svg
104 ms
about.svg
105 ms
bg.jpg
284 ms
all.js
65 ms
resources-locale_en.js
222 ms
home.php
105 ms
widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html
38 ms
gotham-book-webfont.woff
99 ms
gotham-light-webfont.woff
207 ms
gotham-extralight-webfont.woff
187 ms
gotham-thin-webfont.woff
208 ms
gotham-medium-webfont.woff
397 ms
gotham-bold-webfont.woff
250 ms
gotham-black-webfont.woff
262 ms
gotham-ultra-webfont.woff
264 ms
34 ms
settings
154 ms
all.js
12 ms
collect
72 ms
home.css
158 ms
common.js
13 ms
util.js
29 ms
controls.js
57 ms
places_impl.js
57 ms
search-bar.php
273 ms
collect
74 ms
searchbar.css
93 ms
arrow-r-light.svg
93 ms
cross.svg
92 ms
nextride.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
nextride.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
nextride.be SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextride.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 Nextride.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.
nextride.be
Open Graph description is not detected on the main page of Nextride. 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: