Tools & Wizards About Us
forsaleownerhomes.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

forsaleownerhomes.com

Page Load Speed

1.4 sec in total

First Response

431 ms

Resources Loaded

814 ms

Page Rendered

204 ms

forsaleownerhomes.com screenshot

About Website

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

For Sale Owner Homes.com is the nations largest website for homes for sale by owner(FSBO). Buy or sell your home without a real estate agent and save money.

Visit forsaleownerhomes.com

Key Findings

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

Performance Metrics

forsaleownerhomes.com performance score

0

Network Requests Diagram

forsaleownerhomes.com

431 ms

style.css

89 ms

credit2.jpg

389 ms

logo.jpg

190 ms

redpointer.gif

113 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Forsaleownerhomes.com, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (431 ms) belongs to the original domain Forsaleownerhomes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.8 kB (15%)

Content Size

199.7 kB

After Optimization

169.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forsaleownerhomes.com main page is 199.7 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. 15% of websites need less resources to load. Images take 144.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 25.3 kB

  • Original 32.1 kB
  • After minification 29.7 kB
  • After compression 6.8 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.3 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 1.1 kB

  • Original 144.3 kB
  • After minification 143.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. Forsaleownerhomes images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 747 B

  • Original 18.5 kB
  • After minification 18.3 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 3.6 kB

  • Original 4.8 kB
  • After minification 4.0 kB
  • After compression 1.2 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. Forsaleownerhomes.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (40%)

Requests Now

20

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forsaleownerhomes.com

forsaleownerhomes.com

431 ms

style.css

style.css

89 ms

credit2.jpg

credit2.jpg

389 ms

logo.jpg

logo.jpg

190 ms

redpointer.gif

redpointer.gif

113 ms

ajax.js

ajax.js

124 ms

ajax_counties.js

ajax_counties.js

121 ms

makeIcon.php

makeIcon.php

232 ms

makeIcon.php

makeIcon.php

358 ms

makeIcon.php

makeIcon.php

355 ms

usa02.gif

usa02.gif

258 ms

bgHeader.jpg

bgHeader.jpg

155 ms

barDivsGrads.jpg

barDivsGrads.jpg

154 ms

menuBG.jpg

menuBG.jpg

218 ms

divLineNav.gif

divLineNav.gif

241 ms

containerBG.jpg

containerBG.jpg

258 ms

redmap.jpg

redmap.jpg

255 ms

ga.js

ga.js

5 ms

containerDivLine.jpg

containerDivLine.jpg

243 ms

linked.gif

linked.gif

262 ms

__utm.gif

__utm.gif

11 ms

SEO Factors

forsaleownerhomes.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forsaleownerhomes.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 Forsaleownerhomes.com main page’s claimed encoding is . 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

forsaleownerhomes.com

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