6.7 sec in total
503 ms
5.8 sec
418 ms
Click here to check amazing Flavio Oliz content. Otherwise, check out these important facts you probably never knew about flaviooliz.com.br
Encontre seu futuro imóvel aqui - Apartamentos, casas e terrenos na Serra Gaúcha e litoral do Rio Grande do Sul
Visit flaviooliz.com.brWe analyzed Flaviooliz.com.br page load time and found that the first response time was 503 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
flaviooliz.com.br performance score
503 ms
2682 ms
24 ms
847 ms
880 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original Flaviooliz.com.br, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Flaviooliz.com.br.
Page size can be reduced by 635.7 kB (49%)
1.3 MB
652.9 kB
In fact, the total size of Flaviooliz.com.br main page is 1.3 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. 50% of websites need less resources to load. Images take 486.0 kB which makes up the majority of the site volume.
Potential reduce by 60.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 26.7 kB, which is 38% 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 60.4 kB or 85% of the original size.
Potential reduce by 11.2 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. Flavio Oliz images are well optimized though.
Potential reduce by 311.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 311.4 kB or 72% of the original size.
Potential reduce by 252.7 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. Flaviooliz.com.br needs all CSS files to be minified and compressed as it can save up to 252.7 kB or 85% of the original size.
Number of requests can be reduced by 38 (64%)
59
21
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flavio Oliz. 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 7 to 1 for CSS and as a result speed up the page load time.
flaviooliz.com.br
503 ms
www.flaviooliz.com.br
2682 ms
css
24 ms
font-awesome.min.css
847 ms
jquery-ui-1.10.2.custom.min.css
880 ms
titanlighbox.css
757 ms
bootstrap.css
1330 ms
style.css
1301 ms
jquery.toastmessage.css
752 ms
jquery.min.js
72 ms
jquery-ui.min.js
95 ms
jquery.toastmessage.js
866 ms
WebResource.axd
615 ms
ScriptResource.axd
620 ms
ScriptResource.axd
730 ms
js
83 ms
bootstrap.min.js
633 ms
prettify.js
498 ms
jquery.ezmark.js
509 ms
jquery.currency.js
607 ms
jquery.cookie.js
653 ms
jquery.easing.1.3.js
662 ms
jquery.titanlighbox.js
730 ms
carousel.js
889 ms
chosen.jquery.min.js
798 ms
jquery.iosslider.min.js
938 ms
main.js
871 ms
jquery.mask.min.js
884 ms
webresource.axd
585 ms
scriptresource.axd
638 ms
scriptresource.axd
609 ms
analytics.js
10 ms
logo.png
300 ms
destaque1.jpg
458 ms
destaque3.jpg
809 ms
destaque4.jpg
578 ms
destaque5.jpg
459 ms
destaque6.jpg
526 ms
img.ashx
499 ms
etiqueta-Lancamento.png
550 ms
img.ashx
709 ms
img.ashx
766 ms
etiqueta-Obra.png
668 ms
img.ashx
820 ms
img.ashx
893 ms
img.ashx
815 ms
img.ashx
1268 ms
img.ashx
942 ms
img.ashx
990 ms
img.ashx
1345 ms
collect
3 ms
collect
52 ms
btn-nav.png
736 ms
arrow-bottom-black.png
810 ms
footer-border.png
856 ms
arrow-right-white.png
895 ms
bathrooms-white.png
912 ms
bedrooms-white.png
967 ms
bedrooms.png
1019 ms
bathrooms.png
1056 ms
arrow-left-white.png
1068 ms
pop-ligamos.html
1103 ms
pop-fale.html
1170 ms
call-to-action-address.png
1128 ms
call-to-action-key.png
1175 ms
call-to-action-gps.png
1176 ms
twitter.png
1213 ms
facebook.png
1235 ms
google.png
1285 ms
bg_barra_inferior.png
1295 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
154 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
153 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
154 ms
fontawesome-webfont.woff
1315 ms
search.png
1184 ms
arrow-bottom-mult.png
1210 ms
etiqueta-lancamento.png
1139 ms
etiqueta-obra.png
1069 ms
retina.js
351 ms
bootstrap-fileupload.js
382 ms
flaviooliz.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 Flaviooliz.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 Flaviooliz.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.
flaviooliz.com.br
Open Graph description is not detected on the main page of Flavio Oliz. 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: