Tools & Wizards About Us
wooser.tv screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

wooser.tv

TVアニメ 「うーさーのその日暮らし」 公式サイト

Page Load Speed

7.3 sec in total

First Response

355 ms

Resources Loaded

6.5 sec

Page Rendered

370 ms

wooser.tv screenshot

About Website

Click here to check amazing Wooser content for Japan. Otherwise, check out these important facts you probably never knew about wooser.tv

謎の動物"うーさー"の荒ぶりそうであまり荒ぶらない「その日暮らし」

Visit wooser.tv

Key Findings

We analyzed Wooser.tv page load time and found that the first response time was 355 ms and then it took 6.9 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

wooser.tv performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value80.4 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.305

39/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

wooser.tv

355 ms

common.css

171 ms

intro.css

340 ms

top.css

341 ms

ctg.css

342 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 72% of them (107 requests) were addressed to the original Wooser.tv, 13% (20 requests) were made to Platform.twitter.com and 5% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Wooser.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (12%)

Content Size

9.1 MB

After Optimization

8.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wooser.tv main page is 9.1 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 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 84.4 kB

  • Original 95.5 kB
  • After minification 93.3 kB
  • After compression 11.1 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 84.4 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 750.3 kB

  • Original 8.5 MB
  • After minification 7.7 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. Wooser images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 220.2 kB

  • Original 466.8 kB
  • After minification 431.8 kB
  • After compression 246.6 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 220.2 kB or 47% of the original size.

CSS Optimization

-81%

Potential reduce by 44.6 kB

  • Original 54.8 kB
  • After minification 45.6 kB
  • After compression 10.3 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. Wooser.tv needs all CSS files to be minified and compressed as it can save up to 44.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (51%)

Requests Now

143

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wooser.tv

wooser.tv

355 ms

common.css

common.css

171 ms

intro.css

intro.css

340 ms

top.css

top.css

341 ms

ctg.css

ctg.css

342 ms

more.css

more.css

344 ms

entrys.css

entrys.css

349 ms

fortune.css

fortune.css

353 ms

scrollbar.css

scrollbar.css

507 ms

entry.css

entry.css

518 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

859 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

520 ms

jquery.imagesloaded.js

jquery.imagesloaded.js

521 ms

jquery.ba-hashchange.min.js

jquery.ba-hashchange.min.js

528 ms

jquery.mousewheel.js

jquery.mousewheel.js

675 ms

modernizr.js

modernizr.js

686 ms

cssfx.js

cssfx.js

700 ms

swfobject.js

swfobject.js

702 ms

ex.js

ex.js

714 ms

charaAnime.js

charaAnime.js

842 ms

intro.js

intro.js

856 ms

top.js

top.js

886 ms

more.js

more.js

887 ms

viewer.js

viewer.js

887 ms

fortune.js

fortune.js

1011 ms

loader.js

loader.js

1027 ms

scrollbar.js

scrollbar.js

1028 ms

plusone.js

plusone.js

27 ms

iealert.js

iealert.js

1065 ms

style.css

style.css

1065 ms

bookmark_button.js

bookmark_button.js

18 ms

bookmark_button.js

bookmark_button.js

16 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

button-only@2x.png

button-only@2x.png

9 ms

menubtn.png

menubtn.png

171 ms

linebutton_88x20.png

linebutton_88x20.png

176 ms

top.png

top.png

177 ms

info.png

info.png

176 ms

info_character.png

info_character.png

172 ms

info_staffcast.png

info_staffcast.png

174 ms

info_story.png

info_story.png

341 ms

anime.png

anime.png

342 ms

event.png

event.png

342 ms

products.png

products.png

349 ms

special.png

special.png

350 ms

mv1.gif

mv1.gif

1059 ms

logo.png

logo.png

515 ms

fortunebtn.png

fortunebtn.png

515 ms

loadnextbtn.gif

loadnextbtn.gif

514 ms

pagetopbtn.png

pagetopbtn.png

528 ms

cr.png

cr.png

529 ms

button-only@2x.png

button-only@2x.png

5 ms

roundedxmplus1pmedium.ttf

roundedxmplus1pmedium.ttf

5098 ms

widgets.js

widgets.js

68 ms

news.gif

news.gif

685 ms

fortunebtnBG.png

fortunebtnBG.png

690 ms

fukidashi.png

fukidashi.png

686 ms

like.php

like.php

256 ms

lineStamp_fukidashi.png

lineStamp_fukidashi.png

687 ms

lineStamp_chara.png

lineStamp_chara.png

851 ms

ga.js

ga.js

30 ms

news.html

news.html

847 ms

widget.html

widget.html

853 ms

banner.html

banner.html

849 ms

recent.html

recent.html

1009 ms

top.css

top.css

1015 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

28 ms

sharebutton

sharebutton

24 ms

menubtn_on.png

menubtn_on.png

1007 ms

loadnextbtn_on.gif

loadnextbtn_on.gif

1023 ms

pagetopbtn_on.png

pagetopbtn_on.png

1182 ms

loadingFukidashi.gif

loadingFukidashi.gif

1185 ms

loading.gif

loading.gif

1183 ms

__utm.gif

__utm.gif

21 ms

postmessageRelay

postmessageRelay

49 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

143 ms

developers.google.com

developers.google.com

530 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

8 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

settings

settings

97 ms

LakYt5zplU8.js

LakYt5zplU8.js

28 ms

FEppCFCt76d.png

FEppCFCt76d.png

20 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

43 ms

PR_wooser

PR_wooser

63 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

39 ms

embeds

embeds

61 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

23 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

42 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

50 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

57 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

82 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

82 ms

_buildManifest.js

_buildManifest.js

113 ms

_ssgManifest.js

_ssgManifest.js

113 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

23 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

50 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

42 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

64 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

20 ms

bn_380_usat.png

bn_380_usat.png

348 ms

bn_380_facebook.png

bn_380_facebook.png

349 ms

bn_380_nikoniko_2.png

bn_380_nikoniko_2.png

520 ms

bn_380_saizensen.png

bn_380_saizensen.png

520 ms

bn_380_anitere.png

bn_380_anitere.png

522 ms

bn_380_galaxxxy.png

bn_380_galaxxxy.png

522 ms

bn_380_wooser_vs_iogokoro.png

bn_380_wooser_vs_iogokoro.png

872 ms

bn_470_kurasuke.png

bn_470_kurasuke.png

1032 ms

bn_232_nikoniko_mugen_2.jpg

bn_232_nikoniko_mugen_2.jpg

688 ms

bn_232_1st_2.jpg

bn_232_1st_2.jpg

696 ms

kigurumi_sub.jpg

kigurumi_sub.jpg

540 ms

wooser_cake_2019.png

wooser_cake_2019.png

1202 ms

logo_main_anisama2019.jpg

logo_main_anisama2019.jpg

1210 ms

t_anisama2017_logo.jpg

t_anisama2017_logo.jpg

1407 ms

wooser_yuruchara_2017_t.jpg

wooser_yuruchara_2017_t.jpg

1056 ms

img_140422_2.jpg

img_140422_2.jpg

1045 ms

anisama2018_logo_l.gif

anisama2018_logo_l.gif

1219 ms

sm_140917.jpg

sm_140917.jpg

1408 ms

asagaya_bn.jpg

asagaya_bn.jpg

1372 ms

s_140930.jpg

s_140930.jpg

1381 ms

hton_news_%E3%82%B5%E3%83%A0%E3%83%8D%E3%82%A4%E3%83%AB.jpg

hton_news_%E3%82%B5%E3%83%A0%E3%83%8D%E3%82%A4%E3%83%AB.jpg

1733 ms

33.JPG

33.JPG

2909 ms

wooser_summer2017_t.jpg

wooser_summer2017_t.jpg

1551 ms

anisama2017_logo.jpg

anisama2017_logo.jpg

1756 ms

170223_wooser_AJ.jpg

170223_wooser_AJ.jpg

1583 ms

c91_wooser_01_t.jpg

c91_wooser_01_t.jpg

3437 ms

woosermegane_01.jpg

woosermegane_01.jpg

1767 ms

%E3%81%86%E3%83%BC%E3%81%95%E3%83%BC_%E7%89%88%E6%A8%A9%E7%B5%B53.jpg

%E3%81%86%E3%83%BC%E3%81%95%E3%83%BC_%E7%89%88%E6%A8%A9%E7%B5%B53.jpg

1913 ms

logo_samune.jpg

logo_samune.jpg

2099 ms

%E3%81%86%E3%83%BC%E3%81%95%E3%83%BC_%E7%89%88%E6%A8%A9%E7%B5%B52_FIX.jpg

%E3%81%86%E3%83%BC%E3%81%95%E3%83%BC_%E7%89%88%E6%A8%A9%E7%B5%B52_FIX.jpg

1935 ms

illust_03.png

illust_03.png

2094 ms

illust_02.png

illust_02.png

2084 ms

illust_01.png

illust_01.png

2108 ms

morebtn.png

morebtn.png

2111 ms

morebtn_on.png

morebtn_on.png

2141 ms

fukidashi_l_special.png

fukidashi_l_special.png

2285 ms

blank.gif

blank.gif

2286 ms

fukidashi_l_products.png

fukidashi_l_products.png

2143 ms

fukidashi_l_event.png

fukidashi_l_event.png

2288 ms

fukidashi_r_products.png

fukidashi_r_products.png

2295 ms

fukidashi_r_event.png

fukidashi_r_event.png

2316 ms

fukidashi_r_anime.png

fukidashi_r_anime.png

2290 ms

fukidashi_l_anime.png

fukidashi_l_anime.png

2293 ms

wooser.gif

wooser.gif

2312 ms

wooser_fukidashi.gif

wooser_fukidashi.gif

2284 ms

Accessibility Review

wooser.tv accessibility score

74

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

wooser.tv 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wooser.tv SEO score

67

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

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 Wooser.tv 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 Wooser.tv 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

wooser.tv

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