11.5 sec in total
702 ms
10.4 sec
397 ms
Click here to check amazing Am Mufg content for Japan. Otherwise, check out these important facts you probably never knew about am.mufg.jp
三菱UFJアセットマネジメントは投資信託をもっと多くの方に気軽に活用していただくために、新しい商品やサービスの開発に常に取り組んでいます。
Visit am.mufg.jpWe analyzed Am.mufg.jp page load time and found that the first response time was 702 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
am.mufg.jp performance score
name
value
score
weighting
Value15.1 s
0/100
10%
Value21.4 s
0/100
25%
Value22.4 s
0/100
10%
Value40 ms
100/100
30%
Value0.232
54/100
15%
Value18.5 s
3/100
10%
702 ms
1052 ms
1213 ms
528 ms
354 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 92% of them (105 requests) were addressed to the original Am.mufg.jp, 6% (7 requests) were made to T2.jiji.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Am.mufg.jp.
Page size can be reduced by 732.3 kB (42%)
1.8 MB
1.0 MB
In fact, the total size of Am.mufg.jp main page is 1.8 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. 25% of websites need less resources to load. Images take 874.6 kB which makes up the majority of the site volume.
Potential reduce by 69.7 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 40.6 kB, which is 53% 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 69.7 kB or 90% of the original size.
Potential reduce by 34.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. Am Mufg images are well optimized though.
Potential reduce by 528.1 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 528.1 kB or 77% of the original size.
Potential reduce by 99.8 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. Am.mufg.jp needs all CSS files to be minified and compressed as it can save up to 99.8 kB or 86% of the original size.
Number of requests can be reduced by 45 (40%)
112
67
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Am Mufg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
am.mufg.jp
702 ms
www.am.mufg.jp
1052 ms
jquery-1.11.1.min.js
1213 ms
common.js
528 ms
bookmark.js
354 ms
sendExternalSite.js
361 ms
jquery.cookie.js
368 ms
favorite.js
678 ms
top_script.js
865 ms
import.css
709 ms
style.css
866 ms
urchin.js
1187 ms
jquery-1.11.2.js
2682 ms
jquery.cookie.js
1060 ms
jquery.waypoints.js
1360 ms
of_action.js
1227 ms
of_common.js
1410 ms
jquery.customSelect.min.js
1541 ms
rn_common.js
1549 ms
tab.js
1911 ms
of_d1pc_header.js
1706 ms
muam.js
1753 ms
smartphone.js
1902 ms
navChanger.js
1903 ms
rn_style.css
2589 ms
of_slick.css
1950 ms
of_slick.js
2636 ms
muam_side.js
1750 ms
muam_sidemenu.css
1773 ms
of_d1pc_footer.css
2082 ms
ofga.js
2111 ms
reset.css
1410 ms
fund_add.css
1695 ms
module.css
2025 ms
__utm.gif
167 ms
logo1.png
193 ms
logo.png
181 ms
btn_mypage.gif
326 ms
text_fontsize.png
356 ms
btn_fontsize.gif
376 ms
text_search.png
514 ms
btn_header_serch.gif
536 ms
btn_login.gif
547 ms
header_bg.png
659 ms
gnavi.png
1006 ms
slide_260964.jpg
1580 ms
slide_nkw.jpg
1403 ms
slide03.jpg
1604 ms
slide_252390s.jpg
1414 ms
slide_261352.jpg
1715 ms
slide_261347s.jpg
2067 ms
slide02.jpg
2397 ms
slide04.jpg
2472 ms
slide05.jpg
2452 ms
thum_260964.jpg
2134 ms
thum_emaxis.gif
2088 ms
thum_03.jpg
2624 ms
thum_252390s.png
2582 ms
thum_261352.jpg
2659 ms
thum_261347s.jpg
2889 ms
thum_02.jpg
2804 ms
thum_04.jpg
2807 ms
thum_05.jpg
3128 ms
ttl_daily_report.png
2984 ms
btn_03_off.gif
3032 ms
banner_07.jpg
3323 ms
banner_01.jpg
3497 ms
banner_02.jpg
3412 ms
footer_txt.gif
3317 ms
copyright.png
3372 ms
LB1871_MARKET_NAVI.html
955 ms
analytics.js
50 ms
collect
26 ms
TopPage.php
4074 ms
getSecParamSideMenu.php
3511 ms
getSecParamSideMenu.php
3426 ms
search_center.png
3417 ms
search_left.png
3480 ms
btn_search_large.gif
3506 ms
btn_search.gif
3521 ms
btn_mdlist.gif
3710 ms
style.css
507 ms
jquery-1.8.3.min.js
1038 ms
script.js
357 ms
icon_pdf_s.gif
3440 ms
icon_market_report.png
3181 ms
line_black.png
2968 ms
tab_left_market_report.gif
2990 ms
icon_arrow01_blue.gif
2882 ms
icon_updating_info.png
2932 ms
icon_global.png
195 ms
parts_title.png
176 ms
btn_detail.gif
354 ms
tab_updating_info.gif
3054 ms
tab_right.gif
2542 ms
btn_pagetop.png
2633 ms
footer_bana.png
2779 ms
arrow_footer.png
2411 ms
icon_blank.png
2415 ms
arrow_news.png
2507 ms
slide_arrow_left.png
2484 ms
slide_arrow_right.png
2473 ms
now_load.gif
2667 ms
no_date_s.png
1514 ms
icon_fund_ranking.png
1020 ms
tab_left_fund_ranking.gif
1231 ms
fund_02_navi_old.gif
1154 ms
icon_num01.gif
1186 ms
icon_favorite_off.png
1324 ms
icon_num02.gif
1400 ms
icon_num03.gif
1408 ms
icon_num04.gif
1506 ms
icon_num05.gif
1555 ms
arrow.gif
1576 ms
am.mufg.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
am.mufg.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
am.mufg.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Am.mufg.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Am.mufg.jp 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.
am.mufg.jp
Open Graph data is detected on the main page of Am Mufg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: