6.8 sec in total
1.4 sec
4.9 sec
475 ms
Welcome to faenge.com.br homepage info - get ready to check Faenge best content right away, or after learning these important things about faenge.com.br
Visit faenge.com.brWe analyzed Faenge.com.br page load time and found that the first response time was 1.4 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
faenge.com.br performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value15.5 s
0/100
25%
Value10.0 s
9/100
10%
Value310 ms
78/100
30%
Value0.892
3/100
15%
Value16.1 s
6/100
10%
1443 ms
513 ms
260 ms
652 ms
263 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 88% of them (60 requests) were addressed to the original Faenge.com.br, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Faenge.com.br.
Page size can be reduced by 880.6 kB (30%)
2.9 MB
2.0 MB
In fact, the total size of Faenge.com.br main page is 2.9 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. 45% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 27.4 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 9.1 kB, which is 28% 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 27.4 kB or 83% of the original size.
Potential reduce by 386.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. Obviously, Faenge needs image optimization as it can save up to 386.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 395.3 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 395.3 kB or 71% of the original size.
Potential reduce by 71.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. Faenge.com.br needs all CSS files to be minified and compressed as it can save up to 71.9 kB or 82% of the original size.
Number of requests can be reduced by 31 (48%)
64
33
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faenge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
faenge.com.br
1443 ms
main.css
513 ms
stylesheet.css
260 ms
jquery-1.6.2.min.js
652 ms
padrao.js
263 ms
latest.js
1001 ms
modernizr.js
286 ms
jquery.validate.js
643 ms
jquery.maskedinput.js
394 ms
jquery.validacao.forms.js
429 ms
jquery.easing-1.3.pack.js
526 ms
jquery.mousewheel-3.0.4.pack.js
572 ms
jquery.fancybox-1.3.4.js
640 ms
fancybox.site.js
672 ms
plugins.js
1138 ms
script.js
770 ms
modernizr.custom.js
771 ms
jquery.autocomplete.css
780 ms
jquery.zoom.css
789 ms
dropdown.css
901 ms
pagination.css
902 ms
subModal.css
912 ms
skintango.css
920 ms
skintango-dest.css
1032 ms
jquery.fancybox-1.3.4.css
1157 ms
component.css
1043 ms
conversion.js
15 ms
ga.js
33 ms
bg_fade.jpg
136 ms
139566607039.jpg
1289 ms
13251617739646.png
135 ms
13240418975542.jpg
774 ms
133218046308.png
137 ms
13167020892302.jpg
286 ms
13166287766606.jpg
393 ms
13160271433792.jpg
397 ms
13167139332945.jpg
528 ms
13166999948168.jpg
430 ms
13166970753192.jpg
524 ms
13218811728585.png
658 ms
13166981106427.jpg
855 ms
logo_ademi.png
654 ms
logo_sinduscom.png
659 ms
logo_bureau.png
785 ms
logo_pbqp.png
790 ms
logo_extendida.png
907 ms
bt4.png
1142 ms
bg_menu.png
903 ms
itens_menu.png
909 ms
banner_bg.jpg
1127 ms
title_home.png
1419 ms
bg-search.png
1040 ms
bt_search.png
1043 ms
all_results.png
1175 ms
box_title.png
1175 ms
sprite_home.png
2260 ms
bg_ultimas.png
1272 ms
sep-dote.png
1305 ms
bg_revista.png
1304 ms
popup_flutuante_duvida_01.png
1409 ms
logo.png
1399 ms
webroom.png
1436 ms
64 ms
__utm.gif
20 ms
collect
51 ms
40 ms
ga-audiences
23 ms
mTag.js
86 ms
faenge.com.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.
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
faenge.com.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
faenge.com.br 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faenge.com.br 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 Faenge.com.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.
faenge.com.br
Open Graph description is not detected on the main page of Faenge. 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: