Tools & Wizards About Us
onehouse.hcpro.pt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onehouse.hcpro.pt

Habitarnocentro.com - Portal de Imobiliário

Page Load Speed

3.8 sec in total

First Response

967 ms

Resources Loaded

2.6 sec

Page Rendered

251 ms

onehouse.hcpro.pt screenshot

About Website

Welcome to onehouse.hcpro.pt homepage info - get ready to check Onehouse Hcpro best content for Portugal right away, or after learning these important things about onehouse.hcpro.pt

Portal imobiliário nacional - Quer comprar, vender ou alugar casa? Temos milhares de apartamentos e moradias em Lisboa, no Porto e por todo o país.

Visit onehouse.hcpro.pt

Key Findings

We analyzed Onehouse.hcpro.pt page load time and found that the first response time was 967 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

onehouse.hcpro.pt performance score

0

Network Requests Diagram

onehouse.hcpro.pt

967 ms

estilos.css

395 ms

jquery.min.js

28 ms

show_ads.js

5 ms

funcoes_js.js

132 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 52% of them (51 requests) were addressed to the original Onehouse.hcpro.pt, 10% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Onehouse.hcpro.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 528.9 kB (22%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onehouse.hcpro.pt main page is 2.5 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 26.9 kB

  • Original 34.3 kB
  • After minification 31.3 kB
  • After compression 7.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. 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 26.9 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 150.2 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Onehouse Hcpro images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 339.4 kB

  • Original 579.2 kB
  • After minification 578.7 kB
  • After compression 239.8 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 339.4 kB or 59% of the original size.

CSS Optimization

-81%

Potential reduce by 12.3 kB

  • Original 15.1 kB
  • After minification 13.7 kB
  • After compression 2.8 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. Onehouse.hcpro.pt needs all CSS files to be minified and compressed as it can save up to 12.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (30%)

Requests Now

96

After Optimization

67

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onehouse Hcpro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

onehouse.hcpro.pt

onehouse.hcpro.pt

967 ms

estilos.css

estilos.css

395 ms

jquery.min.js

jquery.min.js

28 ms

show_ads.js

show_ads.js

5 ms

funcoes_js.js

funcoes_js.js

132 ms

bjqs-1.3.min.js

bjqs-1.3.min.js

232 ms

among_us.js

among_us.js

295 ms

18128_03191F0AE5DA4EA6AF4A6EB119A5A3DE_XL.JPG

18128_03191F0AE5DA4EA6AF4A6EB119A5A3DE_XL.JPG

972 ms

marca_marca_402954_loja.jpg

marca_marca_402954_loja.jpg

1237 ms

1017_57_101315_001.jpg

1017_57_101315_001.jpg

624 ms

cream_dust.png

cream_dust.png

160 ms

logo.png

logo.png

204 ms

botao_inserir.png

botao_inserir.png

366 ms

star.png

star.png

230 ms

facebook.png

facebook.png

276 ms

youtube.png

youtube.png

280 ms

botao_emprego.png

botao_emprego.png

307 ms

form_valid_nat.png

form_valid_nat.png

485 ms

form_valid_imo.png

form_valid_imo.png

489 ms

form_valid_dis.png

form_valid_dis.png

544 ms

lateral_esquerdo_mapa_3.png

lateral_esquerdo_mapa_3.png

627 ms

banner.png

banner.png

605 ms

banner2.png

banner2.png

857 ms

banner_reilar.jpg

banner_reilar.jpg

690 ms

banner_habitar.jpg

banner_habitar.jpg

929 ms

banner_globalquintas.jpg

banner_globalquintas.jpg

1061 ms

banner_valordemercado.jpg

banner_valordemercado.jpg

678 ms

banner_famalicao.jpg

banner_famalicao.jpg

857 ms

banner_lavita.jpg

banner_lavita.jpg

792 ms

banner_quadratura.jpg

banner_quadratura.jpg

973 ms

banner_escolhaacertada.jpg

banner_escolhaacertada.jpg

907 ms

banner_anabelasousa.jpg

banner_anabelasousa.jpg

1100 ms

banner_hall.jpg

banner_hall.jpg

1107 ms

banner_go.jpg

banner_go.jpg

1020 ms

banner_impacto.jpg

banner_impacto.jpg

1039 ms

banner_limalitoral.jpg

banner_limalitoral.jpg

1332 ms

banner_sintraneves.jpg

banner_sintraneves.jpg

1134 ms

banner_qualisa.jpg

banner_qualisa.jpg

1164 ms

banner_espacos.jpg

banner_espacos.jpg

1178 ms

banner_copimovel.jpg

banner_copimovel.jpg

1222 ms

banner_exitcasa2.jpg

banner_exitcasa2.jpg

1217 ms

banner_imosonho.jpg

banner_imosonho.jpg

1248 ms

914672_1986146_1x.jpg

914672_1986146_1x.jpg

1275 ms

ca-pub-0894668309032582.js

ca-pub-0894668309032582.js

34 ms

zrt_lookup.html

zrt_lookup.html

41 ms

show_ads_impl.js

show_ads_impl.js

57 ms

banner_quintela.jpg

banner_quintela.jpg

1255 ms

banner_lcs.gif

banner_lcs.gif

1259 ms

ads

ads

344 ms

osd.js

osd.js

17 ms

analytics.js

analytics.js

15 ms

likebox.php

likebox.php

221 ms

ads

ads

330 ms

banner_rochagest.jpg

banner_rochagest.jpg

1181 ms

collect

collect

41 ms

banner_markiclass.jpg

banner_markiclass.jpg

1169 ms

tc.js

tc.js

19 ms

banner_amberstar.jpg

banner_amberstar.jpg

1146 ms

banner_arcadasliz.jpg

banner_arcadasliz.jpg

1171 ms

p

p

50 ms

banner_zebimed.jpg

banner_zebimed.jpg

1193 ms

14-bottom.png

14-bottom.png

7 ms

banner_rigor.jpg

banner_rigor.jpg

1176 ms

v2

v2

64 ms

banner_arcada.jpg

banner_arcada.jpg

1178 ms

banner_areasluz.jpg

banner_areasluz.jpg

1168 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

43 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

48 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

50 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

74 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

72 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

42 ms

dpx

dpx

26 ms

banner_dialprogresso.jpg

banner_dialprogresso.jpg

1116 ms

62359_469462666444576_1441093702_n.jpg

62359_469462666444576_1441093702_n.jpg

62 ms

734068_469464976444345_797632822_n.jpg

734068_469464976444345_797632822_n.jpg

42 ms

12278634_492181900961372_8635226204396349188_n.jpg

12278634_492181900961372_8635226204396349188_n.jpg

45 ms

1977132_488103184629750_1211523185_n.jpg

1977132_488103184629750_1211523185_n.jpg

47 ms

12243206_912127985503592_8776707206527304891_n.jpg

12243206_912127985503592_8776707206527304891_n.jpg

48 ms

558548_385454491494305_590269576_n.jpg

558548_385454491494305_590269576_n.jpg

46 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

27 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

39 ms

m_js_controller.js

m_js_controller.js

49 ms

abg.js

abg.js

69 ms

banner_imokasa.jpg

banner_imokasa.jpg

1019 ms

logo_trilhos.png

logo_trilhos.png

1054 ms

ca.png

ca.png

218 ms

xrefid.xgi

xrefid.xgi

7 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

20 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

21 ms

favicon

favicon

102 ms

favicon

favicon

142 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

93 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

73 ms

s

s

67 ms

header_bg.png

header_bg.png

956 ms

x_button_blue2.png

x_button_blue2.png

26 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

5 ms

52154.gif

52154.gif

13 ms

SEO Factors

onehouse.hcpro.pt SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onehouse.hcpro.pt 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 Onehouse.hcpro.pt main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

onehouse.hcpro.pt

Open Graph description is not detected on the main page of Onehouse Hcpro. 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: