Tools & Wizards About Us
taro.org screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

taro.org

河野太郎公式サイト 日本を前に進める。温もりのある国へ｜衆議院議員 河野太郎公式サイト

Page Load Speed

6.5 sec in total

First Response

544 ms

Resources Loaded

5.7 sec

Page Rendered

296 ms

taro.org screenshot

About Website

Click here to check amazing Taro content for Japan. Otherwise, check out these important facts you probably never knew about taro.org

河野太郎公式サイト 日本を前に進める。温もりのある国へ

Visit taro.org

Key Findings

We analyzed Taro.org page load time and found that the first response time was 544 ms and then it took 5.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

taro.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value24.8 s

0/100

10%

TBT (Total Blocking Time)

Value5,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value36.1 s

0/100

10%

Network Requests Diagram

taro.org

544 ms

www.taro.org

1203 ms

style.css

194 ms

common.js

633 ms

style.min.css

850 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 42% of them (32 requests) were addressed to the original Taro.org, 14% (11 requests) were made to Platform.twitter.com and 13% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Taro.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.5 kB (2%)

Content Size

2.2 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taro.org 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.8 kB

  • Original 48.5 kB
  • After minification 47.4 kB
  • After compression 11.7 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 36.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 4.0 kB

  • Original 1.7 MB
  • After minification 1.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. Taro images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.7 kB

  • Original 443.0 kB
  • After minification 442.7 kB
  • After compression 439.3 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

-8%

Potential reduce by 5.0 kB

  • Original 58.7 kB
  • After minification 58.7 kB
  • After compression 53.7 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. Taro.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taro.org

taro.org

544 ms

www.taro.org

www.taro.org

1203 ms

style.css

style.css

194 ms

common.js

common.js

633 ms

style.min.css

style.min.css

850 ms

styles.css

styles.css

681 ms

default.css

default.css

690 ms

js

js

69 ms

js

js

121 ms

gmogs_image_130-66_ja.js

gmogs_image_130-66_ja.js

712 ms

gs_flash_130-66_ja.js

gs_flash_130-66_ja.js

1366 ms

platform.js

platform.js

35 ms

index.js

index.js

714 ms

index.js

index.js

732 ms

api.js

api.js

72 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

951 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

952 ms

wp-polyfill.min.js

wp-polyfill.min.js

991 ms

index.js

index.js

991 ms

23 ms

analytics.js

analytics.js

122 ms

js

js

136 ms

bg.jpg

bg.jpg

839 ms

headbot.png

headbot.png

186 ms

gmenuli.png

gmenuli.png

184 ms

main.png

main.png

1494 ms

pickupbg.jpg

pickupbg.jpg

546 ms

pickup_image_blog.jpg

pickup_image_blog.jpg

781 ms

pickup_image_movie.jpg

pickup_image_movie.jpg

576 ms

pickup_image_policy.jpg

pickup_image_policy.jpg

819 ms

woodbg.jpg

woodbg.jpg

1048 ms

h3_bg.png

h3_bg.png

780 ms

jimin-nyuto.png

jimin-nyuto.png

952 ms

sidebanner_magazine.jpg

sidebanner_magazine.jpg

950 ms

sidebanne_channe.jpg

sidebanne_channe.jpg

1005 ms

sidebanner_book.jpg

sidebanner_book.jpg

1028 ms

sidebg.jpg

sidebg.jpg

1127 ms

dot.png

dot.png

1134 ms

btn_facebook.png

btn_facebook.png

1186 ms

btn_insta.png

btn_insta.png

1211 ms

button_mail.jpg

button_mail.jpg

1252 ms

gs_noscript_130-66_ja.gif

gs_noscript_130-66_ja.gif

127 ms

cse.js

cse.js

100 ms

widgets.js

widgets.js

107 ms

collect

collect

20 ms

collect

collect

31 ms

cse_element__ja.js

cse_element__ja.js

19 ms

default+ja.css

default+ja.css

11 ms

default.css

default.css

10 ms

recaptcha__en.js

recaptcha__en.js

87 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

144 ms

async-ads.js

async-ads.js

47 ms

branding.png

branding.png

36 ms

clear.png

clear.png

10 ms

nav_logo114.png

nav_logo114.png

12 ms

anchor

anchor

36 ms

settings

settings

129 ms

styles__ltr.css

styles__ltr.css

6 ms

recaptcha__en.js

recaptcha__en.js

14 ms

Dahk90Fxhr1MEtfyZ-6_j6N-qVuiwfy-NjSFsUln5nQ.js

Dahk90Fxhr1MEtfyZ-6_j6N-qVuiwfy-NjSFsUln5nQ.js

73 ms

webworker.js

webworker.js

70 ms

logo_48.png

logo_48.png

57 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

47 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

51 ms

recaptcha__en.js

recaptcha__en.js

10 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

26 ms

konotarogomame

konotarogomame

1164 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

23 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

49 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

91 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

77 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

78 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

89 ms

_buildManifest.js

_buildManifest.js

90 ms

_ssgManifest.js

_ssgManifest.js

91 ms

Accessibility Review

taro.org accessibility score

84

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

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

taro.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

taro.org SEO score

90

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

High

Tap targets are not sized appropriately

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 Taro.org 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 Taro.org 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

taro.org

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