Tools & Wizards About Us
ameyoko.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ameyoko.jp

上野アメ横商店街公式サイト

Page Load Speed

7.3 sec in total

First Response

366 ms

Resources Loaded

6.4 sec

Page Rendered

607 ms

ameyoko.jp screenshot

About Website

Click here to check amazing Ameyoko content. Otherwise, check out these important facts you probably never knew about ameyoko.jp

東京都台東区上野にあるアメ横商店街の公式ホームページです。

Visit ameyoko.jp

Key Findings

We analyzed Ameyoko.jp page load time and found that the first response time was 366 ms and then it took 7 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

ameyoko.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value2,000 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

www.ameyoko.net

366 ms

www.ameyoko.net

669 ms

css2

38 ms

common.css

193 ms

shared.css

356 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ameyoko.jp, 8% (8 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Ameyoko.net.

Page Optimization Overview & Recommendations

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

Content Size

6.2 MB

After Optimization

5.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ameyoko.jp main page is 6.2 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. 75% 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 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 198.7 kB

  • Original 236.4 kB
  • After minification 223.8 kB
  • After compression 37.7 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 198.7 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 340.1 kB

  • Original 5.3 MB
  • After minification 5.0 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. Ameyoko images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 21.3 kB

  • Original 585.4 kB
  • After minification 585.4 kB
  • After compression 564.2 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 3.4 kB

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

Requests Breakdown

Number of requests can be reduced by 42 (44%)

Requests Now

95

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ameyoko. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.ameyoko.net

www.ameyoko.net

366 ms

www.ameyoko.net

www.ameyoko.net

669 ms

css2

css2

38 ms

common.css

common.css

193 ms

shared.css

shared.css

356 ms

animate.min.css

animate.min.css

474 ms

global.css

global.css

476 ms

index.css

index.css

492 ms

js

js

66 ms

adsbygoogle.js

adsbygoogle.js

114 ms

base.js

base.js

666 ms

autoload.js

autoload.js

749 ms

jquery.min.js

jquery.min.js

675 ms

common.js

common.js

728 ms

shared.js

shared.js

673 ms

axios.min.js

axios.min.js

673 ms

instagram.js

instagram.js

673 ms

logo.svg

logo.svg

420 ms

arrow.svg

arrow.svg

421 ms

f_logo.svg

f_logo.svg

420 ms

ico1.svg

ico1.svg

417 ms

ico2.svg

ico2.svg

422 ms

ico3.svg

ico3.svg

422 ms

ico4.svg

ico4.svg

609 ms

ico5.svg

ico5.svg

607 ms

sub_soc1.png

sub_soc1.png

612 ms

sub_soc2.png

sub_soc2.png

608 ms

sub_soc3.png

sub_soc3.png

610 ms

key_txt.png

key_txt.png

620 ms

key.jpg

key.jpg

1467 ms

bnr_ico1.png

bnr_ico1.png

764 ms

bnr1.jpg

bnr1.jpg

1107 ms

bnr_ico2.png

bnr_ico2.png

766 ms

bnr2.jpg

bnr2.jpg

1157 ms

bnr_ico3.png

bnr_ico3.png

781 ms

bnr3.jpg

bnr3.jpg

1154 ms

2024_noto.jpg

2024_noto.jpg

1158 ms

shimai_930x180.png

shimai_930x180.png

1065 ms

insta_2_930x180.png

insta_2_930x180.png

1476 ms

70th_930x180.png

70th_930x180.png

1642 ms

tenant_930x180.png

tenant_930x180.png

1432 ms

h_ico1.png

h_ico1.png

1431 ms

h_ico2.png

h_ico2.png

1431 ms

sec1_p1.jpg

sec1_p1.jpg

2911 ms

sec1_p2.jpg

sec1_p2.jpg

2820 ms

sec1_p3.jpg

sec1_p3.jpg

2430 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

266 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf

569 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

589 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

591 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf

590 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

361 ms

arow3.svg

arow3.svg

1514 ms

sec1_p5.jpg

sec1_p5.jpg

2129 ms

instagram.png

instagram.png

1722 ms

sec2_p1.jpg

sec2_p1.jpg

2032 ms

show_ads_impl.js

show_ads_impl.js

276 ms

link.svg

link.svg

1827 ms

sec2_p2.jpg

sec2_p2.jpg

2784 ms

css2

css2

149 ms

common.css

common.css

1984 ms

sdk.js

sdk.js

207 ms

shared.css

shared.css

1986 ms

animate.min.css

animate.min.css

2044 ms

global.css

global.css

2148 ms

index.css

index.css

2207 ms

sec2_p3.jpg

sec2_p3.jpg

3308 ms

sec2_p4.jpg

sec2_p4.jpg

2418 ms

zrt_lookup.html

zrt_lookup.html

76 ms

ads

ads

488 ms

sdk.js

sdk.js

19 ms

sec2_p6.jpg

sec2_p6.jpg

2263 ms

sec2_p5.jpg

sec2_p5.jpg

3625 ms

sec5_p1.jpg

sec5_p1.jpg

2416 ms

sec5_p2.jpg

sec5_p2.jpg

2444 ms

soc1.png

soc1.png

2514 ms

soc2.png

soc2.png

2490 ms

soc3.png

soc3.png

2424 ms

arow2.svg

arow2.svg

2446 ms

f_bnr1.jpg

f_bnr1.jpg

2490 ms

reactive_library.js

reactive_library.js

140 ms

f_bnr2.jpg

f_bnr2.jpg

2202 ms

ads

ads

313 ms

ads

ads

304 ms

f_bnr3.jpg

f_bnr3.jpg

2220 ms

f_bnr4.jpg

f_bnr4.jpg

2215 ms

f_bnr5.jpg

f_bnr5.jpg

2275 ms

up.png

up.png

2317 ms

load_preloaded_resource.js

load_preloaded_resource.js

55 ms

abg_lite.js

abg_lite.js

54 ms

s

s

28 ms

window_focus.js

window_focus.js

53 ms

qs_click_protection.js

qs_click_protection.js

73 ms

ufs_web_display.js

ufs_web_display.js

28 ms

c653839755d9d9a3a773c62a0253f53f.js

c653839755d9d9a3a773c62a0253f53f.js

179 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

57 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

61 ms

icon.png

icon.png

40 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

170 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

169 ms

css

css

29 ms

up_sp.svg

up_sp.svg

2084 ms

font

font

33 ms

font

font

26 ms

d4Vwwu8iHiCDxZ1xzxUGRbEaLZqCebWmAfX3l2eV90k.js

d4Vwwu8iHiCDxZ1xzxUGRbEaLZqCebWmAfX3l2eV90k.js

4 ms

Accessibility Review

ameyoko.jp accessibility score

97

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.

Best Practices

ameyoko.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ameyoko.jp SEO score

100

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

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

ameyoko.jp

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