Tools & Wizards About Us
hiro-ishikawa.net screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

hiro-ishikawa.net

参議院議員 石川ひろたか オフィシャルウェブサイト

Page Load Speed

13.3 sec in total

First Response

615 ms

Resources Loaded

12 sec

Page Rendered

685 ms

hiro-ishikawa.net screenshot

About Website

Click here to check amazing Hiro Ishikawa content. Otherwise, check out these important facts you probably never knew about hiro-ishikawa.net

大阪が生んだ、世界が鍛えた、実行力　参議院議員 石川ひろたか オフィシャルウェブサイト

Visit hiro-ishikawa.net

Key Findings

We analyzed Hiro-ishikawa.net page load time and found that the first response time was 615 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

hiro-ishikawa.net performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.735

6/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

hiro-ishikawa.net

615 ms

www.hiro-ishikawa.net

1248 ms

import.css

504 ms

modernizr.js

672 ms

core.js

1502 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 57% of them (51 requests) were addressed to the original Hiro-ishikawa.net, 12% (11 requests) were made to Pbs.twimg.com and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.3 sec) belongs to the original domain Hiro-ishikawa.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (43%)

Content Size

3.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hiro-ishikawa.net main page is 3.1 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 11.6 kB

  • Original 16.2 kB
  • After minification 14.6 kB
  • After compression 4.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 11.6 kB or 72% of the original size.

Image Optimization

-32%

Potential reduce by 710.6 kB

  • Original 2.2 MB
  • After minification 1.5 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. Obviously, Hiro Ishikawa needs image optimization as it can save up to 710.6 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 356.3 kB

  • Original 541.5 kB
  • After minification 506.0 kB
  • After compression 185.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 356.3 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 265.1 kB

  • Original 316.7 kB
  • After minification 298.2 kB
  • After compression 51.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. Hiro-ishikawa.net needs all CSS files to be minified and compressed as it can save up to 265.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (27%)

Requests Now

77

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hiro-ishikawa.net

hiro-ishikawa.net

615 ms

www.hiro-ishikawa.net

www.hiro-ishikawa.net

1248 ms

import.css

import.css

504 ms

modernizr.js

modernizr.js

672 ms

core.js

core.js

1502 ms

common.js

common.js

527 ms

TweenMax.min.js

TweenMax.min.js

1281 ms

loader.js

loader.js

554 ms

config.js

config.js

1168 ms

ytplayer.js

ytplayer.js

1065 ms

base.css

base.css

554 ms

contents.css

contents.css

1209 ms

css

css

51 ms

bg.gif

bg.gif

541 ms

intro_bg.gif

intro_bg.gif

540 ms

img_main1.jpg

img_main1.jpg

6170 ms

name_1.png

name_1.png

660 ms

name_2.png

name_2.png

660 ms

name_3.png

name_3.png

662 ms

btn_scroll.png

btn_scroll.png

1236 ms

name.png

name.png

1264 ms

i_line.png

i_line.png

1265 ms

i_twitter.png

i_twitter.png

1267 ms

i_fb.png

i_fb.png

1291 ms

bg_top.gif

bg_top.gif

1737 ms

bg_movie.gif

bg_movie.gif

1936 ms

i_start.png

i_start.png

1812 ms

ban_supporter.jpg

ban_supporter.jpg

2931 ms

0316keisai.png

0316keisai.png

7091 ms

650%C3%97400.jpg

650%C3%97400.jpg

8341 ms

ban_mailmaga.jpg

ban_mailmaga.jpg

3313 ms

ban_supporter.jpg

ban_supporter.jpg

3661 ms

ban_radio.jpg

ban_radio.jpg

5088 ms

ban_offitial.jpg

ban_offitial.jpg

4591 ms

ban_youth.gif

ban_youth.gif

4201 ms

ban_zubatto.jpg

ban_zubatto.jpg

5058 ms

ban_fuhonbu.gif

ban_fuhonbu.gif

5116 ms

ban_va.gif

ban_va.gif

5592 ms

ban_komesuke.gif

ban_komesuke.gif

5973 ms

ban_line.gif

ban_line.gif

5654 ms

ban_fb.gif

ban_fb.gif

6091 ms

ban_youtube.gif

ban_youtube.gif

6169 ms

ban_sdd.gif

ban_sdd.gif

6519 ms

f_name.png

f_name.png

6607 ms

logo_komei.gif

logo_komei.gif

6707 ms

widgets.js

widgets.js

178 ms

bg_blog.gif

bg_blog.gif

6690 ms

bg_more.png

bg_more.png

7039 ms

i_next.png

i_next.png

7110 ms

ppse0J9fKSaoxCIIJb33G33uxQAI1Bvm-GxtFNy4yl0.ttf

ppse0J9fKSaoxCIIJb33G33uxQAI1Bvm-GxtFNy4yl0.ttf

91 ms

q9w3H4aeBxj0hZ8Osfi3dytfYakCkPqOMDce0h_3gD8.ttf

q9w3H4aeBxj0hZ8Osfi3dytfYakCkPqOMDce0h_3gD8.ttf

113 ms

ppse0J9fKSaoxCIIJb33GzolfeppZzFSKvLyJNPKLMk.ttf

ppse0J9fKSaoxCIIJb33GzolfeppZzFSKvLyJNPKLMk.ttf

137 ms

ppse0J9fKSaoxCIIJb33GyxQL91WRy8t8mPvAX_dIgA.ttf

ppse0J9fKSaoxCIIJb33GyxQL91WRy8t8mPvAX_dIgA.ttf

170 ms

C6HYlRF50SGJq1XyXj04zwV_pQ1T3xN3K1c3sB361us.ttf

C6HYlRF50SGJq1XyXj04zwV_pQ1T3xN3K1c3sB361us.ttf

171 ms

xgzbb53t8j-Mo-vYa23n5onF5uFdDttMLvmWuJdhhgs.ttf

xgzbb53t8j-Mo-vYa23n5onF5uFdDttMLvmWuJdhhgs.ttf

171 ms

C6HYlRF50SGJq1XyXj04z1FZMcfX2SbzQ69I7OWmkGo.ttf

C6HYlRF50SGJq1XyXj04z1FZMcfX2SbzQ69I7OWmkGo.ttf

211 ms

C6HYlRF50SGJq1XyXj04z306qf9KHRHwsVx7iw5MXmY.ttf

C6HYlRF50SGJq1XyXj04z306qf9KHRHwsVx7iw5MXmY.ttf

166 ms

iframe_api

iframe_api

71 ms

i_totop.png

i_totop.png

7141 ms

analytics.js

analytics.js

102 ms

www-widgetapi.js

www-widgetapi.js

106 ms

collect

collect

62 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

32 ms

UlTXUbN6Nxk

UlTXUbN6Nxk

69 ms

syndication

syndication

99 ms

702713703406284800

702713703406284800

229 ms

www-embed-player-vfl8xM8me.css

www-embed-player-vfl8xM8me.css

29 ms

www-embed-player.js

www-embed-player.js

59 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

34 ms

ad_status.js

ad_status.js

40 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

18 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

17 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

30 ms

i_line_ov.png

i_line_ov.png

6703 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

372 ms

i_twitter_ov.png

i_twitter_ov.png

7056 ms

KB9OsO6u_normal.jpg

KB9OsO6u_normal.jpg

341 ms

vqOI8kao_normal.jpeg

vqOI8kao_normal.jpeg

344 ms

CdqgUwsUEAACfut.jpg:small

CdqgUwsUEAACfut.jpg:small

346 ms

CdlJeT6UAAA_3nw.jpg:small

CdlJeT6UAAA_3nw.jpg:small

348 ms

Cdgj95BUkAEEv_3.jpg:small

Cdgj95BUkAEEv_3.jpg:small

348 ms

CdghOEaUYAEPKKm.jpg:small

CdghOEaUYAEPKKm.jpg:small

345 ms

CdaJgfyUAAAxYu7.jpg:small

CdaJgfyUAAAxYu7.jpg:small

347 ms

CdZ79XrUkAEFLoS.jpg:small

CdZ79XrUkAEFLoS.jpg:small

348 ms

CdYSr3KUEAEmOci.jpg:small

CdYSr3KUEAEmOci.jpg:small

349 ms

CdW6zjHUsAAa6oF.jpg:small

CdW6zjHUsAAa6oF.jpg:small

351 ms

CdWSMlBUsAAeNA_.jpg:small

CdWSMlBUsAAeNA_.jpg:small

349 ms

i_fb_ov.png

i_fb_ov.png

6985 ms

jot

jot

28 ms

Accessibility Review

hiro-ishikawa.net accessibility score

71

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

<frame> or <iframe> elements do not have a title

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

hiro-ishikawa.net 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hiro-ishikawa.net SEO score

100

Search Engine Optimization Advices

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hiro-ishikawa.net 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 Hiro-ishikawa.net 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

hiro-ishikawa.net

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