5 sec in total
480 ms
4.3 sec
226 ms
Click here to check amazing FUMEC content for India. Otherwise, check out these important facts you probably never knew about fumec.br
A FUMEC é toda você, no presencial ou no digital. Aqui você escolhe como quer estudar!
Visit fumec.brWe analyzed Fumec.br page load time and found that the first response time was 480 ms and then it took 4.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.
fumec.br performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value10.8 s
0/100
25%
Value10.1 s
9/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value13.7 s
10/100
10%
480 ms
606 ms
278 ms
279 ms
284 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 70% of them (48 requests) were addressed to the original Fumec.br, 4% (3 requests) were made to Google-analytics.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fumec.br.
Page size can be reduced by 552.2 kB (26%)
2.2 MB
1.6 MB
In fact, the total size of Fumec.br main page is 2.2 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 60.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 60.1 kB or 74% of the original size.
Potential reduce by 127.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. FUMEC images are well optimized though.
Potential reduce by 331.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 331.4 kB or 68% of the original size.
Potential reduce by 33.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. Fumec.br needs all CSS files to be minified and compressed as it can save up to 33.2 kB or 77% of the original size.
Number of requests can be reduced by 51 (77%)
66
15
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUMEC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fumec.br
480 ms
www.fumec.br
606 ms
A.screen.css.pagespeed.cf.rrLDK4-oE4.css
278 ms
A.fumec.css+fumec-home.css,Mcc.D3RX70wqQt.css.pagespeed.cf.eGyaPIyGtt.css
279 ms
A.updates,,_concrete5.6.3.3,,_concrete,,_css,,_ccm.base.css+packages,,_email_list_signup,,_blocks,,_email_list_signup,,_view.css+updates,,_concrete5.6.3.3,,_concrete,,_blocks,,_page_list,,_view.css,Mcc.RaEacgmGo8.css.pagespeed.cf.Bpo78_LHFh.css
284 ms
jquery.js.pagespeed.jm.TiC1blcYSb.js
565 ms
updates,_concrete5.6.3.3,_concrete,_js,_ccm.base.js+packages,_email_list_signup,_blocks,_email_list_signup,_view.js+themes,_fumec_theme,_js,_amalgamation.js.pagespeed.jc.T9ndD25jsf.js
285 ms
a2y.js
114 ms
banner-home-script.js+jquery.easing.js.pagespeed.jc.oPmFl1w3P-.js
408 ms
event_classify.js
637 ms
gtm.js
35 ms
fbds.js
86 ms
xarrow-select.png.pagespeed.ic.vK4baPHPbI.png
151 ms
loading.gif
282 ms
xfull-banner-2016.png.pagespeed.ic.dQYMXMVWR1.jpg
551 ms
xlogo-small.png.pagespeed.ic.YzAs8qpHKY.png
281 ms
520x335xd7f34faf1bdf537aebab279b4e0bdd56_f7241.png.pagespeed.ic.uls8VPOIon.jpg
834 ms
520x335xdc610c1eaee7f9d38fc78c604e16e5a8_f7006.png.pagespeed.ic.9C2M8e-uOq.jpg
602 ms
520x335xa3f0ee79a867d876f582808367e1654d_f7110.jpg.pagespeed.ic.xIBsgorbtc.jpg
698 ms
logo-twitter.png
560 ms
logo-flickr.png
560 ms
xlogo-facebook.png.pagespeed.ic.EtwJbGJT7U.png
826 ms
xlogo-formspring.png.pagespeed.ic.RiKzWPKJUK.jpg
840 ms
xlogo-youtube.png.pagespeed.ic.d6VSh-IFwT.png
840 ms
xlogo-foursquare.png.pagespeed.ic.mOLB7A3Yvh.png
877 ms
xlogo-linkedin.png.pagespeed.ic.679C30eDRk.jpg
978 ms
xlogo-google-plus.png.pagespeed.ic.3KIYWRLuxN.png
1101 ms
xicon-matriculas.png.pagespeed.ic.WV5dZapR1_.png
1114 ms
xicon-sinef.png.pagespeed.ic.PK6VAZxX1v.png
1111 ms
icon-virtual.png
1116 ms
xicon-bib.png.pagespeed.ic.JgZhG4xSop.png
1152 ms
xicon-col.png.pagespeed.ic.TQZGZfs4YM.png
1256 ms
bg-header.png
1371 ms
xbullet-menu-loud.png.pagespeed.ic.exddUBvxHe.png
1382 ms
xbullet-menu.png.pagespeed.ic.BLkxsethmC.png
1386 ms
xbg-content.png.pagespeed.ic.dZZn9ASjqC.png
1378 ms
xbg-home.png.pagespeed.ic.Ugaw1-ypCD.png
1413 ms
DINMittelschriftStd.woff
1657 ms
analytics_debug.js
35 ms
572542.js
101 ms
hotjar-122739.js
102 ms
xbanner-previous.png.pagespeed.ic.i1hGlHNwfu.png
1606 ms
xbanner-next.png.pagespeed.ic.d6RdfJyqM3.png
1618 ms
xbg-tab-bar.png.pagespeed.ic.kH25Y9flgt.png
1618 ms
xarrow-right.png.pagespeed.ic.B09CqUuX7W.png
1620 ms
widgets.js
93 ms
xbg-button-big.png.pagespeed.ic._0oQjNSkzM.png
1629 ms
xbullet-list.png.pagespeed.ic.tW186OSuK9.png
1853 ms
bg-footer.png
1866 ms
sig-bolt.png
1868 ms
1878 ms
collect
18 ms
124 ms
collect
42 ms
collect
113 ms
6834.js
40 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
53 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
150 ms
s
89 ms
u
84 ms
ga-audiences
47 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
44 ms
jot
95 ms
bg-columns.png
142 ms
bg-submenu.png
143 ms
A.print.css.pagespeed.cf.H3g7uPXloe.css
282 ms
A.fumec-print.css.pagespeed.cf.7yDqN-6AE8.css
279 ms
__ptq.gif
14 ms
22 ms
fumec.br 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
fumec.br 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
fumec.br SEO score
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 Fumec.br 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 Fumec.br 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.
fumec.br
Open Graph description is not detected on the main page of FUMEC. 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: