3.6 sec in total
282 ms
3.1 sec
174 ms
Welcome to itinerarium.pt homepage info - get ready to check Itinerarium best content right away, or after learning these important things about itinerarium.pt
Visit itinerarium.ptWe analyzed Itinerarium.pt page load time and found that the first response time was 282 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
itinerarium.pt performance score
name
value
score
weighting
Value12.3 s
0/100
10%
Value14.8 s
0/100
25%
Value14.6 s
1/100
10%
Value580 ms
51/100
30%
Value0.006
100/100
15%
Value15.9 s
6/100
10%
282 ms
535 ms
570 ms
232 ms
799 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Itinerarium.pt, 63% (65 requests) were made to Stcp.pt and 22% (23 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Stcp.pt.
Page size can be reduced by 1.1 MB (57%)
1.9 MB
806.6 kB
In fact, the total size of Itinerarium.pt main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 33.6 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 33.6 kB or 85% of the original size.
Potential reduce by 16.9 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. Itinerarium images are well optimized though.
Potential reduce by 888.3 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 888.3 kB or 73% of the original size.
Potential reduce by 134.9 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. Itinerarium.pt needs all CSS files to be minified and compressed as it can save up to 134.9 kB or 85% of the original size.
Number of requests can be reduced by 64 (66%)
97
33
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itinerarium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
itinerarium.pt
282 ms
535 ms
style.css
570 ms
formbuilder3.css
232 ms
jquery1.7.2.js
799 ms
jquery.ui.min.js
1029 ms
datepicker-pt.js
233 ms
jquery.combobox.js
347 ms
formbuilder3.js
346 ms
jquery.ad-gallery.css
349 ms
jquery.easing.js
573 ms
mousewheel.js
461 ms
jquery.ad-gallery.js
690 ms
jquery.ad-gallery.preset.js
575 ms
fancybox.css
680 ms
fancybox.js
951 ms
jquery.blockui.js
919 ms
placeholder.js
794 ms
jquery.backgroundpos.min.js
803 ms
jquery-inputdefvalue.js
908 ms
jquery.carouFredSel-5.5.0-packed.js
913 ms
jquery.form.js
1034 ms
sidebar.js
1022 ms
jquery.tipsy.js
1027 ms
tipsy.css
1034 ms
jquery.datetimepicker.js
1290 ms
jquery.zclip.min.js
1135 ms
favorites.js
1136 ms
geral.js
1251 ms
formularios.css
1143 ms
linhas.css
1144 ms
geral_stcp.css
1586 ms
geral_stcp_pt.css
1246 ms
cycle.js
1367 ms
jquery.table.js
1257 ms
sig.adapter.js
1358 ms
js
43 ms
style.css
1268 ms
library.js
1153 ms
itinerarium.js
1179 ms
estilos.php
1284 ms
geral.js
1281 ms
jquery.tablesorter.min.js
1151 ms
common.js
92 ms
util.js
94 ms
geocoder.js
92 ms
map.js
40 ms
itinerarium_head.jpg
123 ms
logoStcp.jpg
124 ms
logoMetro.jpg
126 ms
logoCP.jpg
125 ms
circle-blue.png
125 ms
inverter-seleccao.png
126 ms
bullet-yellow.png
257 ms
icon-printer.png
258 ms
seta-white-btns.png
257 ms
Pictograma_Autocarro.png
259 ms
Pictograma_Electrico.png
259 ms
Pictograma_Metro.png
259 ms
Pictograma_Funicular.png
344 ms
Pictograma_Comboio.png
346 ms
iti-help-01.jpg
348 ms
seta-link-square-left.png
347 ms
logo-bottom.png
349 ms
apcer.png
348 ms
logo-sig2000.png
455 ms
logo-seara.png
456 ms
ui-bg_flat_75_ffffff_40x100.png
456 ms
circle-orange.png
458 ms
StaticMapService.GetMapImage
210 ms
onion.js
21 ms
openhand_8_8.cur
31 ms
infowindow.js
24 ms
ViewportInfoService.GetViewportInfo
71 ms
stats.js
21 ms
controls.js
26 ms
transparent.png
24 ms
css
59 ms
google4.png
49 ms
marker.js
38 ms
mapcnt6.png
45 ms
sv5.png
49 ms
tmapctrl.png
24 ms
cb_scout5.png
25 ms
tmapctrl4.png
24 ms
imgs8.png
32 ms
vt
26 ms
vt
21 ms
vt
60 ms
vt
22 ms
vt
46 ms
vt
80 ms
vt
34 ms
vt
55 ms
vt
56 ms
vt
72 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
13 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
22 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
21 ms
AuthenticationService.Authenticate
14 ms
geral_stcp_print.css
115 ms
print.css
116 ms
itinerarium.pt 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
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
Links do not have a discernible name
itinerarium.pt 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
Browser errors were logged to the console
itinerarium.pt 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itinerarium.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Itinerarium.pt 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.
itinerarium.pt
Open Graph description is not detected on the main page of Itinerarium. 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: