Tools & Wizards About Us
hoome.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hoome.com

Properties in Mallorca, Ibiza & Menorca - FIND YOUR HOOME

Page Load Speed

1.6 sec in total

First Response

334 ms

Resources Loaded

1.1 sec

Page Rendered

144 ms

hoome.com screenshot

About Website

Click here to check amazing HOOME content. Otherwise, check out these important facts you probably never knew about hoome.com

The leading real estate marketplace for the Balearics. Search thousands of for-sale and rental listings and connect with local professionals.

Visit hoome.com

Key Findings

We analyzed Hoome.com page load time and found that the first response time was 334 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

hoome.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value17,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

hoome.com

334 ms

return_js.php

265 ms

jquery.min.js

4 ms

tg.php

236 ms

search_caf.php

245 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 30% of them (6 requests) were addressed to the original Hoome.com, 15% (3 requests) were made to Static.uniregistry.com and 10% (2 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (334 ms) belongs to the original domain Hoome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.3 kB (31%)

Content Size

729.1 kB

After Optimization

502.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hoome.com main page is 729.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 419.1 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 1.2 kB

  • Original 2.0 kB
  • After minification 1.9 kB
  • After compression 828 B

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 1.2 kB or 59% of the original size.

Image Optimization

-0%

Potential reduce by 667 B

  • Original 308.0 kB
  • After minification 307.3 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. HOOME images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 224.4 kB

  • Original 419.1 kB
  • After minification 419.1 kB
  • After compression 194.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 224.4 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (24%)

Requests Now

17

After Optimization

13

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

hoome.com

hoome.com

334 ms

return_js.php

return_js.php

265 ms

jquery.min.js

jquery.min.js

4 ms

tg.php

tg.php

236 ms

search_caf.php

search_caf.php

245 ms

page.php

page.php

239 ms

track.php

track.php

237 ms

img.php

img.php

236 ms

partner.gif

partner.gif

13 ms

caf.js

caf.js

45 ms

ur-logo-white.png

ur-logo-white.png

188 ms

caf.gif

caf.gif

22 ms

ads

ads

50 ms

slave.html

slave.html

8 ms

domainpark.cgi

domainpark.cgi

143 ms

async_survey

async_survey

18 ms

bg-parking.jpg

bg-parking.jpg

151 ms

2191FE_4_0.woff

2191FE_4_0.woff

140 ms

prompt_embed_static.js

prompt_embed_static.js

4 ms

chevron-gray.png

chevron-gray.png

11 ms

Accessibility Review

hoome.com accessibility score

96

Accessibility Issues

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

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

hoome.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

hoome.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hoome.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hoome.com 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.

Social Sharing Optimization

hoome.com

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