Tools & Wizards About Us
mortgagegrapevine.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

mortgagegrapevine.com

National Mortgage News Homepage | National Mortgage News

Page Load Speed

88.5 sec in total

First Response

109 ms

Resources Loaded

59.3 sec

Page Rendered

29.1 sec

mortgagegrapevine.com screenshot

About Website

Visit mortgagegrapevine.com now to see the best up-to-date Mortgage Grapevine content for United States and also check out these interesting facts you probably never knew about mortgagegrapevine.com

News analysis and perspective from National Mortgage News, an award-winning comprehensive digital resource serving the entire residential mortgage industry.

Visit mortgagegrapevine.com

Key Findings

We analyzed Mortgagegrapevine.com page load time and found that the first response time was 109 ms and then it took 88.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 39 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

mortgagegrapevine.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value4.1 s

78/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value9.0 s

33/100

10%

Network Requests Diagram

mortgagegrapevine.com

109 ms

www.nationalmortgagenews.com

1260 ms

site-nmn.min.1caadf2346465e4ccce43db894a8bdab.gz.css

2616 ms

main.min.938dd07d7c0e46113fa44f616a9406fd.gz.js

4405 ms

chartbeat.js

1873 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mortgagegrapevine.com, 35% (31 requests) were made to Assets.sourcemedia.com and 10% (9 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (33.6 sec) relates to the external source Assets.sourcemedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (54%)

Content Size

4.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 85.4 kB

  • Original 107.2 kB
  • After minification 95.0 kB
  • After compression 21.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. This page needs HTML code to be minified as it can gain 12.2 kB, which is 11% 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 85.4 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 75.9 kB

  • Original 539.7 kB
  • After minification 463.8 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. Obviously, Mortgage Grapevine needs image optimization as it can save up to 75.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 1.2 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 585.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.2 MB or 66% of the original size.

CSS Optimization

-52%

Potential reduce by 919.8 kB

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

Requests Breakdown

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

Requests Now

36

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mortgagegrapevine.com

mortgagegrapevine.com

109 ms

www.nationalmortgagenews.com

www.nationalmortgagenews.com

1260 ms

site-nmn.min.1caadf2346465e4ccce43db894a8bdab.gz.css

site-nmn.min.1caadf2346465e4ccce43db894a8bdab.gz.css

2616 ms

main.min.938dd07d7c0e46113fa44f616a9406fd.gz.js

main.min.938dd07d7c0e46113fa44f616a9406fd.gz.js

4405 ms

chartbeat.js

chartbeat.js

1873 ms

keywee.min.js

keywee.min.js

1851 ms

lio.js

lio.js

1849 ms

dnb_coretag_v3.min.js

dnb_coretag_v3.min.js

1847 ms

chartbeat_mab.js

chartbeat_mab.js

2212 ms

analytics.js

analytics.js

692 ms

f-a.486828a9d32c377e34fb8155422316bd.gz.css

f-a.486828a9d32c377e34fb8155422316bd.gz.css

2984 ms

f-ss.57cb8bdfdc207a5d8f26a447e905f81e.gz.css

f-ss.57cb8bdfdc207a5d8f26a447e905f81e.gz.css

1941 ms

css

css

1601 ms

gpt.js

gpt.js

230 ms

pubads_impl_147.js

pubads_impl_147.js

343 ms

container.html

container.html

1336 ms

analytics.js

analytics.js

9872 ms

sp.js

sp.js

1280 ms

fbevents.js

fbevents.js

9585 ms

w.js

w.js

33352 ms

dpm_c415505dca69be631ca5d391b3ccd2b44b52d017.min.js

dpm_c415505dca69be631ca5d391b3ccd2b44b52d017.min.js

33352 ms

munchkin.js

munchkin.js

33352 ms

i.js

i.js

33418 ms

io.js

io.js

33598 ms

undefined

undefined

33586 ms

33586 ms

nmn-42x349.png

nmn-42x349.png

33586 ms

33273 ms

33273 ms

33273 ms

33534 ms

33535 ms

33535 ms

33535 ms

33535 ms

33584 ms

33584 ms

33585 ms

33585 ms

33624 ms

33391 ms

33391 ms

33390 ms

33390 ms

33391 ms

33391 ms

33154 ms

33153 ms

33202 ms

33186 ms

33186 ms

i

i

25622 ms

2482 ms

qe3Npi2Tc7yiKp7eio7Wi1O8K1NsK1NsK1NsIjNtTM+TNm0PTY+EzOnet8dyqXHjlffIvMH6qmmb8LL6pepv4PlwLTYAAAAAFWHsouAAA=

qe3Npi2Tc7yiKp7eio7Wi1O8K1NsK1NsK1NsIjNtTM+TNm0PTY+EzOnet8dyqXHjlffIvMH6qmmb8LL6pepv4PlwLTYAAAAAFWHsouAAA=

1757 ms

8DbkHZigABVh7JxAAA

8DbkHZigABVh7JxAAA

1476 ms

Gi6r3rP8DAxTebgABVh7PEAAA

Gi6r3rP8DAxTebgABVh7PEAAA

1526 ms

8Nj3lUAAAFWHsmUAAA=

8Nj3lUAAAFWHsmUAAA=

1338 ms

F15UPUz9H4Ec030AAVYezw4AAA==

F15UPUz9H4Ec030AAVYezw4AAA==

1430 ms

wFVq9N8AAAAAVYeyDMAAA==

wFVq9N8AAAAAVYeyDMAAA==

1514 ms

F15UPUz9H+Bc04sAAAAAAVYeySkAAA==

F15UPUz9H+Bc04sAAAAAAVYeySkAAA==

1168 ms

wOFN9ODAAAAAVYeyDIAAA==

wOFN9ODAAAAAVYeyDIAAA==

984 ms

source-media-iconfont.516ee0004fae54f815f97f841363d55d.ttf

source-media-iconfont.516ee0004fae54f815f97f841363d55d.ttf

23825 ms

1703855259870884

1703855259870884

22689 ms

quant.js

quant.js

22706 ms

uwt.js

uwt.js

22705 ms

_track

_track

22469 ms

collect

collect

0 ms

ads

ads

5787 ms

ads

ads

7306 ms

ads

ads

7145 ms

ads

ads

7022 ms

collect

collect

5752 ms

collect

collect

5989 ms

collect

collect

6118 ms

collect

collect

6117 ms

collect

collect

6117 ms

collect

collect

6116 ms

collect

collect

6395 ms

collect

collect

3668 ms

source-media-iconfont.2d4a2a0164a86a71fc4e240dfa3dd9cc.woff

source-media-iconfont.2d4a2a0164a86a71fc4e240dfa3dd9cc.woff

3354 ms

osd.js

osd.js

3213 ms

11954860094640662428

11954860094640662428

847 ms

osd_listener.js

osd_listener.js

914 ms

m_window_focus_non_hydra.js

m_window_focus_non_hydra.js

1625 ms

11823257954216811507

11823257954216811507

1253 ms

11824504123946682137

11824504123946682137

1317 ms

7193104233095237964

7193104233095237964

1312 ms

ga-audiences

ga-audiences

2656 ms

Accessibility Review

mortgagegrapevine.com accessibility score

89

Accessibility Issues

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mortgagegrapevine.com SEO score

92

Search Engine Optimization Advices

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

mortgagegrapevine.com

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