5.1 sec in total
1.4 sec
3.5 sec
235 ms
Welcome to fectrans.pt homepage info - get ready to check FECTRANS best content for Portugal right away, or after learning these important things about fectrans.pt
Página de informação sindical da FECTRANS
Visit fectrans.ptWe analyzed Fectrans.pt page load time and found that the first response time was 1.4 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Fectrans.pt rating and web reputation
fectrans.pt performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value16.0 s
0/100
25%
Value10.7 s
7/100
10%
Value570 ms
52/100
30%
Value0.969
2/100
15%
Value16.2 s
5/100
10%
1405 ms
223 ms
226 ms
227 ms
341 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 82% of them (67 requests) were addressed to the original Fectrans.pt, 10% (8 requests) were made to Ir0.mobify.com and 5% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fectrans.pt.
Page size can be reduced by 873.0 kB (56%)
1.6 MB
685.6 kB
In fact, the total size of Fectrans.pt main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 836.4 kB which makes up the majority of the site volume.
Potential reduce by 51.5 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.2 kB, which is 11% 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 51.5 kB or 80% of the original size.
Potential reduce by 24.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. FECTRANS images are well optimized though.
Potential reduce by 523.6 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 523.6 kB or 63% of the original size.
Potential reduce by 273.3 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. Fectrans.pt needs all CSS files to be minified and compressed as it can save up to 273.3 kB or 83% of the original size.
Number of requests can be reduced by 50 (63%)
80
30
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FECTRANS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
fectrans.pt
1405 ms
shadowbox.css
223 ms
jcemediabox.css
226 ms
style.css
227 ms
rokbox.css
341 ms
modstyle.css
241 ms
bootstrap.css
662 ms
bootstrap-responsive.css
441 ms
module_default.css
336 ms
modal.css
337 ms
template.css
358 ms
template.css
447 ms
jstyle.css
452 ms
style.css
450 ms
menu.min.css
483 ms
menu.fix.css
554 ms
index.php
586 ms
jcemediabox.js
793 ms
mootools-core.js
790 ms
core.js
599 ms
mootools-more.js
1213 ms
rokbox.js
983 ms
calnav.js
772 ms
modal.js
763 ms
jquery.min.js
985 ms
jquery-noconflict.js
893 ms
jquery-migrate.min.js
901 ms
jscript.js
901 ms
script.js
1012 ms
ext-core.js
1127 ms
menu.min.js
1014 ms
system.css
1093 ms
general.css
1095 ms
template.css
1370 ms
template.responsive.css
1127 ms
jquery.js
1429 ms
element.js
66 ms
script.js
1010 ms
script.responsive.js
1098 ms
system.css
115 ms
abertura.JPG
83 ms
header.jpg
247 ms
menu-arrow-down.png
222 ms
menu-arrow-right.png
224 ms
load-indicator.gif
222 ms
450x239-ManifActivistas5jun2012.gif
225 ms
transparent_bg.png
222 ms
450x239-intervencaoCongressoCGTO2016.jpg
358 ms
450x239-AEForcaLei.gif
366 ms
450x239-CarrisTur.gif
459 ms
450x239-AviaoTap1.jpg
367 ms
450x239-Ferrovia.jpg
412 ms
PlenarioAssembleiaRepublica_thumb.jpg
354 ms
TribunaPublica_LinhaCascais_thumb.jpg
448 ms
Abertura.jpg
450 ms
IPtrans.png
455 ms
twitter.gif
474 ms
facebook(1).gif
532 ms
blank.png
559 ms
CampaanhaETF.jpg
560 ms
conferenciainternacional.jpg
72 ms
456f6053477.png
75 ms
ws049.png
74 ms
reformados.jpg
76 ms
ssocial.jpg
74 ms
puzzle.jpg
75 ms
desumaniza%C3%A7%C3%A3o.jpg
76 ms
undefined
621 ms
grad-bg.png
503 ms
postheadericon.png
521 ms
postbullets.png
582 ms
blockheadericon.png
613 ms
blockbullets.png
615 ms
translateelement.css
145 ms
main.js
150 ms
popup.html
522 ms
tooltip.html
538 ms
16a.png
556 ms
element_main.js
39 ms
translate_24dp.png
57 ms
l
46 ms
googlelogo_color_42x16dp.png
44 ms
fectrans.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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fectrans.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fectrans.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
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fectrans.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 Fectrans.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.
fectrans.pt
Open Graph description is not detected on the main page of FECTRANS. 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: