Tools & Wizards About Us
icx.ca screenshot

Report Summary

  • 0

    Performance

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 0

    Best Practices

  • 67

    SEO

    Google-friendlier than
    25% of websites

icx.ca

Page Load Speed

2.7 sec in total

First Response

80 ms

Resources Loaded

2.2 sec

Page Rendered

417 ms

icx.ca screenshot

About Website

Click here to check amazing Icx content for Canada. Otherwise, check out these important facts you probably never knew about icx.ca

Guided by your local REALTOR®, find your next home or commercial property on Canada's most comprehensive list of Canadian residential and commercial properties.

Visit icx.ca

Key Findings

We analyzed Icx.ca page load time and found that the first response time was 80 ms and then it took 2.7 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

icx.ca performance score

0

Network Requests Diagram

icx.ca

80 ms

www.realtor.ca

303 ms

ga.js

134 ms

jquery.min.js

106 ms

jquery-ui.min.js

134 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Icx.ca, 78% (68 requests) were made to Realtor.ca and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Realtor.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (58%)

Content Size

2.0 MB

After Optimization

838.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Icx.ca 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. 70% of websites need less resources to load. Images take 791.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 402.7 kB

  • Original 481.4 kB
  • After minification 445.8 kB
  • After compression 78.7 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 402.7 kB or 84% of the original size.

Image Optimization

-31%

Potential reduce by 247.0 kB

  • Original 791.2 kB
  • After minification 544.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. Obviously, Icx needs image optimization as it can save up to 247.0 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 302.8 kB

  • Original 472.6 kB
  • After minification 472.6 kB
  • After compression 169.9 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 302.8 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 202.7 kB

  • Original 248.0 kB
  • After minification 248.0 kB
  • After compression 45.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. Icx.ca needs all CSS files to be minified and compressed as it can save up to 202.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (44%)

Requests Now

80

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

icx.ca

icx.ca

80 ms

www.realtor.ca

www.realtor.ca

303 ms

ga.js

ga.js

134 ms

jquery.min.js

jquery.min.js

106 ms

jquery-ui.min.js

jquery-ui.min.js

134 ms

api.js

api.js

81 ms

gigya.js

gigya.js

129 ms

gigyaPlugins.validation.js

gigyaPlugins.validation.js

212 ms

gigyaPlugins.js

gigyaPlugins.js

216 ms

jquery.lightbox_me_old.js

jquery.lightbox_me_old.js

127 ms

jquery-idleTimeout.js

jquery-idleTimeout.js

129 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

127 ms

slick.min.js

slick.min.js

211 ms

jquery-ui-1.8.23.custom.css

jquery-ui-1.8.23.custom.css

164 ms

Realtor.css

Realtor.css

189 ms

default.css

default.css

163 ms

jquery.qtip.min.css

jquery.qtip.min.css

163 ms

smoothDivScroll.css

smoothDivScroll.css

163 ms

slick-theme.css

slick-theme.css

164 ms

ScriptResource.axd

ScriptResource.axd

277 ms

__utm.gif

__utm.gif

33 ms

recaptcha__en.js

recaptcha__en.js

94 ms

jquery.ui.datepicker-en-CA.js

jquery.ui.datepicker-en-CA.js

52 ms

logo_beta2.png

logo_beta2.png

36 ms

close_dialog.png

close_dialog.png

35 ms

header_favourite_empty.png

header_favourite_empty.png

65 ms

header_compare_empty.png

header_compare_empty.png

65 ms

search_white.png

search_white.png

65 ms

loading.gif

loading.gif

82 ms

silh-white.png

silh-white.png

82 ms

silh-white-in.png

silh-white-in.png

81 ms

heart-icon.png

heart-icon.png

81 ms

search-icon.png

search-icon.png

81 ms

notes.png

notes.png

80 ms

exclaim-icon.png

exclaim-icon.png

142 ms

arrow-promo.png

arrow-promo.png

145 ms

close_dialog.png

close_dialog.png

144 ms

map_header_banner2.png

map_header_banner2.png

143 ms

loading_map.gif

loading_map.gif

143 ms

NR-slide1.jpg

NR-slide1.jpg

222 ms

CREA_RoadMap_Blue_03KF.png

CREA_RoadMap_Blue_03KF.png

217 ms

residential_banner.jpg

residential_banner.jpg

298 ms

bed.png

bed.png

217 ms

bath.png

bath.png

218 ms

calendar2.png

calendar2.png

217 ms

favourites_unselected2.png

favourites_unselected2.png

221 ms

favourite_step2.png

favourite_step2.png

219 ms

favourite_step3.png

favourite_step3.png

218 ms

compare_unselected2.png

compare_unselected2.png

220 ms

compare_step2.png

compare_step2.png

220 ms

compare_step3.png

compare_step3.png

223 ms

listings_in_my_area.jpg

listings_in_my_area.jpg

221 ms

youtube_play.png

youtube_play.png

221 ms

NR-tout.jpg

NR-tout.jpg

624 ms

listing_demographics.png

listing_demographics.png

680 ms

apple_app_store_en.png

apple_app_store_en.png

626 ms

google_play_en.png

google_play_en.png

627 ms

gtm.js

gtm.js

139 ms

home.png

home.png

626 ms

realtor.png

realtor.png

599 ms

loading.gif

loading.gif

577 ms

ProximaNova-Reg-webfont.woff

ProximaNova-Reg-webfont.woff

568 ms

ProximaNova-Bold-webfont.woff

ProximaNova-Bold-webfont.woff

568 ms

client.js

client.js

146 ms

hdr_glb.jpg

hdr_glb.jpg

559 ms

dropkick_arrow_black_dwn.png

dropkick_arrow_black_dwn.png

496 ms

androidHomeFrame.jpg

androidHomeFrame.jpg

530 ms

green-realtor-fade3.jpg

green-realtor-fade3.jpg

531 ms

green-realtor-fade9.jpg

green-realtor-fade9.jpg

531 ms

bg-findrealtor.jpg

bg-findrealtor.jpg

530 ms

bg-mobile.jpg

bg-mobile.jpg

1337 ms

iframe_api

iframe_api

463 ms

dropkick_arrow_black_dwn.png

dropkick_arrow_black_dwn.png

465 ms

ForoReg-webfont.woff

ForoReg-webfont.woff

448 ms

ForoIta-webfont.woff

ForoIta-webfont.woff

484 ms

beacon.js

beacon.js

434 ms

analytics.js

analytics.js

433 ms

e.targetfuel.com

e.targetfuel.com

407 ms

GetAllResources

GetAllResources

154 ms

GetAllResources

GetAllResources

178 ms

3PCTest.html

3PCTest.html

61 ms

ajax-loader.gif

ajax-loader.gif

96 ms

slick.woff

slick.woff

82 ms

www-widgetapi.js

www-widgetapi.js

142 ms

linkid.js

linkid.js

41 ms

collect

collect

17 ms

collect

collect

78 ms

Accessibility Review

icx.ca accessibility score

69

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

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

SEO Factors

icx.ca SEO score

67

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Icx.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Icx.ca 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

icx.ca

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