4.6 sec in total
308 ms
3.4 sec
911 ms
Visit cm-fafe.pt now to see the best up-to-date Cm Fafe content for Portugal and also check out these interesting facts you probably never knew about cm-fafe.pt
Câmara Municipal Fafe
Visit cm-fafe.ptWe analyzed Cm-fafe.pt page load time and found that the first response time was 308 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cm-fafe.pt performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value13.5 s
0/100
25%
Value9.9 s
10/100
10%
Value360 ms
72/100
30%
Value0.138
79/100
15%
Value10.4 s
24/100
10%
308 ms
600 ms
28 ms
89 ms
168 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 68% of them (71 requests) were addressed to the original Cm-fafe.pt, 7% (7 requests) were made to Ajax.googleapis.com and 6% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cm-fafe.pt.
Page size can be reduced by 1.2 MB (22%)
5.3 MB
4.1 MB
In fact, the total size of Cm-fafe.pt main page is 5.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 170.3 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 170.3 kB or 79% of the original size.
Potential reduce by 178.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. Cm Fafe images are well optimized though.
Potential reduce by 725.1 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 725.1 kB or 68% of the original size.
Potential reduce by 109.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. Cm-fafe.pt needs all CSS files to be minified and compressed as it can save up to 109.2 kB or 82% of the original size.
Number of requests can be reduced by 50 (51%)
98
48
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cm Fafe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
cm-fafe.pt
308 ms
www.cm-fafe.pt
600 ms
jquery-ui.css
28 ms
minimalist.css
89 ms
jquery.fancybox.css
168 ms
estilo.css
167 ms
cookieBar.css
168 ms
eventCalendar.css
169 ms
eventCalendar_theme_responsive.css
170 ms
jquery.min.js
28 ms
jquery-ui.min.js
39 ms
api.js
61 ms
jquery.easing.1.3.js
227 ms
jquery.fancybox.pack_pt.js
315 ms
flowplayer.min.js
288 ms
date-pt.js
321 ms
jquery.eventCalendar.min.js
287 ms
smoothscroll.js
330 ms
jquery.cycle.min.js
284 ms
jquery.cycle2.min.js
377 ms
jquery.lazy.js
377 ms
jquery.cookieBar.js
374 ms
addthis_widget.js
82 ms
jqueryscripts.js
377 ms
reset.css
370 ms
style.css
371 ms
style-minifield.css
497 ms
buttons.css
494 ms
custom.css
494 ms
css
61 ms
font-awesome.css
494 ms
jquery.anythingslider.js
500 ms
jquery.custom.js
501 ms
cse.js
16 ms
recaptcha__en.js
63 ms
cse.js
215 ms
sdk.js
71 ms
analytics.js
69 ms
collect
77 ms
jsapi
399 ms
page_1_thumb_large.jpg
383 ms
wcag2AA-blue.png
383 ms
logo.png
416 ms
facebook.png
417 ms
youtube.png
414 ms
rss.png
415 ms
google.png
416 ms
zoommais.png
412 ms
zoommenos.png
490 ms
shadow-938.png
489 ms
04.jpg
1260 ms
0004.jpg
1105 ms
0005.png
1017 ms
0007.png
1183 ms
0006.png
1276 ms
widget-area.png
621 ms
0wn5MW5APpL3k8w6GfnXJajngkMlgKYwRZ0mTjObPoU
821 ms
0wn5MW5APpL3k8w6GfnXJajngkMlgKYwRZ0mTjObPoU
996 ms
0wn5MW5APpL3k8w6GfnXJajngkMlgKYwRZ0mTjObPoU
1197 ms
0wn5MW5APpL3k8w6GfnXJajngkMlgKYwRZ0mTjObPoU
1153 ms
0wn5MW5APpL3k8w6GfnXJajngkMlgKYwRZ0mTjObPoU
1213 ms
14.png
1223 ms
15.png
1262 ms
16.png
1270 ms
7.png
1295 ms
2.png
1306 ms
1.png
1329 ms
4.png
1349 ms
5.png
1346 ms
17.png
1358 ms
3.png
1381 ms
8.png
1387 ms
101.jpg
1488 ms
115.jpg
1508 ms
c20ad4d76fe97759aa27a0c99bff6710.png
1433 ms
apoio_inst.jpg
1437 ms
pt.png
1463 ms
page_1_thumb_large.jpg
359 ms
page_1_thumb_large.jpg
391 ms
html5-css.png
1469 ms
435 ms
ui-bg_glass_75_e6e6e6_1x400.png
161 ms
300lo.json
113 ms
ui-bg_flat_75_ffffff_40x100.png
39 ms
ui-icons_888888_256x240.png
40 ms
ui-icons_222222_256x240.png
41 ms
xd_arbiter.php
48 ms
xd_arbiter.php
89 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
81 ms
sntaY1Q8xeij0j8FAJb2VvesZW2xOQ-xsNqO47m55DA.ttf
90 ms
sh.8e5f85691f9aaa082472a194.html
58 ms
default+pt_PT.css
72 ms
minimalist.css
86 ms
default+pt_PT.I.js
85 ms
fontawesome-webfont.woff
1129 ms
input_pattern.png
1140 ms
ajax-loader.gif
1159 ms
default.png
1167 ms
minimalist.css
65 ms
layers.e5ea973510bf60b3db41.js
63 ms
pt.js
13 ms
max-width-1024.css
88 ms
max-width-768.css
86 ms
max-width-480.css
90 ms
max-width-320.css
87 ms
cm-fafe.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
Image elements do not have [alt] attributes
Links do not have a discernible name
cm-fafe.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
Issues were logged in the Issues panel in Chrome Devtools
cm-fafe.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 Cm-fafe.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 Cm-fafe.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.
cm-fafe.pt
Open Graph description is not detected on the main page of Cm Fafe. 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: