7 sec in total
1.5 sec
5.3 sec
249 ms
Click here to check amazing 39 Asset content for Japan. Otherwise, check out these important facts you probably never knew about 39asset.co.jp
国際分散投資のありがとう投信。税理士・公認会計士が立ち上げた独立系資産運用会社がお客様の資産運用を一生涯サポートいたします。
Visit 39asset.co.jpWe analyzed 39asset.co.jp page load time and found that the first response time was 1.5 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
39asset.co.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.9 s
0/100
25%
Value11.7 s
4/100
10%
Value890 ms
32/100
30%
Value0.531
14/100
15%
Value13.9 s
10/100
10%
1531 ms
977 ms
564 ms
385 ms
966 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 69% of them (45 requests) were addressed to the original 39asset.co.jp, 15% (10 requests) were made to Google.com and 5% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain 39asset.co.jp.
Page size can be reduced by 237.1 kB (22%)
1.1 MB
837.3 kB
In fact, the total size of 39asset.co.jp 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. 35% of websites need less resources to load. Images take 867.9 kB which makes up the majority of the site volume.
Potential reduce by 32.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.9 kB or 74% of the original size.
Potential reduce by 121.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. Obviously, 39 Asset needs image optimization as it can save up to 121.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 36.7 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 36.7 kB or 34% of the original size.
Potential reduce by 45.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. 39asset.co.jp needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 83% of the original size.
Number of requests can be reduced by 14 (23%)
60
46
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 39 Asset. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
39asset.co.jp
1531 ms
www.39asset.co.jp
977 ms
skitter.styles.css
564 ms
reset.css
385 ms
ui.css
966 ms
jquery.min.js
33 ms
jquery.leaveNotice.js
388 ms
jquery.easing.1.3.js
582 ms
jquery.animate-color-min.js
572 ms
jquery.skitter.min.js
1179 ms
script-top.js
578 ms
urchin.js
58 ms
index.htm
388 ms
header-logo.gif
194 ms
header-contact.gif
195 ms
header_kouzakaisetsu.png
193 ms
01.jpg
925 ms
02.jpg
761 ms
14.jpg
772 ms
top-icon-1.png
762 ms
top-icon-2.png
582 ms
top-icon-3.png
582 ms
top-icon-4.png
964 ms
top-icon-5.png
969 ms
top-fundinfo-title.png
952 ms
top-fundinfo-tousinlib-link.png
953 ms
top-icon-39letter.png
961 ms
top-icon-fm.png
1109 ms
top-icon-seminar.png
1142 ms
banner_anata-no-hatena.jpg
1142 ms
banner_arigato.png
1538 ms
banner_shoukentorhikitoukanshiiinkai.gif
1155 ms
banner_toushishintakukyoukai.gif
1157 ms
sdk.js
208 ms
cse.js
75 ms
gnav_bg.png
1275 ms
gnav.png
1315 ms
__utm.gif
27 ms
cse.js
157 ms
prev.png
1240 ms
next.png
1256 ms
top-icon-1_ov.png
1451 ms
top-icon-2_ov.png
1580 ms
top-icon-3_ov.png
1623 ms
top-icon-4_ov.png
1626 ms
top-icon-5_ov.png
1644 ms
top-fundinfo-tousinlib-link_ov.png
1641 ms
top-icon-39letter_ov.png
1645 ms
top-icon-fm_ov.png
1766 ms
top-icon-seminar_ov.png
1813 ms
ajax-loader.gif
1815 ms
63 ms
jsapi
56 ms
xd_arbiter.php
180 ms
xd_arbiter.php
300 ms
default+ja.css
6 ms
default.css
17 ms
default+ja.I.js
24 ms
default.css
40 ms
async-ads.js
75 ms
google_custom_search_watermark.gif
59 ms
small-logo.png
53 ms
search_box_icon.png
53 ms
clear.png
55 ms
nav_logo114.png
51 ms
39asset.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
39asset.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
39asset.co.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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 39asset.co.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 39asset.co.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.
39asset.co.jp
Open Graph description is not detected on the main page of 39 Asset. 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: