Tools & Wizards About Us
spatialmatch.com screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

spatialmatch.com

Real Estate Data Provider & Agent Marketing Solutions | Home Junction

Page Load Speed

1.9 sec in total

First Response

48 ms

Resources Loaded

816 ms

Page Rendered

991 ms

spatialmatch.com screenshot

About Website

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

Home Junction provides real estate & property data for agents, brokers, & enterprise. Contact us to learn about our API, application, & Wordpress solutions.

Visit spatialmatch.com

Key Findings

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

Performance Metrics

spatialmatch.com performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value18,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

homejunction.com

48 ms

www.homejunction.com

99 ms

A.all-skins.css,qver=4.3.1.pagespeed.cf.byk1d3mPJg.css

36 ms

A.bootstrap.min.css,qver=4.3.1.pagespeed.cf.5GpFhJF29r.css

40 ms

A.main.min.css,qver=1.18.pagespeed.cf.7coPmLi0XZ.css

30 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Spatialmatch.com, 7% (4 requests) were made to Google-analytics.com and 5% (3 requests) were made to Sdk.engage.co. The less responsive or slowest element that took the longest time to load (197 ms) relates to the external source Homejunction.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 959.2 kB (48%)

Content Size

2.0 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 103.6 kB

  • Original 126.9 kB
  • After minification 126.9 kB
  • After compression 23.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 103.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 6.9 kB

  • Original 664.8 kB
  • After minification 657.9 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. Spatialmatch images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 346.0 kB

  • Original 564.1 kB
  • After minification 561.1 kB
  • After compression 218.1 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 346.0 kB or 61% of the original size.

CSS Optimization

-79%

Potential reduce by 502.7 kB

  • Original 640.0 kB
  • After minification 636.0 kB
  • After compression 137.4 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. Spatialmatch.com needs all CSS files to be minified and compressed as it can save up to 502.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (66%)

Requests Now

50

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

homejunction.com

homejunction.com

48 ms

www.homejunction.com

www.homejunction.com

99 ms

A.all-skins.css,qver=4.3.1.pagespeed.cf.byk1d3mPJg.css

A.all-skins.css,qver=4.3.1.pagespeed.cf.byk1d3mPJg.css

36 ms

A.bootstrap.min.css,qver=4.3.1.pagespeed.cf.5GpFhJF29r.css

A.bootstrap.min.css,qver=4.3.1.pagespeed.cf.5GpFhJF29r.css

40 ms

A.main.min.css,qver=1.18.pagespeed.cf.7coPmLi0XZ.css

A.main.min.css,qver=1.18.pagespeed.cf.7coPmLi0XZ.css

30 ms

A.font-awesome.min.css,qver=4.3.1.pagespeed.cf.HpcIsdYD5q.css

A.font-awesome.min.css,qver=4.3.1.pagespeed.cf.HpcIsdYD5q.css

33 ms

A.flaticon.css,qver=4.3.1.pagespeed.cf.QMx82AYjzl.css

A.flaticon.css,qver=4.3.1.pagespeed.cf.QMx82AYjzl.css

34 ms

A.stylesheet.css,qver=4.3.1.pagespeed.cf.ctZ57jBo-h.css

A.stylesheet.css,qver=4.3.1.pagespeed.cf.ctZ57jBo-h.css

32 ms

A.jquery.bxslider.css,qver=4.3.1.pagespeed.cf.asPWbFADP6.css

A.jquery.bxslider.css,qver=4.3.1.pagespeed.cf.asPWbFADP6.css

47 ms

shiftnav.min.css

shiftnav.min.css

47 ms

A.prettyPhoto.css,qver=1.1.4.pagespeed.cf.oxZKt2BwnX.css

A.prettyPhoto.css,qver=1.1.4.pagespeed.cf.oxZKt2BwnX.css

46 ms

A.font-awesome.min.css,qver=1.3.0.2.pagespeed.cf.RkZZMp5rvJ.css

A.font-awesome.min.css,qver=1.3.0.2.pagespeed.cf.RkZZMp5rvJ.css

42 ms

A.standard-dark.css,qver=1.3.0.2.pagespeed.cf.OEJYjk04n0.css

A.standard-dark.css,qver=1.3.0.2.pagespeed.cf.OEJYjk04n0.css

49 ms

A.jquery.fancybox-1.3.4.css,qver=1.1.4.pagespeed.cf.ZzaYQ0mAoW.css

A.jquery.fancybox-1.3.4.css,qver=1.1.4.pagespeed.cf.ZzaYQ0mAoW.css

48 ms

A.tabby.css,qver=1.2.2.pagespeed.cf.9fJafDQeoP.css

A.tabby.css,qver=1.2.2.pagespeed.cf.9fJafDQeoP.css

57 ms

formreset.min.css

formreset.min.css

51 ms

A.formsmain.min.css,qver=1.9.14.pagespeed.cf.0WqioNiK4i.css

A.formsmain.min.css,qver=1.9.14.pagespeed.cf.0WqioNiK4i.css

53 ms

readyclass.min.css

readyclass.min.css

52 ms

browsers.min.css

browsers.min.css

55 ms

sdk.js

sdk.js

61 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

82 ms

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_plugins,_easy-video-player,_lib,_flowplayer.min.js,qver==4.3.1+wp-content,_themes,_homejunction,_assets,_js,_jquery.bxslider.min.js,qver==4.1.2+wp-content,_themes,_homejunction,_assets,_js,_product_page_init.js,qver==1.0.0.pagespeed.jc.0Xcx0Ov1a-.js

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_plugins,_easy-video-player,_lib,_flowplayer.min.js,qver==4.3.1+wp-content,_themes,_homejunction,_assets,_js,_jquery.bxslider.min.js,qver==4.1.2+wp-content,_themes,_homejunction,_assets,_js,_product_page_init.js,qver==1.0.0.pagespeed.jc.0Xcx0Ov1a-.js

85 ms

bootstrap.min.js,qver=3.3.4.pagespeed.jm.pqJ7fDhaN6.js

bootstrap.min.js,qver=3.3.4.pagespeed.jm.pqJ7fDhaN6.js

79 ms

cycle.js,qver=1.7.pagespeed.jm.HRN2jA5yWT.js

cycle.js,qver=1.7.pagespeed.jm.HRN2jA5yWT.js

80 ms

jquery.prettyPhoto.js,qver=1.1.4.pagespeed.jm.GgHqBAATyP.js

jquery.prettyPhoto.js,qver=1.1.4.pagespeed.jm.GgHqBAATyP.js

78 ms

shiftnav.min.js,qver=1.3.0.2.pagespeed.jm.LVKKQdgnue.js

shiftnav.min.js,qver=1.3.0.2.pagespeed.jm.LVKKQdgnue.js

80 ms

tabby.js,qver=1.2.2.pagespeed.jm.nGjb7QiWfh.js

tabby.js,qver=1.2.2.pagespeed.jm.nGjb7QiWfh.js

80 ms

jquery.json.js,qver=1.9.14.pagespeed.jm.Eo1GkmTOIf.js

jquery.json.js,qver=1.9.14.pagespeed.jm.Eo1GkmTOIf.js

81 ms

gravityforms,_js,_gravityforms.min.js,qver==1.9.14+easy-fancybox,_fancybox,_jquery.fancybox-1.3.7.js,qver==1.5.7+easy-fancybox,_jquery.easing.pack.js,qver==1.3+easy-fancybox,_jquery.mousewheel.min.js,qver==3.1.12.pagespeed.jc.Gf4hXWzvFh.js

gravityforms,_js,_gravityforms.min.js,qver==1.9.14+easy-fancybox,_fancybox,_jquery.fancybox-1.3.7.js,qver==1.5.7+easy-fancybox,_jquery.easing.pack.js,qver==1.3+easy-fancybox,_jquery.mousewheel.min.js,qver==3.1.12.pagespeed.jc.Gf4hXWzvFh.js

82 ms

analytics.js

analytics.js

25 ms

toolbar.js

toolbar.js

19 ms

toolbar.css

toolbar.css

20 ms

collect

collect

155 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

142 ms

gtm.js

gtm.js

125 ms

page.js

page.js

105 ms

xlogo.png.pagespeed.ic.5uU-lYxPTP.png

xlogo.png.pagespeed.ic.5uU-lYxPTP.png

20 ms

xvideo-bg-image.jpg.pagespeed.ic.QfATjU8T5x.jpg

xvideo-bg-image.jpg.pagespeed.ic.QfATjU8T5x.jpg

161 ms

xlogo-icon.png.pagespeed.ic.zdJNNNFotr.png

xlogo-icon.png.pagespeed.ic.zdJNNNFotr.png

141 ms

xhj-arrow-right.png.pagespeed.ic.4_2E6pQSm8.png

xhj-arrow-right.png.pagespeed.ic.4_2E6pQSm8.png

142 ms

xpar_bg_img.jpg.pagespeed.ic.VAYzcaQBxV.jpg

xpar_bg_img.jpg.pagespeed.ic.VAYzcaQBxV.jpg

182 ms

160x160xJohn-Cordiera-235x235.jpg.pagespeed.ic.rBX1BcLI1Y.jpg

160x160xJohn-Cordiera-235x235.jpg.pagespeed.ic.rBX1BcLI1Y.jpg

137 ms

160x160xAriana-Gillette-235x235.jpg.pagespeed.ic.kWlTxKtKUi.jpg

160x160xAriana-Gillette-235x235.jpg.pagespeed.ic.kWlTxKtKUi.jpg

138 ms

160x160xKameron-Wildfong.jpg.pagespeed.ic.R-HCupmzPu.jpg

160x160xKameron-Wildfong.jpg.pagespeed.ic.R-HCupmzPu.jpg

140 ms

xfooter_bg.png.pagespeed.ic.-AQdFmskRb.png

xfooter_bg.png.pagespeed.ic.-AQdFmskRb.png

147 ms

xlogo_white.png.pagespeed.ic.bgbxpDvMxs.png

xlogo_white.png.pagespeed.ic.bgbxpDvMxs.png

147 ms

logo_white.png

logo_white.png

146 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

146 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

179 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

197 ms

proximanova-bold-webfont.woff

proximanova-bold-webfont.woff

179 ms

flaticon.woff

flaticon.woff

178 ms

proximanova-regularitalic-webfont.woff

proximanova-regularitalic-webfont.woff

178 ms

collect

collect

148 ms

sm13.html

sm13.html

77 ms

collect

collect

24 ms

icons.15.svg.css

icons.15.svg.css

66 ms

ga-audiences

ga-audiences

80 ms

ga-audiences

ga-audiences

66 ms

ga.js

ga.js

65 ms

__utm.gif

__utm.gif

26 ms

Accessibility Review

spatialmatch.com accessibility score

80

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

spatialmatch.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

spatialmatch.com SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Spatialmatch.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 Spatialmatch.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

spatialmatch.com

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