57.5 sec in total
406 ms
37.7 sec
19.4 sec
Welcome to homes.com homepage info - get ready to check Homes best content for United States right away, or after learning these important things about homes.com
See why Homes.com is the #1 fastest growing real estate search site. Use our new neighborhood & school search to find your perfect home.
Visit homes.comWe analyzed Homes.com page load time and found that the first response time was 406 ms and then it took 57.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
homes.com performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value5.5 s
18/100
25%
Value3.2 s
92/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value5.4 s
71/100
10%
406 ms
68 ms
284 ms
360 ms
359 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 41% of them (15 requests) were addressed to the original Homes.com, 11% (4 requests) were made to and 11% (4 requests) were made to Blog-cdn.static-homes.com. The less responsive or slowest element that took the longest time to load (11 sec) relates to the external source Stats.g.doubleclick.net.
Page size can be reduced by 4.5 MB (40%)
11.2 MB
6.7 MB
In fact, the total size of Homes.com main page is 11.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 71.9 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 18.7 kB, which is 21% 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 71.9 kB or 81% of the original size.
Potential reduce by 68.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. Homes images are well optimized though.
Potential reduce by 3.6 MB
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 3.6 MB or 76% of the original size.
Potential reduce by 743.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. Homes.com needs all CSS files to be minified and compressed as it can save up to 743.6 kB or 71% of the original size.
Number of requests can be reduced by 7 (24%)
29
22
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
www.homes.com
406 ms
open-sans.css
68 ms
app.css
284 ms
main.css
360 ms
modernizr.js
359 ms
iMAWebCookie.js
10502 ms
main.js
2114 ms
socialize.js
10540 ms
analytics.js
8685 ms
vIXcTtBBgABVDvojgAA
113 ms
UZz8AZkYTjIAAVQ76I4AAA==
111 ms
dnf0AhmVG+gAAAAABVDvokAAA
87 ms
4O8N3AGRG9g7NigGgwiHQKjNrB1bGAIjYqO2MjI2BfZ2tvL4CTrvcEoOGKDgmyk94YUIENAdqMYg1NkcbE2EIFAcVxxCYgGE3AgEQcA7ExACQAAAVQ76I8AAA==
87 ms
Api.aspx
5841 ms
experience
1603 ms
nr-1044.min.js
3948 ms
collect
2743 ms
search-header--directive.html
2168 ms
home.html
2168 ms
home-page-footer--directive.html
2155 ms
national
1808 ms
homescom_logo.png
9444 ms
collect
10990 ms
homes-heart-harvey.png
2883 ms
jquery-1.6.2.min.js
2882 ms
bigstock-Entrance-Hall-And-Dining-Room-8477863-300x200.jpg
1792 ms
bigstock-Smiling-Young-Couple-Sitting-O-184525666-300x200.jpg
1838 ms
bigstock-Boys-Bedroom-1527933-267x200.jpg
1837 ms
app_promo_home.jpg
1594 ms
homepage-hero04.jpg
1791 ms
equal_housing_opportunity.gif
1594 ms
ad-choices.png
1524 ms
ga-audiences
542 ms
activityi;src=5670249;type=pagev0;cat=total0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=4028817049693.3164
1509 ms
homes-icons.woff
1055 ms
51800fdd97
2082 ms
51800fdd97
1731 ms
homes.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
homes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
homes.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homes.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Homes.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.
homes.com
Open Graph data is detected on the main page of Homes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: