Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

royallepage.com

Canada Real Estate Listings and Homes for Sale | Royal LePage Real Estate

Page Load Speed

2.5 sec in total

First Response

194 ms

Resources Loaded

1.7 sec

Page Rendered

629 ms

About Website

Click here to check amazing Royal Le Page content. Otherwise, check out these important facts you probably never knew about royallepage.com

Get expert advice on buying and selling a house, and search Canadian real estate listings. View homes and cottages for sale from Royal LePage Canada.

Visit royallepage.com

Key Findings

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

Performance Metrics

royallepage.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.275

44/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

royallepage.com

194 ms

117 ms

common.css

77 ms

home.css

115 ms

js

111 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Royallepage.com, 47% (26 requests) were made to Storage.googleapis.com and 11% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (571 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.9 kB (21%)

Content Size

1.1 MB

After Optimization

876.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Royallepage.com main page is 1.1 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. Javascripts take 736.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 186.8 kB

  • Original 268.4 kB
  • After minification 268.4 kB
  • After compression 81.6 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 186.8 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 2.4 kB

  • Original 48.0 kB
  • After minification 45.6 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. Royal Le Page images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 38.7 kB

  • Original 736.9 kB
  • After minification 736.9 kB
  • After compression 698.2 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

-0%

Potential reduce by 1 B

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

Requests Breakdown

Number of requests can be reduced by 38 (78%)

Requests Now

49

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

royallepage.com accessibility score

85

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

royallepage.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

SEO Factors

royallepage.com SEO score

82

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

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

High

Tap targets are not sized appropriately

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

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