Tools & Wizards About Us
yoshitome.co.jp screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yoshitome.co.jp

薩摩なた豆｜ヨシトメ産業株式会社

Page Load Speed

2.9 sec in total

First Response

938 ms

Resources Loaded

1.6 sec

Page Rendered

372 ms

yoshitome.co.jp screenshot

About Website

Click here to check amazing Yoshitome content. Otherwise, check out these important facts you probably never knew about yoshitome.co.jp

ナタマメのヨシトメ産業オフィシャル・直販ページ。鹿児島県産の高品質『薩摩なた豆』だけを使った自慢のブランドを、ぜひ体験してください。

Visit yoshitome.co.jp

Key Findings

We analyzed Yoshitome.co.jp page load time and found that the first response time was 938 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Yoshitome.co.jp rating and web reputation

Performance Metrics

yoshitome.co.jp performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.671

0/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

www.yoshitome.co.jp

938 ms

default.v2.js

13 ms

parts.css

15 ms

def.css

24 ms

css01.css

24 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 97% of them (64 requests) were addressed to the original Yoshitome.co.jp, 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (938 ms) belongs to the original domain Yoshitome.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.0 kB (9%)

Content Size

3.6 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yoshitome.co.jp main page is 3.6 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 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 19.7 kB

  • Original 24.2 kB
  • After minification 22.1 kB
  • After compression 4.6 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 19.7 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 146.8 kB

  • Original 3.3 MB
  • After minification 3.2 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. Yoshitome images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 127.0 kB

  • Original 187.4 kB
  • After minification 153.6 kB
  • After compression 60.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 127.0 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 43.5 kB

  • Original 52.5 kB
  • After minification 41.1 kB
  • After compression 9.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. Yoshitome.co.jp needs all CSS files to be minified and compressed as it can save up to 43.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

55

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.yoshitome.co.jp

www.yoshitome.co.jp

938 ms

default.v2.js

default.v2.js

13 ms

parts.css

parts.css

15 ms

def.css

def.css

24 ms

css01.css

css01.css

24 ms

jquery.lightbox.css

jquery.lightbox.css

25 ms

heightLine.js

heightLine.js

25 ms

jquery.js

jquery.js

24 ms

jquery.lightbox.js

jquery.lightbox.js

47 ms

flexslider.css

flexslider.css

45 ms

jquery.flexslider.js

jquery.flexslider.js

50 ms

dc.js

dc.js

69 ms

bg.jpg

bg.jpg

20 ms

logo.png

logo.png

32 ms

menu_1b.png

menu_1b.png

27 ms

menu_2.png

menu_2.png

33 ms

menu_3b.png

menu_3b.png

35 ms

menu_4b.png

menu_4b.png

40 ms

menu_5b.png

menu_5b.png

42 ms

menu_6b.png

menu_6b.png

43 ms

menu_7.png

menu_7.png

44 ms

35_ext_01_0.jpg

35_ext_01_0.jpg

160 ms

clear.png

clear.png

48 ms

35_ext_01_4.jpg

35_ext_01_4.jpg

190 ms

35_ext_01_1.jpg

35_ext_01_1.jpg

180 ms

35_ext_01_2.jpg

35_ext_01_2.jpg

146 ms

35_ext_01_3.jpg

35_ext_01_3.jpg

196 ms

h2_bg.png

h2_bg.png

142 ms

line2.png

line2.png

143 ms

news.png

news.png

146 ms

top_daichi.png

top_daichi.png

160 ms

top_daichi3.jpg

top_daichi3.jpg

169 ms

top_daichi2.jpg

top_daichi2.jpg

175 ms

top_s0.png

top_s0.png

173 ms

top_s1.png

top_s1.png

175 ms

top_s2.png

top_s2.png

180 ms

top_s3.png

top_s3.png

175 ms

top_s4.png

top_s4.png

180 ms

top_s5.png

top_s5.png

182 ms

top_s6.png

top_s6.png

182 ms

ban_msg.png

ban_msg.png

181 ms

side_m.png

side_m.png

182 ms

68_ext_02_0.png

68_ext_02_0.png

222 ms

side_m1_df.png

side_m1_df.png

221 ms

side_m2_df.png

side_m2_df.png

213 ms

side_m3.png

side_m3.png

178 ms

78_ext_02_0.png

78_ext_02_0.png

213 ms

78_ext_02_1.jpg

78_ext_02_1.jpg

178 ms

side_kyoukai.png

side_kyoukai.png

167 ms

side_address-290x140.png

side_address-290x140.png

165 ms

201403271348_1.gif

201403271348_1.gif

196 ms

201404221353_1.gif

201404221353_1.gif

190 ms

footer_bg.gif

footer_bg.gif

190 ms

footer.gif

footer.gif

188 ms

footer_logo.png

footer_logo.png

190 ms

foot_menu_01.png

foot_menu_01.png

189 ms

foot_menu_02.png

foot_menu_02.png

188 ms

__utm.gif

__utm.gif

54 ms

foot_menu_03.png

foot_menu_03.png

88 ms

foot_menu_04.png

foot_menu_04.png

88 ms

foot_menu_05.png

foot_menu_05.png

87 ms

foot_menu_06.png

foot_menu_06.png

92 ms

foot_menu_07.png

foot_menu_07.png

81 ms

foot_menu_08.png

foot_menu_08.png

79 ms

foot_menu_09.png

foot_menu_09.png

70 ms

foot_menu_11.png

foot_menu_11.png

66 ms

Accessibility Review

yoshitome.co.jp accessibility score

71

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

yoshitome.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

yoshitome.co.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document doesn't use 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 Yoshitome.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 Yoshitome.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

yoshitome.co.jp

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