Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

yodlee.com

Envestnet | Yodlee | A Leader in Data Aggregation

Page Load Speed

1.9 sec in total

First Response

51 ms

Resources Loaded

1.6 sec

Page Rendered

224 ms

About Website

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

Envestnet | Yodlee has proudly fueled innovation for financial institutions and fintech companies since 1999 through data, APIs, and FinApps. Learn more about our products and solutions.

Visit yodlee.com

Key Findings

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

Performance Metrics

yodlee.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value3,120 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.107

88/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

www.yodlee.com

51 ms

gtm.js

94 ms

css_H2zsuwWHj1ENWPOCcfNwJl-ncOAE_IeVKkbKup33imA.hyrwqHi-M4jKMIhZvne8wtfaZUOSIkvr-QwnbnXVheI.css

13 ms

css_97htjIvQ15V1EfeTASftshiMIzLS36LIXVDogWwnlWQ.ei8lI1zNN85Mjr1Ebhv1CSzQqv7N2tZ0GrrgspukWKE.css

30 ms

css_73nz4faxDJu-1n9bzB7HHGFw54tKe4MjoN6CazQkWOM.sf70ZqLzd0Ds3uObwnZZE8sspsOMslYZaMD5jr-iJas.css

30 ms

Our browser made a total of 179 requests to load all elements on the main page. We found that 70% of them (125 requests) were addressed to the original Yodlee.com, 3% (6 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (700 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.9 kB (18%)

Content Size

1.0 MB

After Optimization

843.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yodlee.com main page is 1.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 472.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 106.9 kB

  • Original 133.6 kB
  • After minification 114.7 kB
  • After compression 26.6 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 18.9 kB, which is 14% 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 106.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 5.5 kB

  • Original 320.0 kB
  • After minification 314.5 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. Yodlee images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 70.3 kB

  • Original 472.2 kB
  • After minification 471.5 kB
  • After compression 401.9 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 70.3 kB or 15% of the original size.

CSS Optimization

-5%

Potential reduce by 5.1 kB

  • Original 105.1 kB
  • After minification 103.4 kB
  • After compression 100.0 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. Yodlee.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 146 (86%)

Requests Now

170

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

yodlee.com accessibility score

75

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-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

yodlee.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yodlee.com SEO score

86

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

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

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