Tools & Wizards About Us
haikyo.co.jp screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

haikyo.co.jp

俳協｜ナレーター・声優・俳優事務所

Page Load Speed

7 sec in total

First Response

650 ms

Resources Loaded

6 sec

Page Rendered

297 ms

haikyo.co.jp screenshot

About Website

Visit haikyo.co.jp now to see the best up-to-date Haikyo content for Japan and also check out these interesting facts you probably never knew about haikyo.co.jp

東京俳優生活協同組合。ナレーター、声優、俳優、MC、DJのマネジメントを行っているプロダクションです。

Visit haikyo.co.jp

Key Findings

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

haikyo.co.jp performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

haikyo.co.jp

650 ms

haikyo.co.jp

715 ms

cmn_layout.css

172 ms

cmn_style.css

343 ms

style.css

511 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 95% of them (74 requests) were addressed to the original Haikyo.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Haikyo.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.5 kB (4%)

Content Size

3.6 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 34.4 kB

  • Original 41.3 kB
  • After minification 38.1 kB
  • After compression 6.9 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 34.4 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 62.0 kB

  • Original 3.5 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. Haikyo images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 32.0 kB

  • Original 105.7 kB
  • After minification 105.7 kB
  • After compression 73.7 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 32.0 kB or 30% of the original size.

CSS Optimization

-37%

Potential reduce by 4.2 kB

  • Original 11.2 kB
  • After minification 11.2 kB
  • After compression 7.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. Haikyo.co.jp needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (8%)

Requests Now

76

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

haikyo.co.jp

haikyo.co.jp

650 ms

haikyo.co.jp

haikyo.co.jp

715 ms

cmn_layout.css

cmn_layout.css

172 ms

cmn_style.css

cmn_style.css

343 ms

style.css

style.css

511 ms

jquery.js

jquery.js

683 ms

common.js

common.js

513 ms

jquery.bxslider.js

jquery.bxslider.js

514 ms

jquery.bxslider2.js

jquery.bxslider2.js

693 ms

jquery.bxslider3.js

jquery.bxslider3.js

708 ms

analytics.js

analytics.js

76 ms

logo_header01.gif

logo_header01.gif

180 ms

ico_news01.gif

ico_news01.gif

178 ms

ico_contact01.gif

ico_contact01.gif

179 ms

ico_privacy01.gif

ico_privacy01.gif

178 ms

gnavi.gif

gnavi.gif

184 ms

img_slider01.png

img_slider01.png

1384 ms

img_slider02.png

img_slider02.png

1707 ms

img_slider03.png

img_slider03.png

1709 ms

h2_index01.gif

h2_index01.gif

347 ms

s13040.jpg

s13040.jpg

349 ms

s10.jpg

s10.jpg

361 ms

s12236-7.jpg

s12236-7.jpg

516 ms

s12891-4.jpg

s12891-4.jpg

519 ms

s12765-2.jpg

s12765-2.jpg

538 ms

s11570.jpg

s11570.jpg

687 ms

s13118-2.jpg

s13118-2.jpg

690 ms

s13083.jpg

s13083.jpg

715 ms

h2_index02.gif

h2_index02.gif

858 ms

btn_news01_no.gif

btn_news01_no.gif

859 ms

ico_talent01.gif

ico_talent01.gif

891 ms

bnr_index_news01.jpg

bnr_index_news01.jpg

1027 ms

bnr_index_news02.jpg

bnr_index_news02.jpg

1201 ms

bnr_index_news04.jpg

bnr_index_news04.jpg

1068 ms

bnr_index_news05.jpg

bnr_index_news05.jpg

1367 ms

h2_index03.gif

h2_index03.gif

1245 ms

bnr_haikyo01.jpg

bnr_haikyo01.jpg

1543 ms

links_icon.png

links_icon.png

1421 ms

zororitakara_banner.png

zororitakara_banner.png

1537 ms

bnr_haikyo03.jpg

bnr_haikyo03.jpg

1554 ms

h2_index04.gif

h2_index04.gif

1598 ms

bnr_index_link07.jpg

bnr_index_link07.jpg

1709 ms

bnr_tominaga.png

bnr_tominaga.png

3761 ms

bnr_kajiwara.jpg

bnr_kajiwara.jpg

1757 ms

bnr_waki.jpg

bnr_waki.jpg

3898 ms

bnr_H4Krogo.jpg

bnr_H4Krogo.jpg

2215 ms

bnr_cait-c.png

bnr_cait-c.png

1877 ms

collect

collect

12 ms

collect

collect

29 ms

js

js

60 ms

bnr_sugutahina.jpg

bnr_sugutahina.jpg

1709 ms

bg_dot_x01.gif

bg_dot_x01.gif

1756 ms

btn_pagetop01_no.gif

btn_pagetop01_no.gif

1875 ms

txt_footer_links101.gif

txt_footer_links101.gif

1878 ms

txt_footer_links102.gif

txt_footer_links102.gif

1922 ms

txt_footer_links103.gif

txt_footer_links103.gif

1876 ms

ico_blank01.gif

ico_blank01.gif

1877 ms

txt_footer_links104.gif

txt_footer_links104.gif

1916 ms

txt_footer_links201.gif

txt_footer_links201.gif

1873 ms

ico_square01.gif

ico_square01.gif

1873 ms

txt_footer_links201_01.gif

txt_footer_links201_01.gif

1857 ms

txt_footer_links201_02.gif

txt_footer_links201_02.gif

1762 ms

txt_footer_links201_03.gif

txt_footer_links201_03.gif

1869 ms

txt_footer_links201_04.gif

txt_footer_links201_04.gif

1847 ms

txt_footer_links201_05.gif

txt_footer_links201_05.gif

1708 ms

txt_footer_links301.gif

txt_footer_links301.gif

1761 ms

txt_footer_links301_01.gif

txt_footer_links301_01.gif

1837 ms

txt_footer_links301_02.gif

txt_footer_links301_02.gif

1704 ms

txt_footer_links301_03.gif

txt_footer_links301_03.gif

1667 ms

txt_footer_links301_04.gif

txt_footer_links301_04.gif

1592 ms

txt_footer_links301_05.gif

txt_footer_links301_05.gif

1652 ms

txt_footer_links401.gif

txt_footer_links401.gif

1534 ms

txt_footer_links402.gif

txt_footer_links402.gif

1522 ms

txt_footer_links403.gif

txt_footer_links403.gif

1543 ms

logo_footer01.gif

logo_footer01.gif

1529 ms

btn_news01_on.gif

btn_news01_on.gif

1529 ms

btn_pagetop01_on.gif

btn_pagetop01_on.gif

1520 ms

btn_pager01.png

btn_pager01.png

1539 ms

Accessibility Review

haikyo.co.jp accessibility score

88

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

haikyo.co.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

haikyo.co.jp SEO score

69

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

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 Haikyo.co.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 Haikyo.co.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

haikyo.co.jp

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