Tools & Wizards About Us
m.huff.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

m.huff.com

Huff Realty, Real Estate in Cincinnati, Northern Kentucky, Indiana

Page Load Speed

6.2 sec in total

First Response

559 ms

Resources Loaded

4.1 sec

Page Rendered

1.5 sec

m.huff.com screenshot

About Website

Visit m.huff.com now to see the best up-to-date M Huff content for United States and also check out these interesting facts you probably never knew about m.huff.com

Providing real estate services in Cincinnati Ohio, Northern Kentucky, Dayton Ohio and Southeast Indiana

Visit m.huff.com

Key Findings

We analyzed M.huff.com page load time and found that the first response time was 559 ms and then it took 5.6 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

m.huff.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value7,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

www.huff.com

559 ms

analytics.js

109 ms

liveby.js

202 ms

77344dd828869e8c289de0f.js

195 ms

jquery-1.8.3.min.js

172 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.huff.com, 13% (6 requests) were made to Content.mediastg.net and 11% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (873 ms) relates to the external source Huff.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (86%)

Content Size

1.9 MB

After Optimization

275.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.huff.com main page is 1.9 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. 60% of websites need less resources to load. CSS take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 43.5 kB

  • Original 54.9 kB
  • After minification 49.7 kB
  • After compression 11.4 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.5 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 1.7 kB

  • Original 39.8 kB
  • After minification 38.0 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. M Huff images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 15.4 kB

  • Original 66.2 kB
  • After minification 66.2 kB
  • After compression 50.8 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 15.4 kB or 23% of the original size.

CSS Optimization

-90%

Potential reduce by 1.6 MB

  • Original 1.8 MB
  • After minification 1.6 MB
  • After compression 175.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. M.huff.com needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (75%)

Requests Now

40

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.huff.com

www.huff.com

559 ms

analytics.js

analytics.js

109 ms

liveby.js

liveby.js

202 ms

77344dd828869e8c289de0f.js

77344dd828869e8c289de0f.js

195 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

172 ms

jquery-ui.min.js

jquery-ui.min.js

221 ms

reliance.jsx

reliance.jsx

103 ms

site.jsx

site.jsx

272 ms

global-branding.min.css

global-branding.min.css

465 ms

slick.min.css

slick.min.css

188 ms

slick-theme.min.css

slick-theme.min.css

253 ms

huff1.css

huff1.css

873 ms

596 ms

css-vars-polyfill.js

css-vars-polyfill.js

319 ms

js.cookie.min.js

js.cookie.min.js

248 ms

slick.min.js

slick.min.js

249 ms

intersection-observer.js

intersection-observer.js

322 ms

lazyload.min.js

lazyload.min.js

321 ms

cms.js

cms.js

383 ms

huff1-app.js

huff1-app.js

388 ms

collect

collect

38 ms

reliance.event.js

reliance.event.js

148 ms

reliance.browser.js

reliance.browser.js

208 ms

css

css

151 ms

css

css

204 ms

css

css

218 ms

7450e409-aa32-4af4-85f7-a32b1338eb4a.png

7450e409-aa32-4af4-85f7-a32b1338eb4a.png

226 ms

e16c9085-d2ea-46a8-b747-aed246171100.png

e16c9085-d2ea-46a8-b747-aed246171100.png

234 ms

480b6fdb-fc42-4bad-a519-4da71f7a26d1.jpg

480b6fdb-fc42-4bad-a519-4da71f7a26d1.jpg

250 ms

f35ad46d-02a9-4de9-aa35-2ea0be5da117.png

f35ad46d-02a9-4de9-aa35-2ea0be5da117.png

249 ms

ecc520a0-0f0f-49eb-9d94-c615a66264ea.png

ecc520a0-0f0f-49eb-9d94-c615a66264ea.png

247 ms

180d4bb9-9b02-41ea-9478-e8b224771016.jpg

180d4bb9-9b02-41ea-9478-e8b224771016.jpg

244 ms

fbevents.js

fbevents.js

224 ms

gtm.js

gtm.js

488 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

455 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

465 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

773 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

784 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

784 ms

reliance.controls.SuggestionField.js

reliance.controls.SuggestionField.js

192 ms

reliance.domUtilities.js

reliance.domUtilities.js

189 ms

reliance.xDomainHttpRequest.js

reliance.xDomainHttpRequest.js

196 ms

reliance.common.js

reliance.common.js

188 ms

quicksearch-tags.js

quicksearch-tags.js

172 ms

1065568730198911

1065568730198911

569 ms

Reliance-Network-Icon-Font.ttf

Reliance-Network-Icon-Font.ttf

307 ms

quicksearchredirect.css

quicksearchredirect.css

119 ms

Accessibility Review

m.huff.com accessibility score

93

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-*] attributes do not match their roles

Best Practices

m.huff.com best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

m.huff.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

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 doesn't use 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 M.huff.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 M.huff.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

m.huff.com

Open Graph data is detected on the main page of M Huff. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: