9 sec in total
2.1 sec
6.4 sec
490 ms
Click here to check amazing Madrid content. Otherwise, check out these important facts you probably never knew about madrid.com.br
Visit madrid.com.brWe analyzed Madrid.com.br page load time and found that the first response time was 2.1 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
madrid.com.br performance score
2109 ms
23 ms
36 ms
306 ms
308 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 82% of them (53 requests) were addressed to the original Madrid.com.br, 8% (5 requests) were made to Boxepm.com.br and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Madrid.com.br.
Page size can be reduced by 819.3 kB (34%)
2.4 MB
1.6 MB
In fact, the total size of Madrid.com.br main page is 2.4 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 25.5 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 25.5 kB or 79% of the original size.
Potential reduce by 462.5 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, Madrid needs image optimization as it can save up to 462.5 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 222.7 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 222.7 kB or 69% of the original size.
Potential reduce by 108.6 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. Madrid.com.br needs all CSS files to be minified and compressed as it can save up to 108.6 kB or 82% of the original size.
Number of requests can be reduced by 29 (48%)
60
31
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Madrid. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.madrid.com.br
2109 ms
css
23 ms
css
36 ms
style.css
306 ms
styles.css
308 ms
shortcodes.css
460 ms
jquery-ui-1.8.16.custom.css
460 ms
custom.css
497 ms
pagenavi-css.css
336 ms
jquery.fancybox-1.3.4.css
477 ms
page_templates.css
637 ms
jquery.js
1025 ms
jquery-migrate.min.js
763 ms
vslider.js
774 ms
css
14 ms
style.css
764 ms
jquery.cycle.all.min.js
463 ms
jquery.easing.1.3.js
417 ms
superfish.js
539 ms
jquery.form.min.js
539 ms
scripts.js
689 ms
jquery.fullcalendar.min.js
1026 ms
jquery.simplemodal.1.4.3.min.js
754 ms
jquery.mousewheel.min.js
792 ms
jquery.jgrowl.min.js
825 ms
jquery.ui.core.min.js
839 ms
jquery.ui.datepicker.min.js
1148 ms
jquery.ui.datepicker-pt.js
1058 ms
jquery.init_show_calendar.js
1095 ms
jquery.easing-1.3.pack.js
1128 ms
jquery.fancybox-1.3.4.pack.js
1330 ms
et-ptemplates-frontend.js
1329 ms
malha-fundo.png
1870 ms
faixa-sidebar.jpg
484 ms
category-deco.png
486 ms
pagination_next.png
490 ms
fundo-info-panel-home.png
490 ms
top-bg.png
860 ms
logo-madrid.png
1047 ms
slogan-bg.png
903 ms
content-bg.png
925 ms
banner-adega-pequeno.jpg
1282 ms
banner-padaria-pequeno.jpg
1318 ms
slider-bg.png
1138 ms
ajax-loader.gif
1231 ms
SLIDER-NOVO-MADRID-TOP-475765_952x271.png
2438 ms
saude-52676_73x73.jpg
1351 ms
p%C3%A1o-de-queijo-28516_73x73.jpg
1443 ms
saude-8880_73x73.jpg
1534 ms
Receita-Madrid-9039_73x73.jpg
1584 ms
receita1-22110_73x73.jpg
1647 ms
caf%C3%A9-28839_73x73.jpg
1680 ms
torta-de-morango-36661_73x73.jpg
1751 ms
sa%C3%BAde-35305_73x73.jpg
1837 ms
fachada-madrid.png
2640 ms
footer-bg.png
1974 ms
facebook.png
2009 ms
twitter.png
2053 ms
footer-top-bg.png
2137 ms
cartoes-aceitos.png
2273 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
29 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
44 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
60 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
56 ms
ajax-loader.gif
1466 ms
madrid.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 Madrid.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 Madrid.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.
madrid.com.br
Open Graph description is not detected on the main page of Madrid. 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: