Tools & Wizards About Us
tokuriki-kanda.co.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

tokuriki-kanda.co.jp

金　相場・売買・資産形成は徳力本店

Page Load Speed

7.9 sec in total

First Response

594 ms

Resources Loaded

7.1 sec

Page Rendered

231 ms

tokuriki-kanda.co.jp screenshot

About Website

Visit tokuriki-kanda.co.jp now to see the best up-to-date Tokuriki Kanda content for Japan and also check out these interesting facts you probably never knew about tokuriki-kanda.co.jp

金　相場・売買・資産形成は徳力本店。金に関することなら、江戸時代からの伝統と信頼の徳力本店にお任せください。

Visit tokuriki-kanda.co.jp

Key Findings

We analyzed Tokuriki-kanda.co.jp page load time and found that the first response time was 594 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tokuriki-kanda.co.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value730 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

tokuriki-kanda.co.jp

594 ms

tokuriki-kanda.co.jp

912 ms

gtm.js

69 ms

viewport.js

346 ms

style.css

486 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Tokuriki-kanda.co.jp, 11% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Tokuriki-kanda.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 790.4 kB (24%)

Content Size

3.3 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokuriki-kanda.co.jp main page is 3.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. 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. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 19.7 kB

  • Original 24.9 kB
  • After minification 18.4 kB
  • After compression 5.2 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 6.6 kB, which is 26% 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 19.7 kB or 79% of the original size.

Image Optimization

-17%

Potential reduce by 488.6 kB

  • Original 2.9 MB
  • After minification 2.4 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. Obviously, Tokuriki Kanda needs image optimization as it can save up to 488.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 227.1 kB

  • Original 331.4 kB
  • After minification 324.8 kB
  • After compression 104.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 227.1 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 55.0 kB

  • Original 64.2 kB
  • After minification 45.8 kB
  • After compression 9.2 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. Tokuriki-kanda.co.jp needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (27%)

Requests Now

52

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokuriki-kanda.co.jp

tokuriki-kanda.co.jp

594 ms

tokuriki-kanda.co.jp

tokuriki-kanda.co.jp

912 ms

gtm.js

gtm.js

69 ms

viewport.js

viewport.js

346 ms

style.css

style.css

486 ms

drawermenu.css

drawermenu.css

519 ms

common.css

common.css

869 ms

top.css

top.css

528 ms

header.css

header.css

529 ms

Chart.bundle.min.js

Chart.bundle.min.js

1942 ms

jquery.min.js

jquery.min.js

1123 ms

smoothScroll.js

smoothScroll.js

523 ms

drawermenu.js

drawermenu.js

533 ms

common.js

common.js

537 ms

top.js

top.js

697 ms

chart.js

chart.js

709 ms

css

css

39 ms

notosansjapanese.css

notosansjapanese.css

54 ms

logo.png

logo.png

206 ms

header_txt01.png

header_txt01.png

206 ms

common_navbtn_off.png

common_navbtn_off.png

206 ms

icon_search.png

icon_search.png

205 ms

sp_header_txt01.png

sp_header_txt01.png

206 ms

buybtn_img02.png

buybtn_img02.png

204 ms

buybtn_img01.png

buybtn_img01.png

379 ms

buybtn_img03.png

buybtn_img03.png

383 ms

img01.png

img01.png

1080 ms

img01-2.png

img01-2.png

689 ms

img01-3.png

img01-3.png

558 ms

img02-1.png

img02-1.png

560 ms

img02-2.png

img02-2.png

900 ms

img02-3.png

img02-3.png

913 ms

img02-4.png

img02-4.png

1072 ms

img02-5.png

img02-5.png

911 ms

img03.png

img03.png

1173 ms

img03-2.png

img03-2.png

1247 ms

img03-3.png

img03-3.png

1089 ms

img04-1.png

img04-1.png

1266 ms

img04-2.png

img04-2.png

1595 ms

img05.png

img05.png

1431 ms

img06.png

img06.png

1442 ms

img07-01.png

img07-01.png

1497 ms

img07-02.png

img07-02.png

1593 ms

bnr01.png

bnr01.png

1444 ms

bnr05.jpg

bnr05.jpg

1781 ms

bnr03.png

bnr03.png

1619 ms

bnr06.png

bnr06.png

3739 ms

WPIC.png

WPIC.png

1658 ms

bnr04.png

bnr04.png

1769 ms

bnr_sdgs.png

bnr_sdgs.png

1769 ms

bnr_tokurikihd.jpg

bnr_tokurikihd.jpg

1797 ms

pagetop.png

pagetop.png

1820 ms

logo_footer.png

logo_footer.png

1942 ms

line_bnr.png

line_bnr.png

1999 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

34 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

89 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

406 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

315 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

291 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

112 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

115 ms

icomoon.ttf

icomoon.ttf

1756 ms

Accessibility Review

tokuriki-kanda.co.jp accessibility score

74

Accessibility Issues

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.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tokuriki-kanda.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tokuriki-kanda.co.jp SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Tokuriki-kanda.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 Tokuriki-kanda.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

tokuriki-kanda.co.jp

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