4.4 sec in total
945 ms
3.2 sec
228 ms
Visit traveline.info now to see the best up-to-date Traveline content for United Kingdom and also check out these interesting facts you probably never knew about traveline.info
The gateway to Britain's public transport network.
Visit traveline.infoWe analyzed Traveline.info page load time and found that the first response time was 945 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.
traveline.info performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value8.0 s
3/100
25%
Value7.8 s
24/100
10%
Value1,070 ms
25/100
30%
Value0.443
21/100
15%
Value10.9 s
21/100
10%
945 ms
7 ms
154 ms
242 ms
47 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 29% of them (15 requests) were addressed to the original Traveline.info, 10% (5 requests) were made to Tnjplib.mxdata.co.uk and 10% (5 requests) were made to Image2.pubmatic.com. The less responsive or slowest element that took the longest time to load (968 ms) relates to the external source Image2.pubmatic.com.
Page size can be reduced by 645.5 kB (52%)
1.2 MB
586.7 kB
In fact, the total size of Traveline.info main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 779.8 kB which makes up the majority of the site volume.
Potential reduce by 22.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.2 kB or 76% of the original size.
Potential reduce by 1.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. Traveline images are well optimized though.
Potential reduce by 529.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 529.2 kB or 68% of the original size.
Potential reduce by 92.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. Traveline.info needs all CSS files to be minified and compressed as it can save up to 92.5 kB or 83% 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 Traveline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.traveline.info
945 ms
gpt.js
7 ms
styles.css
154 ms
global.css
242 ms
leaflet.css
47 ms
headScripts.js
245 ms
pubads_impl_81.js
16 ms
container.html
15 ms
jquery.min.js
49 ms
jquery.form.min.js
223 ms
scripts.js
242 ms
main.js
441 ms
traveline.min.js
762 ms
leaflet.js
12 ms
Oxfordshire.jpg
845 ms
traveline-logo.svg
83 ms
sprite.svg
85 ms
titilliumweb-regular-webfont.woff
162 ms
titilliumweb-light-webfont.woff
259 ms
titilliumweb-semibold-webfont.woff
202 ms
titilliumweb-bold-webfont.woff
206 ms
sprite.png
98 ms
analytics.js
95 ms
transport.css
187 ms
std.css
261 ms
ads
78 ms
collect
21 ms
collect
21 ms
collect
21 ms
collect
62 ms
showad.js
33 ms
osd.js
13 ms
showad.js
29 ms
AdServerServlet
131 ms
PugMaster
31 ms
p-P7x87XHnVfbWr.gif
12 ms
pixel
40 ms
sync
32 ms
demconf.jpg
28 ms
Pug
33 ms
Pug
52 ms
data
16 ms
Pug
37 ms
mxTransport.svg
407 ms
Pug
23 ms
Pug
968 ms
13278.js
7 ms
sync
19 ms
377046-2.js
9 ms
2.jpg
25 ms
mxTransport.woff
84 ms
traveline.info 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
traveline.info 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
traveline.info 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traveline.info 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 Traveline.info 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.
traveline.info
Open Graph description is not detected on the main page of Traveline. 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: