Tools & Wizards About Us
m.chase.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

m.chase.com

Credit Card, Mortgage, Banking, Auto | Chase Online | Chase.com

Page Load Speed

1.3 sec in total

First Response

59 ms

Resources Loaded

1.1 sec

Page Rendered

105 ms

m.chase.com screenshot

About Website

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

Chase online; credit cards, mortgages, commercial banking, auto loans, investing & retirement planning, checking and business banking.

Visit m.chase.com

Key Findings

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

Performance Metrics

m.chase.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.855

4/100

15%

TTI (Time to Interactive)

Value5.3 s

72/100

10%

Network Requests Diagram

www.chase.com

59 ms

home.min.css

11 ms

jquery.min.js

21 ms

require.min.js

31 ms

Reporting.js

60 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.chase.com, 8% (6 requests) were made to Asset.chase.com and 1% (1 request) were made to S2.go-mpulse.net. The less responsive or slowest element that took the longest time to load (562 ms) relates to the external source Chase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 593.0 kB (52%)

Content Size

1.1 MB

After Optimization

552.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.chase.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. 50% of websites need less resources to load. Javascripts take 815.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 116.2 kB

  • Original 133.6 kB
  • After minification 109.7 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 23.9 kB, which is 18% 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 116.2 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 129 B

  • Original 1.8 kB
  • After minification 1.7 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 Chase images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 476.7 kB

  • Original 815.2 kB
  • After minification 665.4 kB
  • After compression 338.5 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 476.7 kB or 58% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 195.2 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.

Requests Breakdown

Number of requests can be reduced by 61 (91%)

Requests Now

67

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.chase.com

www.chase.com

59 ms

home.min.css

home.min.css

11 ms

jquery.min.js

jquery.min.js

21 ms

require.min.js

require.min.js

31 ms

Reporting.js

Reporting.js

60 ms

index.min.js

index.min.js

30 ms

9GMXG-P9JCU-47Q2G-PYE6D-MR9ML

9GMXG-P9JCU-47Q2G-PYE6D-MR9ML

123 ms

ie_alert.png

ie_alert.png

52 ms

EHL-Slice.png

EHL-Slice.png

49 ms

main.js

main.js

47 ms

marketing-loader.js

marketing-loader.js

76 ms

opensans.woff

opensans.woff

73 ms

opensans-light.woff

opensans-light.woff

135 ms

opensans-semibold.woff

opensans-semibold.woff

87 ms

opensans-bold.woff

opensans-bold.woff

84 ms

opensans-extrabold.woff

opensans-extrabold.woff

96 ms

icomoon.ttf

icomoon.ttf

45 ms

adobetargetinit.js

adobetargetinit.js

64 ms

adobetarget-page-mbox.js

adobetarget-page-mbox.js

186 ms

dynamic-page-creation.js

dynamic-page-creation.js

168 ms

env.js

env.js

56 ms

country-banner.js

country-banner.js

263 ms

header-navigation.js

header-navigation.js

42 ms

sidemenu-navigation.js

sidemenu-navigation.js

80 ms

browser-message.js

browser-message.js

145 ms

speedbump.js

speedbump.js

135 ms

scroll-event-tracker.js

scroll-event-tracker.js

112 ms

signin.js

signin.js

174 ms

signin-btn.js

signin-btn.js

169 ms

ada.js

ada.js

304 ms

language.js

language.js

210 ms

persona.js

persona.js

260 ms

cookie.js

cookie.js

228 ms

xfs.js

xfs.js

395 ms

utils.js

utils.js

249 ms

info-banner.js

info-banner.js

338 ms

global-overlay.js

global-overlay.js

418 ms

survey.js

survey.js

292 ms

jquery.cookie.js

jquery.cookie.js

390 ms

cookie.chase-campaign.js

cookie.chase-campaign.js

316 ms

config.json

config.json

71 ms

slotplacement.min.js

slotplacement.min.js

116 ms

clientconfig.js

clientconfig.js

262 ms

platform.js

platform.js

334 ms

accordian.js

accordian.js

406 ms

header.js

header.js

306 ms

sticky-footer.js

sticky-footer.js

322 ms

personalized-links.js

personalized-links.js

341 ms

weblink-disclosure.js

weblink-disclosure.js

422 ms

roostifylinks.js

roostifylinks.js

503 ms

addsourcecode.js

addsourcecode.js

426 ms

sub-header.js

sub-header.js

359 ms

disclosure.js

disclosure.js

439 ms

mboxcomp.js

mboxcomp.js

392 ms

intro-hero.js

intro-hero.js

408 ms

sweeps-table.js

sweeps-table.js

459 ms

secondary-nav-subheader.js

secondary-nav-subheader.js

556 ms

tabs.js

tabs.js

562 ms

jquery.appear.js

jquery.appear.js

491 ms

jquery.isonscreen.min.js

jquery.isonscreen.min.js

420 ms

timeout-message.js

timeout-message.js

464 ms

cpo-utilities.js

cpo-utilities.js

393 ms

sendMessageClient.js

sendMessageClient.js

436 ms

has.js

has.js

493 ms

sidemenu.js

sidemenu.js

327 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

257 ms

iscroll-5.1.3.min.js

iscroll-5.1.3.min.js

241 ms

anchorlink.js

anchorlink.js

243 ms

buckets.js

buckets.js

290 ms

left-nav.js

left-nav.js

223 ms

modal.js

modal.js

212 ms

video.js

video.js

235 ms

transcript.js

transcript.js

235 ms

module.html

module.html

13 ms

Accessibility Review

m.chase.com accessibility score

100

Accessibility Issues

Best Practices

m.chase.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

m.chase.com SEO score

92

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.chase.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.chase.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.chase.com

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