Tools & Wizards About Us
torinoichi.jp screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

torinoichi.jp

浅草・酉の市2023(令和５年の酉の市は11月11日（土）・11月23日（木）勤労感謝の日 | 浅草 酉の市公式ホームページ。江戸の昔より『1年の無事に感謝し、来る年の幸を願う』酉の市。ここ浅草は、東京で一番大きく、最も賑わう酉の市です。酉の市の由来歴史を学ぶ。熊手やお守りを買う。懐かしい屋台の味を...

Page Load Speed

6.1 sec in total

First Response

1.7 sec

Resources Loaded

4.2 sec

Page Rendered

165 ms

torinoichi.jp screenshot

About Website

Welcome to torinoichi.jp homepage info - get ready to check Torinoichi best content for Japan right away, or after learning these important things about torinoichi.jp

浅草 酉の市公式ホームページ。江戸の昔より『1年の無事に感謝し、来る年の幸を願う』酉の市。ここ浅草は、東京で一番大きく、最も賑わう酉の市です。酉の市の由来歴史を学ぶ。熊手やお守りを買う。懐かしい屋台の味を堪能すし遊ぶ事を網羅した酉の市オフィシャルホームページです。

Visit torinoichi.jp

Key Findings

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

Performance Metrics

torinoichi.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value30.5 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value2,490 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.896

3/100

15%

TTI (Time to Interactive)

Value44.3 s

0/100

10%

Network Requests Diagram

index.htm

1749 ms

cho.css

577 ms

spc.gif

331 ms

top_05.gif

342 ms

top_08.gif

359 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that all of those requests were addressed to Torinoichi.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Torinoichi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.2 kB (75%)

Content Size

25.5 kB

After Optimization

6.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Torinoichi.jp main page is 25.5 kB. 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 10% of websites need less resources to load. HTML takes 21.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 15.7 kB

  • Original 21.1 kB
  • After minification 19.6 kB
  • After compression 5.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 15.7 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 311 B
  • After minification 311 B

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

CSS Optimization

-85%

Potential reduce by 3.5 kB

  • Original 4.1 kB
  • After minification 3.5 kB
  • After compression 619 B

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. Torinoichi.jp needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (43%)

Requests Now

44

After Optimization

25

  • Images
  • CSS

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

Network Requests Diagram

index.htm

index.htm

1749 ms

cho.css

cho.css

577 ms

spc.gif

spc.gif

331 ms

top_05.gif

top_05.gif

342 ms

top_08.gif

top_08.gif

359 ms

top_13.gif

top_13.gif

357 ms

top_19.gif

top_19.gif

397 ms

top_01.gif

top_01.gif

498 ms

top_03.gif

top_03.gif

507 ms

top_06.gif

top_06.gif

712 ms

top_09.gif

top_09.gif

712 ms

top_14.gif

top_14.gif

562 ms

top_20.gif

top_20.gif

596 ms

top_24.gif

top_24.gif

664 ms

top_29.gif

top_29.gif

674 ms

top_01-20061030.gif

top_01-20061030.gif

753 ms

top_02-20061030.gif

top_02-20061030.gif

796 ms

top_20160101.gif

top_20160101.gif

1488 ms

top_04.gif

top_04.gif

838 ms

top_07.gif

top_07.gif

887 ms

top_12.gif

top_12.gif

1064 ms

top_18.gif

top_18.gif

939 ms

top_menu_01.gif

top_menu_01.gif

998 ms

top_menu_02.gif

top_menu_02.gif

1002 ms

top_menu_03.gif

top_menu_03.gif

1061 ms

top_menu_04.gif

top_menu_04.gif

1125 ms

top_menu_05.gif

top_menu_05.gif

1195 ms

top_menu_06.gif

top_menu_06.gif

1167 ms

top_20080101_3.gif

top_20080101_3.gif

1240 ms

top_30.gif

top_30.gif

1242 ms

top_31a.gif

top_31a.gif

1312 ms

top_32.gif

top_32.gif

1339 ms

top_33.gif

top_33.gif

1399 ms

top_34.gif

top_34.gif

1416 ms

top_35.gif

top_35.gif

1419 ms

top_37.gif

top_37.gif

1499 ms

top_38.gif

top_38.gif

1321 ms

top_39.gif

top_39.gif

1282 ms

top_40.gif

top_40.gif

1265 ms

top_41.gif

top_41.gif

1251 ms

top_42.gif

top_42.gif

1297 ms

top_43.gif

top_43.gif

1307 ms

pagetop.gif

pagetop.gif

1291 ms

counter.cgi

counter.cgi

1501 ms

indexback.jpg

indexback.jpg

1282 ms

Accessibility Review

torinoichi.jp accessibility score

92

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

torinoichi.jp SEO score

90

Search Engine Optimization Advices

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torinoichi.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 Torinoichi.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

torinoichi.jp

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