7.3 sec in total
1.5 sec
4.6 sec
1.2 sec
Visit frangobar.com.br now to see the best up-to-date Frangobar content and also check out these interesting facts you probably never knew about frangobar.com.br
Visit frangobar.com.brWe analyzed Frangobar.com.br page load time and found that the first response time was 1.5 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
frangobar.com.br performance score
1477 ms
562 ms
422 ms
419 ms
302 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 71% of them (50 requests) were addressed to the original Frangobar.com.br, 10% (7 requests) were made to Farm4.staticflickr.com and 10% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Frangobar.com.br.
Page size can be reduced by 324.6 kB (27%)
1.2 MB
879.6 kB
In fact, the total size of Frangobar.com.br main page is 1.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. 40% of websites need less resources to load. Images take 788.8 kB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 12.3 kB, which is 29% 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 36.1 kB or 85% of the original size.
Potential reduce by 5.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. Frangobar images are well optimized though.
Potential reduce by 191.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 191.3 kB or 71% of the original size.
Potential reduce by 92.0 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. Frangobar.com.br needs all CSS files to be minified and compressed as it can save up to 92.0 kB or 88% of the original size.
Number of requests can be reduced by 41 (61%)
67
26
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frangobar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
frangobar.com.br
1477 ms
style.css
562 ms
components.css
422 ms
responsive.css
419 ms
cardozafacebook.css
302 ms
jquery.js
719 ms
jquery-migrate.min.js
413 ms
cardozafacebook.js
554 ms
supersized.js
752 ms
supersized.shutter.js
694 ms
easing.js
698 ms
sticky.js
698 ms
datepicker.js
844 ms
tweet.js
841 ms
prettyphoto.js
976 ms
form.js
847 ms
validate.js
860 ms
custom.js
860 ms
download
142 ms
badge_code_v2.gne
121 ms
jquery.ui.core.min.js
935 ms
comment-reply.min.js
935 ms
bg-header.png
192 ms
bg-header-container.png
192 ms
logo_frango1.png
286 ms
bg-menu.png
187 ms
arrow-prev.png
186 ms
arrow-next.png
183 ms
bg-overlay-pattern.png
278 ms
bg-content.png
282 ms
bg-callout-title.png
285 ms
loading.gif
287 ms
box_especialidades.jpg
286 ms
bg-overlay-dark-25.png
420 ms
bg-button.png
431 ms
tripadv-frango-2014.gif
437 ms
box_historia.jpg
437 ms
icon-comments.png
436 ms
frango-nyt-226x120.jpg
437 ms
coxinha-frango-226x120.jpg
561 ms
coxinha1-226x120.jpg
575 ms
bg-widget-area-footer.png
585 ms
OpenSans-Regular-webfont.woff
808 ms
OpenSans-CondLight-webfont.woff
814 ms
OpenSans-CondBold-webfont.woff
732 ms
3231762572_f928fcbe8d_s.jpg
54 ms
4621064557_124d9e800f_s.jpg
54 ms
p
44 ms
3231763116_5f18665bee_s.jpg
43 ms
3231985230_4fb173395d_s.jpg
92 ms
3231138395_cc6a0300b0_s.jpg
90 ms
3231831682_4c03a921d2_s.jpg
94 ms
3230912453_2800204260_s.jpg
94 ms
3231764266_0b8b554ccb_s.jpg
95 ms
bg-a.png
696 ms
bg-footer.png
692 ms
icon-twitter.png
694 ms
icon-facebook.png
791 ms
icon-flickr.png
791 ms
likebox.php
209 ms
user_timeline.json
39 ms
slide_balcao.jpg
1672 ms
hDvwL1_H7g-.css
190 ms
q68gy-v_YMF.js
311 ms
FJmpeSpHpjS.js
388 ms
0wM5s1Khldu.js
343 ms
1bNoFZUdlYZ.js
342 ms
I6-MnjEovm5.js
44 ms
pQrUxxo5oQp.js
43 ms
OpenSans-Bold-webfont.woff
420 ms
frangobar.com.br SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frangobar.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 Frangobar.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.
frangobar.com.br
Open Graph description is not detected on the main page of Frangobar. 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: