Tools & Wizards About Us
orea.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

orea.com

OREA - Ontario Real Estate Association

Page Load Speed

1.2 sec in total

First Response

66 ms

Resources Loaded

1.1 sec

Page Rendered

54 ms

orea.com screenshot

About Website

Welcome to orea.com homepage info - get ready to check OREA best content for Canada right away, or after learning these important things about orea.com

OREA - Ontario Real Estate Association, supporting Ontario REALTORS® in building stronger communities across the province.

Visit orea.com

Key Findings

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

Performance Metrics

orea.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value6,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.375

28/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

orea.com

66 ms

www.orea.com

253 ms

js

63 ms

gtm.js

139 ms

css2

33 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 65% of them (48 requests) were addressed to the original Orea.com, 7% (5 requests) were made to Gstatic.com and 5% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (366 ms) belongs to the original domain Orea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.7 kB (12%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Orea.com main page is 1.4 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. 75% 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 942.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 138.2 kB

  • Original 166.5 kB
  • After minification 142.8 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 23.8 kB, which is 14% 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 138.2 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 15.8 kB

  • Original 942.9 kB
  • After minification 927.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. OREA images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 239.9 kB
  • After minification 239.9 kB
  • After compression 236.6 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

-5%

Potential reduce by 1.4 kB

  • Original 27.3 kB
  • After minification 27.3 kB
  • After compression 25.9 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. Orea.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

47

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OREA. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

orea.com

orea.com

66 ms

www.orea.com

www.orea.com

253 ms

js

js

63 ms

gtm.js

gtm.js

139 ms

css2

css2

33 ms

head

head

180 ms

head

head

251 ms

orea2022-t.min.css

orea2022-t.min.css

179 ms

header

header

280 ms

api.js

api.js

34 ms

ccRwidget.css

ccRwidget.css

181 ms

ccRwidget.js

ccRwidget.js

182 ms

ga.js

ga.js

28 ms

1036.js

1036.js

39 ms

__utm.gif

__utm.gif

13 ms

www.orea.com.json

www.orea.com.json

14 ms

collect

collect

11 ms

orea-logo.svg

orea-logo.svg

30 ms

recaptcha__en.js

recaptcha__en.js

33 ms

eye-hide.svg

eye-hide.svg

27 ms

eye-show.svg

eye-show.svg

25 ms

Apr-12-2024.webp

Apr-12-2024.webp

95 ms

Apr-10-homepage.jpg

Apr-10-homepage.jpg

76 ms

Building-More-Homes-Faster.webp

Building-More-Homes-Faster.webp

78 ms

Ford%20Government%20Housing%20Announcement.webp

Ford%20Government%20Housing%20Announcement.webp

74 ms

Tops%20of%20Houses_GettyImages-474796264.jpg

Tops%20of%20Houses_GettyImages-474796264.jpg

155 ms

06-March.jpg

06-March.jpg

111 ms

2023%20Annual%20Report%20cover.jpg

2023%20Annual%20Report%20cover.jpg

175 ms

reality24-home.webp

reality24-home.webp

175 ms

Housing-Supply-advocacy.webp

Housing-Supply-advocacy.webp

210 ms

Tim-Hudak-Swanepoel.jpg

Tim-Hudak-Swanepoel.jpg

175 ms

Advocacy-ABACUS-Housing-Affordability-Wave-4.jpg

Advocacy-ABACUS-Housing-Affordability-Wave-4.jpg

176 ms

Parliament-Hill.jpg

Parliament-Hill.jpg

176 ms

Power%20House%20410.jpg

Power%20House%20410.jpg

211 ms

queens-park-arial-sm.jpg

queens-park-arial-sm.jpg

212 ms

Advocacy-carousel-Immigration-Report.jpg

Advocacy-carousel-Immigration-Report.jpg

211 ms

hp-press-sept-20-2023.jpg

hp-press-sept-20-2023.jpg

212 ms

hp-press-release-September-15.jpg

hp-press-release-September-15.jpg

214 ms

hp-press-release-September-14.jpg

hp-press-release-September-14.jpg

232 ms

hp-media-july-2023.jpg

hp-media-july-2023.jpg

214 ms

ORWP-press-release-hp.jpg

ORWP-press-release-hp.jpg

214 ms

5-June-2023.webp

5-June-2023.webp

234 ms

24-May-2023-PR.webp

24-May-2023-PR.webp

234 ms

HP-Apr6-2023.webp

HP-Apr6-2023.webp

282 ms

5-April-2023.webp

5-April-2023.webp

283 ms

March-31-2023-HP.webp

March-31-2023-HP.webp

284 ms

March-29-2023-Sm.jpg

March-29-2023-Sm.jpg

285 ms

QueensPark.webp

QueensPark.webp

286 ms

Queens-Park-Spring.webp

Queens-Park-Spring.webp

287 ms

Meet-Your-New-President-2023-409x400.webp

Meet-Your-New-President-2023-409x400.webp

315 ms

2023-Forms-Revisions.webp

2023-Forms-Revisions.webp

315 ms

increase-housing-supply.webp

increase-housing-supply.webp

324 ms

Saving-the-Dream.webp

Saving-the-Dream.webp

347 ms

Open-Bidding-Small.webp

Open-Bidding-Small.webp

347 ms

app.js

app.js

149 ms

Election-Spotlights-Affordability.webp

Election-Spotlights-Affordability.webp

335 ms

Transparency-to-Real-Estate-Offer-Process.webp

Transparency-to-Real-Estate-Offer-Process.webp

366 ms

home-forms.webp

home-forms.webp

365 ms

anchor

anchor

38 ms

jqg4lxhwvi

jqg4lxhwvi

102 ms

Advocate-Queens-Park.webp

Advocate-Queens-Park.webp

310 ms

orea-icon-lockup.svg

orea-icon-lockup.svg

310 ms

styles__ltr.css

styles__ltr.css

5 ms

recaptcha__en.js

recaptcha__en.js

15 ms

tKcPQSh2okjZHiZ2jIssRExVWo45mlVHOakavsOpwK4.js

tKcPQSh2okjZHiZ2jIssRExVWo45mlVHOakavsOpwK4.js

37 ms

webworker.js

webworker.js

70 ms

logo_48.png

logo_48.png

27 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

79 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

79 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

80 ms

clarity.js

clarity.js

29 ms

recaptcha__en.js

recaptcha__en.js

21 ms

orea2022-m.min.css

orea2022-m.min.css

29 ms

c.gif

c.gif

7 ms

Accessibility Review

orea.com accessibility score

98

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

Links do not have a discernible name

Best Practices

orea.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

orea.com SEO score

92

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

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

orea.com

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