Tools & Wizards About Us
antiquehome.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

antiquehome.org

Old Houses For Sale - Discover Interesting Old Homes

Page Load Speed

2.7 sec in total

First Response

45 ms

Resources Loaded

1.2 sec

Page Rendered

1.4 sec

antiquehome.org screenshot

About Website

Visit antiquehome.org now to see the best up-to-date Antiquehome content for United States and also check out these interesting facts you probably never knew about antiquehome.org

Old Houses For Sale is a premier real estate marketplace for antique, historical, and old homes. Browse current listings or list a home right here.

Visit antiquehome.org

Key Findings

We analyzed Antiquehome.org page load time and found that the first response time was 45 ms and then it took 2.6 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

antiquehome.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value4,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value32.2 s

0/100

10%

Network Requests Diagram

antiquehome.org

45 ms

oldhousesforsale.com

90 ms

ads.min.js

176 ms

js

74 ms

main.app.css

31 ms

Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Antiquehome.org, 72% (98 requests) were made to Oldhousesforsale.com and 15% (20 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (763 ms) relates to the external source Oldhousesforsale.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.4 kB (11%)

Content Size

2.6 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Antiquehome.org main page is 2.6 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. Only a small number of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 265.6 kB

  • Original 324.4 kB
  • After minification 315.0 kB
  • After compression 58.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 265.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1.0 kB

  • Original 1.4 MB
  • After minification 1.4 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. Antiquehome images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.4 kB

  • Original 652.3 kB
  • After minification 652.3 kB
  • After compression 650.0 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

-15%

Potential reduce by 25.4 kB

  • Original 172.7 kB
  • After minification 172.3 kB
  • After compression 147.3 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. Antiquehome.org needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (70%)

Requests Now

109

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

antiquehome.org

antiquehome.org

45 ms

oldhousesforsale.com

oldhousesforsale.com

90 ms

ads.min.js

ads.min.js

176 ms

js

js

74 ms

main.app.css

main.app.css

31 ms

css2

css2

63 ms

blocks.style.build.css

blocks.style.build.css

47 ms

bootstrap.min.css

bootstrap.min.css

55 ms

bootstrap-select.min.css

bootstrap-select.min.css

53 ms

all.min.css

all.min.css

50 ms

icons.css

icons.css

48 ms

slick-min.css

slick-min.css

53 ms

slick-theme-min.css

slick-theme-min.css

63 ms

jquery-ui.min.css

jquery-ui.min.css

62 ms

radio-checkbox-min.css

radio-checkbox-min.css

64 ms

bootstrap-datepicker.min.css

bootstrap-datepicker.min.css

64 ms

main.css

main.css

105 ms

styling-options.css

styling-options.css

66 ms

style.css

style.css

67 ms

elementor-icons.min.css

elementor-icons.min.css

99 ms

frontend-lite.min.css

frontend-lite.min.css

94 ms

swiper.min.css

swiper.min.css

100 ms

post-8.css

post-8.css

101 ms

frontend-lite.min.css

frontend-lite.min.css

101 ms

post-44402.css

post-44402.css

116 ms

css

css

99 ms

jquery.min.js

jquery.min.js

117 ms

jquery-migrate.min.js

jquery-migrate.min.js

117 ms

frontend-gtag.min.js

frontend-gtag.min.js

118 ms

js

js

43 ms

js

js

91 ms

widget-call-to-action.min.css

widget-call-to-action.min.css

117 ms

widget-posts.min.css

widget-posts.min.css

117 ms

animations.min.css

animations.min.css

116 ms

rs6.css

rs6.css

116 ms

child-scripts.js

child-scripts.js

117 ms

rbtools.min.js

rbtools.min.js

148 ms

rs6.min.js

rs6.min.js

151 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

148 ms

bootstrap-select.min.js

bootstrap-select.min.js

148 ms

modernizr.custom.js

modernizr.custom.js

149 ms

slideout.min.js

slideout.min.js

150 ms

lightbox.min.js

lightbox.min.js

151 ms

api.js

api.js

56 ms

jquery.validate.min.js

jquery.validate.min.js

84 ms

theia-sticky-sidebar.min.js

theia-sticky-sidebar.min.js

150 ms

slick.min.js

slick.min.js

140 ms

houzez-instant-page.js

houzez-instant-page.js

122 ms

core.min.js

core.min.js

119 ms

menu.min.js

menu.min.js

118 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

119 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

118 ms

wp-polyfill.min.js

wp-polyfill.min.js

112 ms

dom-ready.min.js

dom-ready.min.js

110 ms

hooks.min.js

hooks.min.js

110 ms

i18n.min.js

i18n.min.js

108 ms

a11y.min.js

a11y.min.js

109 ms

style.css

style.css

106 ms

autocomplete.min.js

autocomplete.min.js

176 ms

mouse.min.js

mouse.min.js

144 ms

slider.min.js

slider.min.js

144 ms

css

css

58 ms

jquery.vide.min.js

jquery.vide.min.js

143 ms

custom.js

custom.js

143 ms

houzez-validate.js

houzez-validate.js

130 ms

jquery.form.min.js

jquery.form.min.js

129 ms

imagesloaded.min.js

imagesloaded.min.js

129 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

129 ms

webpack.runtime.min.js

webpack.runtime.min.js

128 ms

frontend-modules.min.js

frontend-modules.min.js

181 ms

frontend.min.js

frontend.min.js

180 ms

waypoints.min.js

waypoints.min.js

179 ms

frontend.min.js

frontend.min.js

179 ms

elements-handlers.min.js

elements-handlers.min.js

179 ms

underscore.min.js

underscore.min.js

149 ms

wp-util.min.js

wp-util.min.js

214 ms

frontend.min.js

frontend.min.js

213 ms

js

js

180 ms

js

js

436 ms

dmca_protected_sml_120n.png

dmca_protected_sml_120n.png

694 ms

Old-Houses-For-Sale-Logo-Footer.png

Old-Houses-For-Sale-Logo-Footer.png

157 ms

Old-Houses-For-Sale-Background-1.jpg

Old-Houses-For-Sale-Background-1.jpg

688 ms

Our-Old-House-Facebook-Group-1024x534.jpg

Our-Old-House-Facebook-Group-1024x534.jpg

390 ms

Our-Old-House-Is-For-Sale-Facebook-Group-1024x534.jpg

Our-Old-House-Is-For-Sale-Facebook-Group-1024x534.jpg

757 ms

20240504_194846_240-592x444.webp

20240504_194846_240-592x444.webp

649 ms

20240502_005042_062-592x444.webp

20240502_005042_062-592x444.webp

616 ms

20240422_000956_651-592x444.webp

20240422_000956_651-592x444.webp

686 ms

20240411_004838_967-592x444.webp

20240411_004838_967-592x444.webp

647 ms

20240401_225256_349-592x444.webp

20240401_225256_349-592x444.webp

686 ms

20240401_010803_503-592x444.webp

20240401_010803_503-592x444.webp

757 ms

20240401_003855_420-592x444.webp

20240401_003855_420-592x444.webp

759 ms

20240330_013638_331-592x444.webp

20240330_013638_331-592x444.webp

759 ms

20240330_011328_275-592x444.jpg

20240330_011328_275-592x444.jpg

755 ms

20240326_023656_071-592x444.webp

20240326_023656_071-592x444.webp

763 ms

Vintage-House-Plans-1-1024x576.jpeg

Vintage-House-Plans-1-1024x576.jpeg

761 ms

Abandoned-Richardson-Kennedy-House-300x157.jpg

Abandoned-Richardson-Kennedy-House-300x157.jpg

761 ms

Should-I-Add-a-Bathroom-Before-Selling-300x169.jpg

Should-I-Add-a-Bathroom-Before-Selling-300x169.jpg

762 ms

Why-Did-Old-Houses-Have-Doors-Between-Bedrooms-300x169.jpg

Why-Did-Old-Houses-Have-Doors-Between-Bedrooms-300x169.jpg

762 ms

Why-Did-Old-Houses-Have-Two-Front-Doors-300x169.jpg

Why-Did-Old-Houses-Have-Two-Front-Doors-300x169.jpg

760 ms

How-Do-You-Make-An-Old-House-Look-Good-To-Sell-300x169.jpg

How-Do-You-Make-An-Old-House-Look-Good-To-Sell-300x169.jpg

762 ms

Is-It-Worth-Buying-an-Old-House-and-Renovating-300x169.jpg

Is-It-Worth-Buying-an-Old-House-and-Renovating-300x169.jpg

761 ms

Is-It-Smart-To-Pay-For-A-House-In-Cash-300x169.jpg

Is-It-Smart-To-Pay-For-A-House-In-Cash-300x169.jpg

761 ms

How-Do-You-Avoid-Buying-a-Money-Pit-300x169.jpg

How-Do-You-Avoid-Buying-a-Money-Pit-300x169.jpg

761 ms

How-Long-Are-You-Liable-After-Selling-A-House-300x169.jpg

How-Long-Are-You-Liable-After-Selling-A-House-300x169.jpg

761 ms

rid

rid

352 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

322 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

411 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

533 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

550 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

618 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

617 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

584 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

583 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

617 ms

analytics.js

analytics.js

262 ms

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxY.ttf

534 ms

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcU.ttf

539 ms

92zPtBhPNqw79Ij1E865zBUv7mx9IjVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mx9IjVBNI0.ttf

539 ms

92zPtBhPNqw79Ij1E865zBUv7mxEIjVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mxEIjVBNI0.ttf

539 ms

92zPtBhPNqw79Ij1E865zBUv7mwjIjVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mwjIjVBNI0.ttf

538 ms

92zPtBhPNqw79Ij1E865zBUv7mwKIjVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mwKIjVBNI0.ttf

538 ms

92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI0.ttf

538 ms

92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI0.ttf

603 ms

92zPtBhPNqw79Ij1E865zBUv7mz9JTVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mz9JTVBNI0.ttf

603 ms

92zPtBhPNqw79Ij1E865zBUv7mwjJTVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7mwjJTVBNI0.ttf

603 ms

92zPtBhPNqw79Ij1E865zBUv7myjJDVBNI0.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJDVBNI0.ttf

602 ms

houzez-iconfont.ttf

houzez-iconfont.ttf

614 ms

fa-regular-400.woff

fa-regular-400.woff

614 ms

fa-solid-900.woff

fa-solid-900.woff

615 ms

recaptcha__en.js

recaptcha__en.js

308 ms

abd.js

abd.js

190 ms

collect

collect

128 ms

prev.png

prev.png

182 ms

next.png

next.png

183 ms

loading.gif

loading.gif

183 ms

close.png

close.png

184 ms

Accessibility Review

antiquehome.org accessibility score

89

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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

antiquehome.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

antiquehome.org SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antiquehome.org 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 Antiquehome.org 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

antiquehome.org

Open Graph data is detected on the main page of Antiquehome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: