Powered by https://baaed.com ()
examined at : 24-08-06 05:33:28
follow recommendations of this health report to keep your site healthy
Wells Fargo Bank | Financial Services & Online Banking
Your page title does not exceed 60 characters. It's fine.
Committed to the financial health of our customers and communities. Explore bank accounts, loans, mortgages, investing, credit cards & banking services»
Your meta description exceeds 150 characters. It's not good.
appointment, make an appointment, online banking, open account, book appointment, contact, statements, new account, payment, sign up, change password, contact us, enroll, login, create account, account, make payment, my account, change password for login, account summary, enroll account for online access, sign in, mobile banking, password, english, wells fargo, balance, log in, pay bills, register, create an account, sign on, online statements, full site, home, wellsfargo.com, personal, wells fargo online, covid, covid 19 hardship, covid 19 relief, covid-19, covid 19
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Wells | 65 | 2.904 % | No |
Fargo | 65 | 2.904 % | No |
website | 27 | 1.206 % | No |
| 25 | 1.117 % | No |
credit | 20 | 0.894 % | Yes |
account | 19 | 0.849 % | No |
policy | 18 | 0.804 % | No |
leaving | 18 | 0.804 % | No |
services | 13 | 0.581 % | No |
rates | 12 | 0.536 % | No |
loan | 12 | 0.536 % | No |
Zelle® | 12 | 0.536 % | No |
products | 11 | 0.492 % | No |
security | 11 | 0.492 % | No |
provided | 10 | 0.447 % | No |
content | 10 | 0.447 % | No |
FAQs | 10 | 0.447 % | No |
Search | 9 | 0.402 % | No |
card | 9 | 0.402 % | No |
options | 9 | 0.402 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Wells Fargo | 64 | 2.86 % | No |
does not | 19 | 0.849 % | No |
are leaving | 18 | 0.804 % | No |
You are | 18 | 0.804 % | No |
the Wells | 10 | 0.447 % | No |
is not | 10 | 0.447 % | No |
convenience but | 9 | 0.402 % | No |
not responsible | 9 | 0.402 % | No |
responsible for | 9 | 0.402 % | No |
for the | 9 | 0.402 % | No |
the products | 9 | 0.402 % | No |
products services | 9 | 0.402 % | No |
services content | 9 | 0.402 % | No |
content links | 9 | 0.402 % | No |
links privacy | 9 | 0.402 % | No |
policy or | 9 | 0.402 % | No |
privacy policy | 9 | 0.402 % | No |
endorse and | 9 | 0.402 % | No |
or security | 9 | 0.402 % | No |
security policy | 9 | 0.402 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
You are leaving | 18 | 0.804 % | No |
the Wells Fargo | 10 | 0.447 % | No |
a website that | 9 | 0.402 % | No |
is not responsible | 9 | 0.402 % | No |
for your convenience | 9 | 0.402 % | No |
your convenience but | 9 | 0.402 % | No |
convenience but does | 9 | 0.402 % | No |
but does not | 9 | 0.402 % | No |
does not endorse | 9 | 0.402 % | No |
not endorse and | 9 | 0.402 % | No |
endorse and is | 9 | 0.402 % | No |
and is not | 9 | 0.402 % | No |
responsible for the | 9 | 0.402 % | No |
not responsible for | 9 | 0.402 % | No |
provided this link | 9 | 0.402 % | No |
for the products | 9 | 0.402 % | No |
the products services | 9 | 0.402 % | No |
products services content | 9 | 0.402 % | No |
services content links | 9 | 0.402 % | No |
content links privacy | 9 | 0.402 % | No |
Keyword | Occurrence | Density | Possible Spam |
---|---|---|---|
Fargo website You are | 9 | 0.402 % | No |
Wells Fargo does not | 9 | 0.402 % | No |
your convenience but does | 9 | 0.402 % | No |
for your convenience but | 9 | 0.402 % | No |
link for your convenience | 9 | 0.402 % | No |
this link for your | 9 | 0.402 % | No |
are leaving the Wells | 9 | 0.402 % | No |
has provided this link | 9 | 0.402 % | No |
Fargo has provided this | 9 | 0.402 % | No |
Wells Fargo has provided | 9 | 0.402 % | No |
control Wells Fargo has | 9 | 0.402 % | No |
not control Wells Fargo | 9 | 0.402 % | No |
does not control Wells | 9 | 0.402 % | No |
Fargo does not control | 9 | 0.402 % | No |
that Wells Fargo does | 9 | 0.402 % | No |
but does not endorse | 9 | 0.402 % | No |
website that Wells Fargo | 9 | 0.402 % | No |
a website that Wells | 9 | 0.402 % | No |
entering a website that | 9 | 0.402 % | No |
and entering a website | 9 | 0.402 % | No |
appointment, make an appointment, online banking, open account, book appointment, contact, statements, new account, payment, sign up, change password, contact us, enroll, login, create account, account, make payment, my account, change password for login, account summary, enroll account for online access, sign in, mobile banking, password, english, wells fargo, balance, log in, pay bills, register, create an account, sign on, online statements, full site, home, wellsfargo.com, personal, wells fargo online, covid, covid 19 hardship, covid 19 relief, covid-19, covid 19
The most using keywords match with meta keywords.
Your site have sitemap
https://www.wellsfargo.com/seo-sitemap/wellsfargositemap_index.xml
2238
Text/HTML Ratio Test : 35%
Your site have robot.txt
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" />
directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a>
if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
Some links of your site are not SEO friendly.
Site passed plain text email test. No plain text email found.
Page have doc type.
Your site have 11 images without alt text.
Your site does not have any depreciated HTML tag.
HTML page size is > 100KB
GZIP compression is enabled.
Your site have 1 inline css.
Your site does not have any internal css.
Site failed micro data schema test.
SL | Host | Class | TTL | Type | PRI | Target | IP |
---|---|---|---|---|---|---|---|
1 | Wellsfargo.com | IN | 4 | A | 23.64.119.18 | ||
2 | Wellsfargo.com | IN | 4 | A | 23.64.119.7 | ||
3 | Wellsfargo.com | IN | 3600 | NS | edns1.ultradns.net | ||
4 | Wellsfargo.com | IN | 3600 | NS | edns1.ultradns.com | ||
5 | Wellsfargo.com | IN | 3600 | NS | a1-189.akam.net | ||
6 | Wellsfargo.com | IN | 3600 | NS | a2-64.akam.net | ||
7 | Wellsfargo.com | IN | 3600 | NS | a24-66.akam.net | ||
8 | Wellsfargo.com | IN | 3600 | NS | edns1.ultradns.biz | ||
9 | Wellsfargo.com | IN | 3600 | NS | edns1.ultradns.org | ||
10 | Wellsfargo.com | IN | 900 | MX | 10 | mxa-00004003.gslb.pphosted.com | |
11 | Wellsfargo.com | IN | 900 | MX | 10 | mxb-00004003.gslb.pphosted.com |
Site failed IP canonicalization test.
Site passed URL canonicalization test.
<link rel="canonical" href="https://mywebsite.com/home" />
<link rel="canonical" href="https://www.mywebsite.com/home" />
Aggregates all network requests and groups them by typeLearn More
Potential savings of 690 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 880 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
2,510 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
5.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Potential savings of 99 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
50 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 16 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 2,036 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
6.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
1,142 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
10 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More
Aggregates all network requests and groups them by typeLearn More
Potential savings of 280 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More
Optimized images load faster and consume less cellular data. Learn More
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More
21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn More
Third-party code blocked the main thread for 100 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn More
620 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More
10 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn More
Potential savings of 37 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn More
Potential savings of 17 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More
Total size was 2,365 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn More
2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More
10 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn More
1,187 elements
A large DOM will increase memory usage, cause longer Learn More
Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded. Learn More
Minifying JavaScript files can reduce payload sizes and script parse time. Learn More
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More
10 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn More