6.9 sec in total
669 ms
5.3 sec
964 ms
Welcome to sadia.com.br homepage info - get ready to check Sadia best content for United States right away, or after learning these important things about sadia.com.br
Acesse e descubra centenas de receitas práticas e deliciosas para você fazer em casa.
Visit sadia.com.brWe analyzed Sadia.com.br page load time and found that the first response time was 669 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sadia.com.br performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value17.2 s
0/100
25%
Value20.4 s
0/100
10%
Value40,100 ms
0/100
30%
Value1
2/100
15%
Value54.5 s
0/100
10%
669 ms
265 ms
265 ms
265 ms
265 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 83% of them (65 requests) were addressed to the original Sadia.com.br, 4% (3 requests) were made to Cdn.luckyorange.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Sadia.com.br.
Page size can be reduced by 683.2 kB (6%)
10.9 MB
10.3 MB
In fact, the total size of Sadia.com.br main page is 10.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. 70% of websites need less resources to load. Images take 10.2 MB which makes up the majority of the site volume.
Potential reduce by 39.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. This page needs HTML code to be minified as it can gain 5.3 kB, which is 11% 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 39.3 kB or 83% of the original size.
Potential reduce by 144.9 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. Sadia images are well optimized though.
Potential reduce by 283.5 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 283.5 kB or 70% of the original size.
Potential reduce by 215.5 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. Sadia.com.br needs all CSS files to be minified and compressed as it can save up to 215.5 kB or 88% of the original size.
Number of requests can be reduced by 41 (55%)
74
33
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sadia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
sadia.com.br
669 ms
system.base.css
265 ms
system.menus.theme.css
265 ms
system.messages.theme.css
265 ms
system.theme.css
265 ms
comment.theme.css
301 ms
node.css
359 ms
field.theme.css
500 ms
search.theme.css
521 ms
youtube.css
521 ms
user.base.css
544 ms
views.css
559 ms
user.theme.css
639 ms
ctools.css
759 ms
jquery.fancybox.css
780 ms
omega.development.css
818 ms
brf-portalsadia.normalize.css
805 ms
brf-portalsadia.hacks.css
798 ms
brf-portalsadia.styles.css
1421 ms
owl.carousel.css
1058 ms
bootstrap.css
1170 ms
jquery.min.js
1452 ms
jquery.once.js
1087 ms
drupal.js
1264 ms
no-js.js
1317 ms
pt-br_JUcaQqaopjTGp_7iEfUhLrExN8iorVrVxTbbjcXlRiM.js
1350 ms
ajax_button.js
1410 ms
jquery.cycle2.min.js
1655 ms
jquery.fancybox.js
1839 ms
jquery.fancybox-media.js
1649 ms
produtos.js
1671 ms
cards.js
1679 ms
brf-portalsadia.behaviors.js
1748 ms
responsive.js
1917 ms
owl.carousel.min.js
2097 ms
bootstrap.css
658 ms
w.js
109 ms
sadia_logo.png
139 ms
card_0.png
749 ms
card_1_0.png
719 ms
card_2_1.png
787 ms
151109-Sadia-Site-TORTA-DE-FRANGO-6458_CARD_8.png
658 ms
card-emb2_1_0.png
525 ms
card-emb1_0.png
599 ms
MKP_PPSL_500130_V2_CARD_1.png
787 ms
341853_mkp_ppfb_v2_card_0.png
899 ms
campanhas_2.png
789 ms
redes.png
839 ms
redes-02.jpg
897 ms
redes-01.jpg
917 ms
redes-03.jpg
918 ms
redes-04.jpg
919 ms
gtm.js
110 ms
sprite.png
853 ms
menu-leaf.png
941 ms
landing_sadia_v6-1280_salamitos-corr2.png
1540 ms
landing_sadia_v6-1280_melancia-foto.jpg
1595 ms
header_4_0.jpg
1727 ms
banner-produtos_0.jpg
1073 ms
paper_fibers.png
972 ms
header_desk_campanhas_home_destaques_02.png
1452 ms
header_desk_campanhas_home_destaques_01.png
2511 ms
destaque_campanha_melancia_background_2.png
1468 ms
destaque_campanha_melancia_1.png
1698 ms
bg_redes.png
1740 ms
HelveticaNeue-MediumCond.woff
1686 ms
HelveticaNeue.woff
1725 ms
clickstream.min.js
21 ms
analytics.js
29 ms
124 ms
storage.luckyorange.net
62 ms
collect
11 ms
collect
66 ms
settings.luckyorange.net
35 ms
ga-audiences
42 ms
27 ms
mutation.min.js
25 ms
reset.css
5 ms
sadia.com.br 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.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
sadia.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
Missing source maps for large first-party JavaScript
sadia.com.br SEO score
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 doesn't use 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 Sadia.com.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 Sadia.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.
sadia.com.br
Open Graph description is not detected on the main page of Sadia. 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: