5.7 sec in total
446 ms
5.2 sec
76 ms
Visit fcgab.pt now to see the best up-to-date FCGAB content and also check out these interesting facts you probably never knew about fcgab.pt
Site onde se apresenta de uma forma sucinta O que é a FCGAB, Qual é a sua história, qual é o seu papel no mercado e de que forma se pode tornar uma mais-valia para a indústria das construções metálica...
Visit fcgab.ptWe analyzed Fcgab.pt page load time and found that the first response time was 446 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fcgab.pt performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value2.6 s
87/100
25%
Value3.5 s
88/100
10%
Value60 ms
100/100
30%
Value0.002
100/100
15%
Value4.4 s
83/100
10%
446 ms
813 ms
858 ms
209 ms
231 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 95% of them (57 requests) were addressed to the original Fcgab.pt, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fcgab.pt.
Page size can be reduced by 520.0 kB (39%)
1.3 MB
812.9 kB
In fact, the total size of Fcgab.pt main page is 1.3 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. 30% of websites need less resources to load. Images take 613.9 kB which makes up the majority of the site volume.
Potential reduce by 26.1 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 5.7 kB, which is 18% 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 26.1 kB or 81% of the original size.
Potential reduce by 3.0 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. FCGAB images are well optimized though.
Potential reduce by 358.7 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 358.7 kB or 69% of the original size.
Potential reduce by 132.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. Fcgab.pt needs all CSS files to be minified and compressed as it can save up to 132.2 kB or 79% of the original size.
Number of requests can be reduced by 39 (72%)
54
15
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCGAB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
fcgab.pt
446 ms
ptpt
813 ms
858 ms
system.css
209 ms
calendar.css
231 ms
front.css
248 ms
rokbox.css
399 ms
grid-responsive.css
225 ms
master-962d1d890aa09ea141d0f1bfa5257987.css
594 ms
typography.css
434 ms
font-awesome.css
452 ms
1200fixed.css
449 ms
fusionmenu.css
496 ms
common.css
638 ms
module_default.css
622 ms
template.css
641 ms
slideshow.css
654 ms
mootools-core.js
991 ms
core.js
779 ms
jquery.min.js
34 ms
k2.js
819 ms
caption.js
821 ms
script.js
830 ms
mootools-more.js
1305 ms
rokbox.js
1168 ms
gantry-totop.js
1026 ms
browser-engines.js
1026 ms
load-transition.js
1025 ms
fusion.js
1273 ms
acymailing_module.js
1208 ms
mootools-mobile.js
1213 ms
rokmediaqueries.js
1212 ms
roksprocket.js
1351 ms
moofx.js
1485 ms
features.js
1397 ms
slideshow.js
1396 ms
ga.js
77 ms
logo.png
114 ms
menu-item-overlay.png
110 ms
nav-arrows.png
186 ms
pt.gif
194 ms
fr.gif
188 ms
en.gif
192 ms
slideshow-overlay-top.png
298 ms
slideshow-overlay-left.png
299 ms
slideshow-overlay-right.png
369 ms
1.jpg
741 ms
slideshow-overlay.png
384 ms
slideshow-overlay2.png
383 ms
features-content.png
480 ms
4.jpg
767 ms
2.jpg
945 ms
3.jpg
932 ms
slideshow-overlay-btm.png
577 ms
title-hex.png
665 ms
social-icons.png
764 ms
edmondsans-regular-webfont.woff
955 ms
edmondsans-medium-webfont.woff
1014 ms
fontawesome-webfont.woff
1130 ms
__utm.gif
13 ms
fcgab.pt 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
fcgab.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
General
Impact
Issue
Detected JavaScript libraries
fcgab.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcgab.pt 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 Fcgab.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.
fcgab.pt
Open Graph description is not detected on the main page of FCGAB. 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: