Tools & Wizards About Us
taritari.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

taritari.jp

アニメ「TARI TARI」公式サイト

Page Load Speed

3.5 sec in total

First Response

543 ms

Resources Loaded

2.8 sec

Page Rendered

158 ms

taritari.jp screenshot

About Website

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

晴れたり泣いたり　あとは時々 歌ってみたり

Visit taritari.jp

Key Findings

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

Performance Metrics

taritari.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

taritari.jp

543 ms

master.css

179 ms

rollover.js

347 ms

jquery.min.js

529 ms

jquery.lightbox-0.5.js

357 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 70% of them (48 requests) were addressed to the original Taritari.jp, 26% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Taritari.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.4 kB (6%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taritari.jp main page is 2.0 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. 70% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.7 kB

  • Original 11.3 kB
  • After minification 10.3 kB
  • After compression 3.6 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 7.7 kB or 68% of the original size.

Image Optimization

-6%

Potential reduce by 109.2 kB

  • Original 2.0 MB
  • After minification 1.9 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. TARI images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 8.5 kB

  • Original 35.6 kB
  • After minification 35.4 kB
  • After compression 27.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 8.5 kB or 24% of the original size.

CSS Optimization

-36%

Potential reduce by 1.1 kB

  • Original 3.1 kB
  • After minification 3.0 kB
  • After compression 2.0 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. Taritari.jp needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (35%)

Requests Now

66

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taritari.jp

taritari.jp

543 ms

master.css

master.css

179 ms

rollover.js

rollover.js

347 ms

jquery.min.js

jquery.min.js

529 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

357 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

355 ms

mrliteLogger.js

mrliteLogger.js

553 ms

base.css

base.css

184 ms

main.css

main.css

344 ms

rss_getter.php

rss_getter.php

306 ms

body_img_bg.jpg

body_img_bg.jpg

1389 ms

main_img.jpg

main_img.jpg

183 ms

logo_taritari.png

logo_taritari.png

369 ms

pre_txt_img150107.png

pre_txt_img150107.png

178 ms

topmenu_story_btn.jpg

topmenu_story_btn.jpg

173 ms

topmenu_chara_btn.jpg

topmenu_chara_btn.jpg

357 ms

topmenu_staff_btn.jpg

topmenu_staff_btn.jpg

369 ms

topmenu_onair_btn.jpg

topmenu_onair_btn.jpg

369 ms

topmenu_goods_btn.jpg

topmenu_goods_btn.jpg

482 ms

topmenu_special_btn.jpg

topmenu_special_btn.jpg

516 ms

topmenu_news_btn.jpg

topmenu_news_btn.jpg

532 ms

topmenu_blog_btn.jpg

topmenu_blog_btn.jpg

535 ms

top_main_img.jpg

top_main_img.jpg

1087 ms

top_siteupdata_bg02.png

top_siteupdata_bg02.png

662 ms

top_blogupdata_bg.png

top_blogupdata_bg.png

690 ms

btn_joint-bd3.jpg

btn_joint-bd3.jpg

709 ms

copyright_img.gif

copyright_img.gif

713 ms

bn_ponican.gif

bn_ponican.gif

834 ms

spacer.gif

spacer.gif

861 ms

bn_lantis.gif

bn_lantis.gif

885 ms

bn_gsc.jpg

bn_gsc.jpg

890 ms

bn_paworks.gif

bn_paworks.gif

1011 ms

wakana_anime_text.gif

wakana_anime_text.gif

1033 ms

bn_onsen.gif

bn_onsen.gif

1061 ms

bn_hibiki.gif

bn_hibiki.gif

1067 ms

bn_ganganjoker.gif

bn_ganganjoker.gif

1187 ms

bn_cospa.gif

bn_cospa.gif

1206 ms

widgets.js

widgets.js

6 ms

fooder_line_bg.gif

fooder_line_bg.gif

1224 ms

fooder_linksarea_bg.gif

fooder_linksarea_bg.gif

1233 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

29 ms

settings

settings

152 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

2 ms

taritarianime

taritarianime

61 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

22 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

25 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

22 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

23 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

23 ms

_buildManifest.js

_buildManifest.js

23 ms

_ssgManifest.js

_ssgManifest.js

22 ms

base.css

base.css

353 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

10 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

10 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

13 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

6 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

13 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

5 ms

pre_txt_img150107_o.png

pre_txt_img150107_o.png

178 ms

topmenu_story_btn_o.jpg

topmenu_story_btn_o.jpg

174 ms

topmenu_chara_btn_o.jpg

topmenu_chara_btn_o.jpg

182 ms

topmenu_staff_btn_o.jpg

topmenu_staff_btn_o.jpg

178 ms

topmenu_onair_btn_o.jpg

topmenu_onair_btn_o.jpg

178 ms

topmenu_goods_btn_o.jpg

topmenu_goods_btn_o.jpg

173 ms

topmenu_special_btn_o.jpg

topmenu_special_btn_o.jpg

346 ms

topmenu_news_btn_o.jpg

topmenu_news_btn_o.jpg

355 ms

topmenu_blog_btn_o.jpg

topmenu_blog_btn_o.jpg

359 ms

Accessibility Review

taritari.jp accessibility score

65

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

taritari.jp best practices score

58

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

taritari.jp 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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Taritari.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Taritari.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

taritari.jp

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