Tools & Wizards About Us
hayesteam.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hayesteam.com

Kyle & Michelle Hayes - Hayes Team LLC www.HayesTeam.com

Page Load Speed

5.9 sec in total

First Response

165 ms

Resources Loaded

5 sec

Page Rendered

707 ms

hayesteam.com screenshot

About Website

Visit hayesteam.com now to see the best up-to-date Hayes Team content and also check out these interesting facts you probably never knew about hayesteam.com

hayesteam.com - Michelle Hayes, Principal Broker, REALTOR - Oregon Real Estate

Visit hayesteam.com

Key Findings

We analyzed Hayesteam.com page load time and found that the first response time was 165 ms and then it took 5.7 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

hayesteam.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

hayesteam.com

165 ms

www.hayesteam.com

253 ms

style.css

240 ms

search_widget.css

242 ms

real

266 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 52% of them (34 requests) were addressed to the original Hayesteam.com, 25% (16 requests) were made to Proagentwebsites.com and 18% (12 requests) were made to Photos.rmlsweb.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Photos.rmlsweb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 661.0 kB (7%)

Content Size

9.2 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hayesteam.com main page is 9.2 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. 40% of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 43.2 kB

  • Original 55.1 kB
  • After minification 52.6 kB
  • After compression 11.8 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 43.2 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 547.8 kB

  • Original 8.9 MB
  • After minification 8.3 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. Hayes Team images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 68.1 kB

  • Original 224.4 kB
  • After minification 223.1 kB
  • After compression 156.3 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 68.1 kB or 30% of the original size.

CSS Optimization

-22%

Potential reduce by 1.9 kB

  • Original 8.9 kB
  • After minification 8.9 kB
  • After compression 6.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. Hayesteam.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (22%)

Requests Now

63

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hayesteam.com

hayesteam.com

165 ms

www.hayesteam.com

www.hayesteam.com

253 ms

style.css

style.css

240 ms

search_widget.css

search_widget.css

242 ms

real

real

266 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

273 ms

jquery-1.7.js

jquery-1.7.js

341 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

408 ms

real

real

339 ms

mainmenu

mainmenu

308 ms

real

real

266 ms

real

real

574 ms

real

real

505 ms

socialicons

socialicons

531 ms

real

real

539 ms

headerLogo3.png

headerLogo3.png

255 ms

zoom-in.png

zoom-in.png

263 ms

star.png

star.png

329 ms

info.png

info.png

345 ms

agentWelcome2.png

agentWelcome2.png

616 ms

welcome_header.png

welcome_header.png

521 ms

hameValue.png

hameValue.png

603 ms

phone.png

phone.png

617 ms

loansButton.png

loansButton.png

693 ms

ehlogo.jpg

ehlogo.jpg

585 ms

rmls_large.jpg

rmls_large.jpg

261 ms

lock.png

lock.png

748 ms

page1.jpg

page1.jpg

989 ms

page2.jpg

page2.jpg

1007 ms

page3.jpg

page3.jpg

1012 ms

page4.jpg

page4.jpg

1067 ms

Shutterstock%20original.jpg

Shutterstock%20original.jpg

1031 ms

downarrow.png

downarrow.png

1080 ms

smallmap.png

smallmap.png

367 ms

magsmall.png

magsmall.png

365 ms

ui-bg_inset-soft_25_ffffff_1x100.png

ui-bg_inset-soft_25_ffffff_1x100.png

248 ms

24084021-1.jpg

24084021-1.jpg

1952 ms

bgLinks2.jpg

bgLinks2.jpg

1252 ms

24438433-1.jpg

24438433-1.jpg

1891 ms

24699881-1.jpg

24699881-1.jpg

1991 ms

24697950-1.jpg

24697950-1.jpg

2011 ms

24697939-1.jpg

24697939-1.jpg

2063 ms

24697709-1.jpg

24697709-1.jpg

1908 ms

24696346-1.jpg

24696346-1.jpg

2879 ms

24695998-1.jpg

24695998-1.jpg

3010 ms

24693765-1.jpg

24693765-1.jpg

3986 ms

24693681-1.jpg

24693681-1.jpg

3012 ms

24693221-1.jpg

24693221-1.jpg

2975 ms

24693048-1.jpg

24693048-1.jpg

3384 ms

rmls_small.jpg

rmls_small.jpg

233 ms

Hayes_Team_Blurred_background.jpg

Hayes_Team_Blurred_background.jpg

1084 ms

facebook.gif

facebook.gif

238 ms

linkedin.gif

linkedin.gif

333 ms

twitter.gif

twitter.gif

344 ms

youtube.gif

youtube.gif

449 ms

blog.gif

blog.gif

460 ms

igram.gif

igram.gif

464 ms

broker2.jpg

broker2.jpg

1138 ms

real

real

1115 ms

real

real

1159 ms

ui-bg_glass_20_555555_1x400.png

ui-bg_glass_20_555555_1x400.png

454 ms

analytics.js

analytics.js

21 ms

widget.js

widget.js

170 ms

spacer.gif

spacer.gif

61 ms

widget_app_base_1731405450658.js

widget_app_base_1731405450658.js

16 ms

Accessibility Review

hayesteam.com accessibility score

89

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

hayesteam.com best practices score

83

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

Page has valid source maps

SEO Factors

hayesteam.com SEO score

86

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hayesteam.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hayesteam.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

hayesteam.com

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