Access 39asset.co.jp. 国際分散投資ならありがとう投信

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

39asset.co.jp

534 ms

www.39asset.co.jp

1220 ms

import.css

507 ms

css2

35 ms

jquery-1.8.3.min.js

1041 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 87% of them (80 requests) were addressed to the original 39asset.co.jp, 8% (7 requests) were made to Google.com and 2% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain 39asset.co.jp.

Content Size

4.3 MB

After Optimization

3.8 MB

In fact, the total size of 39asset.co.jp main page is 4.3 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. 60% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 54.0 kB

Original 67.4 kB
After minification 59.8 kB
After compression 13.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 7.6 kB, which is 11% 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 54.0 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 213.2 kB

Original 3.8 MB
After minification 3.6 MB

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. 39 Asset images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 100.9 kB

Original 297.2 kB
After minification 294.1 kB
After compression 196.3 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 100.9 kB or 34% of the original size.

CSS Optimization

-78%

Potential reduce by 73.0 kB

Original 94.0 kB
After minification 71.3 kB
After compression 21.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. 39asset.co.jp needs all CSS files to be minified and compressed as it can save up to 73.0 kB or 78% of the original size.

Requests Now

After Optimization

The browser has sent 88 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 10 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

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.

Social Sharing Optimization

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:

Report Summary

Performance

Accessibility

Best Practices

SEO

国際分散投資ならありがとう投信

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

39asset.co.jp

www.39asset.co.jp

import.css

css2

jquery-1.8.3.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

39asset.co.jp

www.39asset.co.jp

import.css

css2

jquery-1.8.3.min.js

jquery.cookie.js

switch.js

common.js

slick.css

slick.min.js

top.js

normalize.css

master.css

pc.css

sp_master.css

sp.css

logo.png

btn_h_contact.png

btn_h_consultation.png

btn_h_login.png

mv01_3.png

mv01_3.jpg

mv02.png

mv02.jpg

mv03.png

mv03.jpg

mv04.png

mv04.jpg

mv05.png

mv05.jpg

mv07.png

mv07.jpg

tit_jewel.png

btn_report.jpg

img_support01.png

img_support02.png

img_support03.png

26015070_s-thumb-235xauto-6635.jpg

30317058_s-thumb-235xauto-6626.jpg

30426659_s-thumb-235xauto-6634.jpg

13c21734aa20507faae3a1a183da2abb8a1de803-thumb-235xauto-6617.jpg

btn_other01.png

btn_other02.png