Tools & Wizards About Us
taiho.co.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

taiho.co.jp

大鵬薬品工業株式会社

Page Load Speed

33.7 sec in total

First Response

339 ms

Resources Loaded

32.7 sec

Page Rendered

729 ms

taiho.co.jp screenshot

About Website

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

大鵬薬品工業株式会社のオフィシャルウェブサイトです。「私たちは人びとの健康を高め 満ち足りた笑顔あふれる 社会づくりに貢献します。」を企業理念に、世界中の人びとに貢献できる企業を目指します。

Visit taiho.co.jp

Key Findings

We analyzed Taiho.co.jp page load time and found that the first response time was 339 ms and then it took 33.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

taiho.co.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.87

4/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

taiho.co.jp

339 ms

taiho.co.jp

1010 ms

common.css

1169 ms

viewport.js

504 ms

library.js

1609 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 58% of them (40 requests) were addressed to the original Taiho.co.jp, 10% (7 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (16.2 sec) relates to the external source Eqc110jrwr.eq.webcdn.stream.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (32%)

Content Size

5.5 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taiho.co.jp main page is 5.5 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. 65% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 44.5 kB

  • Original 55.7 kB
  • After minification 54.0 kB
  • After compression 11.2 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 44.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 5.7 kB

  • Original 2.3 MB
  • After minification 2.3 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. Taiho images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 1.2 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 1.3 MB

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 1.2 MB or 47% of the original size.

CSS Optimization

-92%

Potential reduce by 498.0 kB

  • Original 540.6 kB
  • After minification 470.9 kB
  • After compression 42.6 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. Taiho.co.jp needs all CSS files to be minified and compressed as it can save up to 498.0 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (59%)

Requests Now

64

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taiho.co.jp

taiho.co.jp

339 ms

taiho.co.jp

taiho.co.jp

1010 ms

common.css

common.css

1169 ms

viewport.js

viewport.js

504 ms

library.js

library.js

1609 ms

setting.js

setting.js

506 ms

function.js

function.js

835 ms

common.js

common.js

510 ms

top.css

top.css

1004 ms

swiper-bundle.min.css

swiper-bundle.min.css

842 ms

ga_gtm.js

ga_gtm.js

680 ms

js

js

86 ms

top.js

top.js

533 ms

sync_suggest.js

sync_suggest.js

830 ms

css2

css2

36 ms

css2

css2

52 ms

gtm.js

gtm.js

181 ms

MjQ5Mw%3D%3D%23MTU4MQ%3D%3D%23280%23168%230%233FE120D9E100%23MDoyOjc6YTpmOzEwOzEwOzEw%23

MjQ5Mw%3D%3D%23MTU4MQ%3D%3D%23280%23168%230%233FE120D9E100%23MDoyOjc6YTpmOzEwOzEwOzEw%23

1663 ms

logo_top.webp

logo_top.webp

247 ms

logo_white.svg

logo_white.svg

246 ms

logo.svg

logo.svg

244 ms

i_search2.svg

i_search2.svg

245 ms

i_search2_white.svg

i_search2_white.svg

247 ms

i_contact.svg

i_contact.svg

665 ms

i_contact_white.svg

i_contact_white.svg

663 ms

i_menu.svg

i_menu.svg

664 ms

p_top_keyvisual_01_sp.jpg

p_top_keyvisual_01_sp.jpg

1177 ms

t_top_keyvisual_01_sp.svg

t_top_keyvisual_01_sp.svg

666 ms

p_top_keyvisual_02_sp.jpg

p_top_keyvisual_02_sp.jpg

694 ms

t_top_keyvisual_02_sp.svg

t_top_keyvisual_02_sp.svg

691 ms

t_aboutus_sp.svg

t_aboutus_sp.svg

846 ms

p_top_about-us_sp.jpg

p_top_about-us_sp.jpg

1014 ms

i_arrow3.svg

i_arrow3.svg

690 ms

bg_aboutus_circle1_pc.svg

bg_aboutus_circle1_pc.svg

862 ms

bg_aboutus_circle2_pc.svg

bg_aboutus_circle2_pc.svg

864 ms

p_top_info_medical.jpg

p_top_info_medical.jpg

885 ms

i_arrow3.svg

i_arrow3.svg

1020 ms

p_top_info_user.jpg

p_top_info_user.jpg

1042 ms

p_top_info_healthcare.jpg

p_top_info_healthcare.jpg

1204 ms

p_top_info_healthcare_banner.jpg

p_top_info_healthcare_banner.jpg

1069 ms

p_top_info_topicks_sp.jpg

p_top_info_topicks_sp.jpg

1359 ms

p_youtube.jpg

p_youtube.jpg

1869 ms

bg_contents_pc.jpg

bg_contents_pc.jpg

1216 ms

i_facebook.svg

i_facebook.svg

1242 ms

logo_group.png

logo_group.png

1344 ms

i_blank.svg

i_blank.svg

1378 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

15 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

41 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

41 ms

js

js

62 ms

js

js

167 ms

js

js

228 ms

js

js

226 ms

js

js

225 ms

analytics.js

analytics.js

137 ms

ytag.js

ytag.js

1016 ms

lt.js

lt.js

126 ms

track.js

track.js

1033 ms

collect

collect

296 ms

err.gif

err.gif

825 ms

collect

collect

39 ms

js

js

54 ms

ga-audiences

ga-audiences

81 ms

universe_cookie_sync.html

universe_cookie_sync.html

831 ms

config.json

config.json

170 ms

if.js

if.js

2153 ms

inner.html

inner.html

10154 ms

EQPlayer.js

EQPlayer.js

14905 ms

Inner.js

Inner.js

16194 ms

Accessibility Review

taiho.co.jp accessibility score

96

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

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

taiho.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

taiho.co.jp SEO score

91

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

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

High

Tap targets are not sized appropriately

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

taiho.co.jp

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