1.7 sec in total
90 ms
1.4 sec
270 ms
Click here to check amazing JoTM Be Tmb content for Spain. Otherwise, check out these important facts you probably never knew about jotmbe.tmb.cat
Amb JoTMBé tindràs sempre a mà tota la informació personalitzada per desplaçar-te en transport públic. Guanya premis i recompenses amb el Programa de Punts.
Visit jotmbe.tmb.catWe analyzed Jotmbe.tmb.cat page load time and found that the first response time was 90 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
jotmbe.tmb.cat performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value15.4 s
0/100
25%
Value13.5 s
2/100
10%
Value1,570 ms
13/100
30%
Value0
100/100
15%
Value19.9 s
2/100
10%
90 ms
430 ms
140 ms
62 ms
54 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jotmbe.tmb.cat, 63% (50 requests) were made to Static-web.tmb.cat and 21% (17 requests) were made to Tmb.cat. The less responsive or slowest element that took the longest time to load (506 ms) relates to the external source Tmb.cat.
Page size can be reduced by 315.6 kB (18%)
1.7 MB
1.4 MB
In fact, the total size of Jotmbe.tmb.cat main page is 1.7 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. 45% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 302.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 47.9 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 302.0 kB or 86% of the original size.
Potential reduce by 2.1 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. JoTM Be Tmb images are well optimized though.
Potential reduce by 11.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. This website has mostly compressed JavaScripts.
Potential reduce by 274 B
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. Jotmbe.tmb.cat needs all CSS files to be minified and compressed as it can save up to 274 B or 14% of the original size.
Number of requests can be reduced by 48 (62%)
78
30
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JoTM Be Tmb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
jotmbe.tmb.cat
90 ms
jotmbe
430 ms
gtm.js
140 ms
uc.js
62 ms
main.c4f5d468.css
54 ms
my_chatbot_Karma.css
60 ms
main.1836593a.js
78 ms
chatbot-controller_karma.js
66 ms
chatbot-action.js
68 ms
main.css
47 ms
all.js
363 ms
keycloak.js
476 ms
userAPI.js
346 ms
app.js
326 ms
clay.css
53 ms
combo
198 ms
loader.js
266 ms
combo
506 ms
main.css
8 ms
main.css
233 ms
main.js
319 ms
platform.js
28 ms
keycloak.js
163 ms
analytics.js
89 ms
fbevents.js
84 ms
client-help.svg
85 ms
700c8521-c0e1-4f77-a0c7-42eaa18e6300
168 ms
2246ba12-ffbe-42f2-9027-8ccb6e86c669
168 ms
658e4e3c-97fb-4f52-afcd-b32436113814
222 ms
cf8b8ae0-ec6b-48d7-bd0f-61ad605323c7
168 ms
6734d8f7-b593-48bd-ac86-6b928c53002d
220 ms
81384043-6f22-404f-a447-d5287a7a4691
222 ms
33701632-242c-43cc-aec1-93abb3db3d91
224 ms
2ebccdc1-e2cf-40f2-8d80-c743da32916e
225 ms
311d7edc-7b2a-410f-a64c-e4223ad14f2d
290 ms
9a16caf3-bc33-49a9-9321-d26700f64f28
289 ms
bad3666b-4ed7-4eb4-8c39-ae4103cc3289
292 ms
84b39554-e4cc-4f70-a8ae-9ef842eacafb
293 ms
arrow_idioma_down.svg
40 ms
jotmbe-account.svg
37 ms
ico-language-alt.svg
39 ms
logo_TMB_new.png
38 ms
menu.svg
84 ms
16px_Usuari_blanc.svg
77 ms
close-black.svg
85 ms
search.svg
77 ms
jotmbe-account-2.svg
76 ms
share.svg
78 ms
twitter.png
80 ms
linia.jpg
77 ms
facebook.png
79 ms
linkedin.png
80 ms
correu.png
80 ms
whatsapp.png
82 ms
icon-espai-personal-ayuda.svg
99 ms
facebook_footer_white.svg
82 ms
x_footer_white.svg
89 ms
instagram_footer_white.svg
86 ms
youtube_footer_white.svg
85 ms
spotify_footer_white.svg
95 ms
linkedin_footer_white.svg
84 ms
logotip_TMB_blanc.svg
86 ms
up.png
92 ms
48px_Favorit_vermell.svg
88 ms
mobile.svg
92 ms
alertes.svg
89 ms
trajectes.svg
90 ms
cultura.svg
132 ms
48px_Usuari_vermell.svg
92 ms
48px_Lloc_vermell.svg
128 ms
48px_Trajecte_vermell.svg
93 ms
more_menu.svg
123 ms
close_black.svg
89 ms
search.svg
91 ms
plus-light-white.svg
61 ms
nav_prev.svg
95 ms
nav_next.svg
55 ms
nav_white_prev.png
16 ms
nav_white_next.png
4 ms
pause.png
7 ms
jotmbe.tmb.cat 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
jotmbe.tmb.cat 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
jotmbe.tmb.cat SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jotmbe.tmb.cat can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Jotmbe.tmb.cat 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.
jotmbe.tmb.cat
Open Graph data is detected on the main page of JoTM Be Tmb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: