Tools & Wizards About Us
etotama.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

etotama.com

TVアニメ「えとたま」公式サイト

Page Load Speed

6.8 sec in total

First Response

1.4 sec

Resources Loaded

5 sec

Page Rendered

397 ms

etotama.com screenshot

About Website

Visit etotama.com now to see the best up-to-date Etotama content for Japan and also check out these interesting facts you probably never knew about etotama.com

「白組」と「タブリエ・コミュニケーションズ」がタッグを組んだオリジナルTVアニメ！

Visit etotama.com

Key Findings

We analyzed Etotama.com page load time and found that the first response time was 1.4 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

etotama.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value22.3 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value7,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.554

13/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

etotama.com

1413 ms

reset.css

175 ms

jquery.mCustomScrollbar.css

345 ms

home.css

358 ms

jquery.js

553 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 69% of them (59 requests) were addressed to the original Etotama.com, 24% (20 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Etotama.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.3 kB (10%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-92%

Potential reduce by 178.2 kB

  • Original 194.0 kB
  • After minification 186.0 kB
  • After compression 15.8 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 178.2 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 39.1 kB

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

JavaScript Optimization

-3%

Potential reduce by 2.4 kB

  • Original 75.3 kB
  • After minification 75.3 kB
  • After compression 73.0 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

-26%

Potential reduce by 2.6 kB

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 7.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. Etotama.com needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 26% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

etotama.com

etotama.com

1413 ms

reset.css

reset.css

175 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

345 ms

home.css

home.css

358 ms

jquery.js

jquery.js

553 ms

jquery.easing.js

jquery.easing.js

353 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

360 ms

jquery.imgloaded.js

jquery.imgloaded.js

348 ms

jquery.init.js

jquery.init.js

520 ms

ga.js

ga.js

522 ms

analytics.js

analytics.js

530 ms

body_bg.jpg

body_bg.jpg

1713 ms

gnav_01.png

gnav_01.png

528 ms

gnav_icon.png

gnav_icon.png

530 ms

gnav_02.png

gnav_02.png

528 ms

gnav_03.png

gnav_03.png

529 ms

gnav_04.png

gnav_04.png

527 ms

gnav_05.png

gnav_05.png

530 ms

gnav_06.png

gnav_06.png

531 ms

gnav_07.png

gnav_07.png

530 ms

gnav_08.png

gnav_08.png

531 ms

gnav_09.png

gnav_09.png

532 ms

gnav_10.png

gnav_10.png

532 ms

gnav_11.png

gnav_11.png

579 ms

gnav_12.png

gnav_12.png

580 ms

gnav_13.png

gnav_13.png

580 ms

gnav_logo.png

gnav_logo.png

878 ms

main_image_char_rebroad.png

main_image_char_rebroad.png

2541 ms

main_image_frame.png

main_image_frame.png

704 ms

main_image_frame_txt11.png

main_image_frame_txt11.png

885 ms

wiget_bg_news.gif

wiget_bg_news.gif

722 ms

wiget_icon_news.png

wiget_icon_news.png

883 ms

widget_ttl_news.gif

widget_ttl_news.gif

889 ms

wiget_bg_calendar.gif

wiget_bg_calendar.gif

1054 ms

wiget_icon_calendar.png

wiget_icon_calendar.png

1186 ms

widget_ttl_calendar.gif

widget_ttl_calendar.gif

1061 ms

wiget_bg_music.gif

wiget_bg_music.gif

1064 ms

wiget_icon_music.png

wiget_icon_music.png

1231 ms

widget_ttl_music.gif

widget_ttl_music.gif

1236 ms

jkt_01.jpg

jkt_01.jpg

1933 ms

jkt_02.jpg

jkt_02.jpg

2057 ms

jkt_03.jpg

jkt_03.jpg

2273 ms

jkt_04.jpg

jkt_04.jpg

2276 ms

jkt_05.jpg

jkt_05.jpg

2041 ms

jkt_06.jpg

jkt_06.jpg

2456 ms

wiget_bg_twitter.gif

wiget_bg_twitter.gif

2212 ms

widgets.js

widgets.js

480 ms

wiget_icon_twitter.png

wiget_icon_twitter.png

1712 ms

widget_ttl_twitter.gif

widget_ttl_twitter.gif

1862 ms

fnav_banner01.jpg

fnav_banner01.jpg

2057 ms

fnav_banner02.jpg

fnav_banner02.jpg

1926 ms

fnav_banner03.jpg

fnav_banner03.jpg

2100 ms

fnav_banner04.jpg

fnav_banner04.jpg

2034 ms

fnav_icon_tw.png

fnav_icon_tw.png

2101 ms

fnav_icon_fb.png

fnav_icon_fb.png

2104 ms

fnav_icon_gp.png

fnav_icon_gp.png

2521 ms

icon_calendar_event.png

icon_calendar_event.png

2204 ms

icon_calendar_tv.png

icon_calendar_tv.png

2232 ms

collect

collect

66 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

48 ms

icon_calendar_movie.png

icon_calendar_movie.png

2229 ms

icon_calendar_music.png

icon_calendar_music.png

2228 ms

fnav_bg_border.gif

fnav_bg_border.gif

2231 ms

settings

settings

109 ms

js

js

79 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

9 ms

embeds

embeds

29 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

16 ms

etotama_anime

etotama_anime

801 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

9 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

8 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

12 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

12 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

15 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

14 ms

_buildManifest.js

_buildManifest.js

13 ms

_ssgManifest.js

_ssgManifest.js

15 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

11 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

5 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

20 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

21 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

18 ms

Accessibility Review

etotama.com accessibility score

60

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.

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

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

etotama.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

etotama.com SEO score

92

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

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 Etotama.com 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 Etotama.com 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

etotama.com

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