Tools & Wizards About Us
yagenbori.jp screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

yagenbori.jp

やげん堀　七味唐辛子本舗-オフィシャルサイト

Page Load Speed

6.8 sec in total

First Response

536 ms

Resources Loaded

5.4 sec

Page Rendered

826 ms

yagenbori.jp screenshot

About Website

Visit yagenbori.jp now to see the best up-to-date Yagenbori content and also check out these interesting facts you probably never knew about yagenbori.jp

寛永二年創業約400年、やげん堀は七味唐辛子の製造販売といったこの道一筋の老舗として、浅草新仲見世本店・メトロ通り店にて昔のままの味と伝統を誇っております。お問い合わせ»03-3626-7716

Visit yagenbori.jp

Key Findings

We analyzed Yagenbori.jp page load time and found that the first response time was 536 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

yagenbori.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value1.363

0/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

yagenbori.jp

536 ms

yagenbori.jp

1586 ms

js

62 ms

sbi-styles.min.css

194 ms

vkExUnit_style.css

388 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 77% of them (68 requests) were addressed to the original Yagenbori.jp, 8% (7 requests) were made to Youtube.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Yagenbori.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 171.0 kB (5%)

Content Size

3.3 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yagenbori.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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 93.7 kB

  • Original 114.1 kB
  • After minification 111.4 kB
  • After compression 20.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. 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 93.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 15.5 kB

  • Original 2.4 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. Yagenbori images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 37.3 kB

  • Original 619.7 kB
  • After minification 619.7 kB
  • After compression 582.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 24.5 kB

  • Original 208.3 kB
  • After minification 208.3 kB
  • After compression 183.9 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. Yagenbori.jp needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (45%)

Requests Now

80

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yagenbori.jp

yagenbori.jp

536 ms

yagenbori.jp

yagenbori.jp

1586 ms

js

js

62 ms

sbi-styles.min.css

sbi-styles.min.css

194 ms

vkExUnit_style.css

vkExUnit_style.css

388 ms

style.css

style.css

530 ms

styles.css

styles.css

529 ms

dashicons.min.css

dashicons.min.css

706 ms

reset.css

reset.css

532 ms

twentyeighteen.css

twentyeighteen.css

580 ms

swiper.min.css

swiper.min.css

580 ms

style.css

style.css

879 ms

block-build.css

block-build.css

705 ms

common.css

common.css

708 ms

style.css

style.css

772 ms

media-posts.css

media-posts.css

771 ms

style.css

style.css

889 ms

all.min.css

all.min.css

890 ms

jquery.min.js

jquery.min.js

1055 ms

&ver=0.2.1

&ver=0.2.1

1756 ms

wp-polyfill.min.js

wp-polyfill.min.js

1216 ms

lodash.min.js

lodash.min.js

1050 ms

api.js

api.js

39 ms

autoptimize_7486348308efa4c7f1e06733cdb975c1.js

autoptimize_7486348308efa4c7f1e06733cdb975c1.js

1233 ms

logo.png

logo.png

188 ms

main01.jpg

main01.jpg

188 ms

main02.jpg

main02.jpg

190 ms

main03.jpg

main03.jpg

307 ms

ttl_news.png

ttl_news.png

527 ms

1x1.trans.gif

1x1.trans.gif

650 ms

link_1ran.png

link_1ran.png

651 ms

ttl_about.png

ttl_about.png

652 ms

about01.jpg

about01.jpg

888 ms

about02.jpg

about02.jpg

694 ms

about04.jpg

about04.jpg

888 ms

about05.jpg

about05.jpg

752 ms

ttl_online_shop.png

ttl_online_shop.png

692 ms

top_7mi.jpg

top_7mi.jpg

886 ms

top_youki.jpg

top_youki.jpg

1052 ms

top_set.jpg

top_set.jpg

888 ms

top_furikake.jpg

top_furikake.jpg

1070 ms

top_ochaduke.jpg

top_ochaduke.jpg

1264 ms

top_tsukudani.jpg

top_tsukudani.jpg

1074 ms

link_staff.png

link_staff.png

1055 ms

ttl_sns.png

ttl_sns.png

1055 ms

sns_fb.png

sns_fb.png

1228 ms

sns_insta.png

sns_insta.png

1231 ms

sns_twi.png

sns_twi.png

1231 ms

sns_line.png

sns_line.png

1245 ms

placeholder.png

placeholder.png

1266 ms

logo_black.png

logo_black.png

1405 ms

footer_online2.png

footer_online2.png

1404 ms

224wvscg_middle.png

224wvscg_middle.png

1407 ms

iframe_api

iframe_api

116 ms

ir_20240816000001.jpg

ir_20240816000001.jpg

1571 ms

IMG_20180829_083558_928-1024x1024.jpg

IMG_20180829_083558_928-1024x1024.jpg

1617 ms

IMG_7276-1024x683.jpg

IMG_7276-1024x683.jpg

1617 ms

20240701chogo.jpg

20240701chogo.jpg

1750 ms

widgets.js

widgets.js

78 ms

wARDj0u

wARDj0u

3 ms

fa-solid-900.woff

fa-solid-900.woff

1615 ms

www-widgetapi.js

www-widgetapi.js

14 ms

r4XUmSNaDgo

r4XUmSNaDgo

95 ms

fa-regular-400.woff

fa-regular-400.woff

1401 ms

2283f1d6-60e6-490d-8f91-ca5e9bc45f06-1024x1024.jpg

2283f1d6-60e6-490d-8f91-ca5e9bc45f06-1024x1024.jpg

1598 ms

santo-yagen01.jpg

santo-yagen01.jpg

1597 ms

staff_bg.jpg

staff_bg.jpg

1831 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

58 ms

vk-menu-btn-white.svg

vk-menu-btn-white.svg

1513 ms

ad_status.js

ad_status.js

185 ms

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

98 ms

embed.js

embed.js

69 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

1244 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

1246 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

1255 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

1267 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

1428 ms

wp-polyfill-object-fit.min.js

wp-polyfill-object-fit.min.js

1425 ms

object-fit-polyfill.min.5f0c4c73.js

object-fit-polyfill.min.5f0c4c73.js

1424 ms

id

id

51 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

140 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

141 ms

Create

Create

149 ms

GenerateIT

GenerateIT

15 ms

recaptcha__en.js

recaptcha__en.js

57 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

34 ms

Accessibility Review

yagenbori.jp accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

yagenbori.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yagenbori.jp SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Yagenbori.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 Yagenbori.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

yagenbori.jp

Open Graph data is detected on the main page of Yagenbori. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: