5.5 sec in total
581 ms
4.7 sec
220 ms
Welcome to fcm.pt homepage info - get ready to check FCM best content right away, or after learning these important things about fcm.pt
A FCM dispõe de experiência e know-how comprovados permitindo desenvolver projetos em todas as áreas da construção. Apoiando o seu desempenho nos valores estabelecidos interna
Visit fcm.ptWe analyzed Fcm.pt page load time and found that the first response time was 581 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fcm.pt performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value13.3 s
0/100
25%
Value21.8 s
0/100
10%
Value2,150 ms
6/100
30%
Value0.343
32/100
15%
Value26.5 s
0/100
10%
581 ms
1828 ms
491 ms
610 ms
255 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Fcm.pt, 85% (22 requests) were made to Grupofcm.com and 12% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Grupofcm.com.
Page size can be reduced by 341.7 kB (23%)
1.5 MB
1.1 MB
In fact, the total size of Fcm.pt main page is 1.5 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. 20% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 7.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. 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 7.1 kB or 72% of the original size.
Potential reduce by 45.3 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. FCM images are well optimized though.
Potential reduce by 257.4 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 257.4 kB or 71% of the original size.
Potential reduce by 31.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. Fcm.pt needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 83% of the original size.
Number of requests can be reduced by 14 (58%)
24
10
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
fcm.pt
581 ms
www.grupofcm.com
1828 ms
jquery-1.4.4.min.js
491 ms
jquery-ui-1.8.8.custom.min.js
610 ms
jquery.jcarousel.min.js
255 ms
jquery.jscrollpane.min.js
250 ms
jquery.mousewheel.js
251 ms
liteaccordion.jquery.js
256 ms
main.js
496 ms
homepage.css
495 ms
ga.js
28 ms
fc03d2b18d442425b02eaa8e11dc6d40.jpg
1672 ms
3e2b2582b8c7daa54757d25df86938c8.png
279 ms
menuItem_black.png
259 ms
arrowSearch.png
257 ms
contentMainContainerBackground.png
262 ms
greenArrow.png
268 ms
efd3a61ef9092ae063d7c75c5c4521cf.jpg
1157 ms
2fc39ee7ec303ba695ba66ae71faec9c.jpg
983 ms
95e06a29ad2dd90b246f9850b3fb8f77.jpg
1281 ms
mapa_mundi_home.png
537 ms
ff916711825c21520b07af7f17699877.jpg
673 ms
showImages.png
777 ms
blackbarV2.png
915 ms
__utm.gif
12 ms
__utm.gif
3 ms
fcm.pt 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
fcm.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fcm.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcm.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fcm.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.
fcm.pt
Open Graph description is not detected on the main page of FCM. 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: