Tools & Wizards About Us
kamiusagi.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

kamiusagi.jp

「紙兎ロペ」オフィシャルサイト

Page Load Speed

6.1 sec in total

First Response

940 ms

Resources Loaded

4.5 sec

Page Rendered

634 ms

kamiusagi.jp screenshot

About Website

Click here to check amazing Kamiusagi content for Japan. Otherwise, check out these important facts you probably never knew about kamiusagi.jp

ショートアニメ『紙兎ロペ 笑う朝には福来るってマジっすか！？』が、フジテレビ「めざましテレビ」にて毎週月〜金曜日放送中！！

Visit kamiusagi.jp

Key Findings

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

Performance Metrics

kamiusagi.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value2,160 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

kamiusagi.jp

940 ms

style.css

778 ms

colorbox.css

475 ms

lightbox.css

509 ms

jquery-1.7.1.min.js

1325 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Kamiusagi.jp, 16% (15 requests) were made to Pbs.twimg.com and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Kamiusagi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 714.2 kB (17%)

Content Size

4.3 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 23.2 kB

  • Original 29.6 kB
  • After minification 24.8 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 16% 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 23.2 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 233.0 kB

  • Original 3.6 MB
  • After minification 3.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. Kamiusagi images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 202.8 kB

  • Original 329.7 kB
  • After minification 327.8 kB
  • After compression 126.9 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 202.8 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 255.2 kB

  • Original 306.9 kB
  • After minification 298.6 kB
  • After compression 51.7 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. Kamiusagi.jp needs all CSS files to be minified and compressed as it can save up to 255.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (33%)

Requests Now

85

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kamiusagi.jp

kamiusagi.jp

940 ms

style.css

style.css

778 ms

colorbox.css

colorbox.css

475 ms

lightbox.css

lightbox.css

509 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1325 ms

smartRollover.js

smartRollover.js

385 ms

scrolltopcontrol.js

scrolltopcontrol.js

770 ms

mouseover.js

mouseover.js

631 ms

randomdisplay.js

randomdisplay.js

668 ms

reset.css

reset.css

170 ms

common.css

common.css

160 ms

ga.js

ga.js

86 ms

title_bg.jpg

title_bg.jpg

2205 ms

close.png

close.png

208 ms

loading.gif

loading.gif

210 ms

prev.png

prev.png

208 ms

next.png

next.png

210 ms

bg_navi.png

bg_navi.png

363 ms

gnav01_off.png

gnav01_off.png

368 ms

gnav02_off.png

gnav02_off.png

581 ms

gnav03_off.png

gnav03_off.png

365 ms

gnav04_off.png

gnav04_off.png

607 ms

gnav05_off.png

gnav05_off.png

578 ms

gnav06_off.png

gnav06_off.png

577 ms

btn_contact_off.png

btn_contact_off.png

578 ms

title.png

title.png

2192 ms

btn_dvd.png

btn_dvd.png

1630 ms

btn_shindan.png

btn_shindan.png

1134 ms

label_mezamashi.png

label_mezamashi.png

904 ms

btn_twitter.png

btn_twitter.png

797 ms

btn_facebook.png

btn_facebook.png

1129 ms

akira_pattern.png

akira_pattern.png

1135 ms

bg.png

bg.png

1193 ms

nazonazo_banner_top.png

nazonazo_banner_top.png

1710 ms

tl_top_news.png

tl_top_news.png

1248 ms

bg_top_box.png

bg_top_box.png

1377 ms

bg_top_news.gif

bg_top_news.gif

1420 ms

external-link-grey-light02.png

external-link-grey-light02.png

1701 ms

bg_top_box2.png

bg_top_box2.png

1729 ms

bg_box2_top.jpg

bg_box2_top.jpg

1787 ms

tl_top_movie.png

tl_top_movie.png

2184 ms

bana_top.png

bana_top.png

1879 ms

bnr_twitter.png

bnr_twitter.png

1884 ms

bnr_facebook.png

bnr_facebook.png

2048 ms

bnr_youtube.png

bnr_youtube.png

2039 ms

bnr_planetarium.png

bnr_planetarium.png

2739 ms

bnr_collabo_au.jpg

bnr_collabo_au.jpg

2656 ms

widgets.js

widgets.js

84 ms

bnr_collabo_taiyakan_new2.jpg

bnr_collabo_taiyakan_new2.jpg

2150 ms

HUihg8LLH3M

HUihg8LLH3M

127 ms

eyaAO0sxqQ0

eyaAO0sxqQ0

192 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

397 ms

collect

collect

179 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

41 ms

www-embed-player.js

www-embed-player.js

125 ms

base.js

base.js

179 ms

bnr_collabo_auWallet.jpg

bnr_collabo_auWallet.jpg

2348 ms

title_goods.png

title_goods.png

2143 ms

bnr_goods_eshop.gif

bnr_goods_eshop.gif

2163 ms

bnr_goods_mgstella.png

bnr_goods_mgstella.png

2452 ms

top_copylight.png

top_copylight.png

2179 ms

bana_bg4.png

bana_bg4.png

2351 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

82 ms

ad_status.js

ad_status.js

69 ms

totop_off.png

totop_off.png

2142 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

93 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

94 ms

syndication

syndication

153 ms

345109282376794112

345109282376794112

219 ms

proxy.jpg

proxy.jpg

134 ms

proxy.jpg

proxy.jpg

78 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

40 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

75 ms

tohorope_av1_normal.png

tohorope_av1_normal.png

86 ms

Mv4fgDci_normal.jpg

Mv4fgDci_normal.jpg

83 ms

Cdz_fkGVAAACV1B.png:large

Cdz_fkGVAAACV1B.png:large

254 ms

Cdj0SLiUMAQTpxq.jpg:large

Cdj0SLiUMAQTpxq.jpg:large

253 ms

Cdfj9ZgUUAAesJ2.jpg:small

Cdfj9ZgUUAAesJ2.jpg:small

87 ms

Cc_PHXvUYAAa1it.jpg:small

Cc_PHXvUYAAa1it.jpg:small

88 ms

Ccq_8QXUYAE2lRI.jpg:large

Ccq_8QXUYAE2lRI.jpg:large

255 ms

CccXZRhUMAMAWJG.jpg:large

CccXZRhUMAMAWJG.jpg:large

255 ms

CbirbAaUYAAjM0i.jpg:small

CbirbAaUYAAjM0i.jpg:small

249 ms

CavN60AUYAAoEsX.jpg:large

CavN60AUYAAoEsX.jpg:large

314 ms

CaLM64mUEAAL8Pw.jpg:large

CaLM64mUEAAL8Pw.jpg:large

274 ms

CYMc-0jUQAAl1kV.jpg:large

CYMc-0jUQAAl1kV.jpg:large

257 ms

CX_s3ZkUEAAQUyD.jpg:large

CX_s3ZkUEAAQUyD.jpg:large

315 ms

CcDTSayUUAAXv1A.png:small

CcDTSayUUAAXv1A.png:small

255 ms

CcDTSaXUkAAG3VN.jpg:small

CcDTSaXUkAAG3VN.jpg:small

377 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

90 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

236 ms

proxy.jpg

proxy.jpg

51 ms

jot.html

jot.html

29 ms

Accessibility Review

kamiusagi.jp accessibility score

60

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

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

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

SEO Factors

kamiusagi.jp SEO score

77

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

High

robots.txt is not valid

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

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

kamiusagi.jp

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