Tools & Wizards About Us

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

legacy.property

For Top-Tier Real Estate in Central Oregon | Legacy Realty LLC

Page Load Speed

5.5 sec in total

First Response

89 ms

Resources Loaded

2.9 sec

Page Rendered

2.5 sec

About Website

Click here to check amazing Legacy content. Otherwise, check out these important facts you probably never knew about legacy.property

Explore starter homes, investment property, vast estates, and some of the best real estate in Central Oregon on Legacy Realty's website. Call for details.

Visit legacy.property

Key Findings

We analyzed Legacy.property page load time and found that the first response time was 89 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

legacy.property performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value3,650 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

legacy.property

89 ms

legacy.property

188 ms

picturefill.min.js

109 ms

dsidx-icons.css

201 ms

combo-css

537 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 67% of them (74 requests) were addressed to the original Legacy.property, 17% (19 requests) were made to Resources.agentimage.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Legacy.property.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.6 kB (8%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Legacy.property main page is 2.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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.7 kB

  • Original 105.0 kB
  • After minification 105.0 kB
  • After compression 18.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 86.7 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 63.7 kB

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

JavaScript Optimization

-3%

Potential reduce by 16.0 kB

  • Original 543.9 kB
  • After minification 543.9 kB
  • After compression 528.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

-24%

Potential reduce by 27.3 kB

  • Original 112.8 kB
  • After minification 112.8 kB
  • After compression 85.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. Legacy.property needs all CSS files to be minified and compressed as it can save up to 27.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (63%)

Requests Now

101

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

legacy.property 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

legacy.property best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

legacy.property SEO score

84

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

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 Legacy.property 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 Legacy.property 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 data is detected on the main page of Legacy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: