Tools & Wizards About Us
izumi-tadashi.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

izumi-tadashi.net

泉忠司　オフィシャルサイト～あらゆる分野で頂点を取り続ける泉忠司～

Page Load Speed

4.2 sec in total

First Response

583 ms

Resources Loaded

3.3 sec

Page Rendered

329 ms

izumi-tadashi.net screenshot

About Website

Visit izumi-tadashi.net now to see the best up-to-date Izumi Tadashi content for Japan and also check out these interesting facts you probably never knew about izumi-tadashi.net

泉忠司　オフィシャルサイト～あらゆる分野で頂点を取り続ける泉忠司～

Visit izumi-tadashi.net

Key Findings

We analyzed Izumi-tadashi.net page load time and found that the first response time was 583 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

izumi-tadashi.net performance score

0

Network Requests Diagram

izumi-tadashi.net

583 ms

import.css

166 ms

jquery1.7.2.min.js

794 ms

script.js

357 ms

jquery.min.js

32 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 65% of them (41 requests) were addressed to the original Izumi-tadashi.net, 14% (9 requests) were made to Calendar.google.com and 6% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Izumi-tadashi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.7 kB (37%)

Content Size

1.5 MB

After Optimization

971.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Izumi-tadashi.net main page is 1.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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 11.3 kB

  • Original 15.6 kB
  • After minification 14.4 kB
  • After compression 4.4 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.3 kB or 72% of the original size.

Image Optimization

-27%

Potential reduce by 314.4 kB

  • Original 1.2 MB
  • After minification 845.1 kB

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, Izumi Tadashi needs image optimization as it can save up to 314.4 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 193.4 kB

  • Original 305.0 kB
  • After minification 304.8 kB
  • After compression 111.5 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 193.4 kB or 63% of the original size.

CSS Optimization

-80%

Potential reduce by 41.6 kB

  • Original 52.1 kB
  • After minification 44.7 kB
  • After compression 10.5 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. Izumi-tadashi.net needs all CSS files to be minified and compressed as it can save up to 41.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (28%)

Requests Now

60

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

izumi-tadashi.net

izumi-tadashi.net

583 ms

import.css

import.css

166 ms

jquery1.7.2.min.js

jquery1.7.2.min.js

794 ms

script.js

script.js

357 ms

jquery.min.js

jquery.min.js

32 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

517 ms

jquery.bxslider.css

jquery.bxslider.css

396 ms

jquery.min.js

jquery.min.js

388 ms

jquery.zrssfeed.min.js

jquery.zrssfeed.min.js

392 ms

bace.css

bace.css

392 ms

rssticker.css

rssticker.css

438 ms

publication.css

publication.css

439 ms

embed

embed

95 ms

load

load

254 ms

bg.jpg

bg.jpg

645 ms

logo.png

logo.png

377 ms

head_contact.png

head_contact.png

584 ms

topnavBg_on.png

topnavBg_on.png

189 ms

topnavBg.png

topnavBg.png

206 ms

3.jpg

3.jpg

1036 ms

2.jpg

2.jpg

964 ms

5.jpg

5.jpg

1069 ms

6.jpg

6.jpg

1086 ms

7.jpg

7.jpg

1693 ms

1.jpg

1.jpg

1147 ms

rank01.jpg

rank01.jpg

1138 ms

top_m2.jpg

top_m2.jpg

1214 ms

rank02.jpg

rank02.jpg

1246 ms

top_m3.jpg

top_m3.jpg

1265 ms

rank03.jpg

rank03.jpg

1304 ms

top_m1.jpg

top_m1.jpg

1313 ms

top_bana_bg.jpg

top_bana_bg.jpg

1555 ms

top_bana01.jpg

top_bana01.jpg

1602 ms

side_13.jpg

side_13.jpg

1444 ms

side_10.jpg

side_10.jpg

1476 ms

side_11.jpg

side_11.jpg

1480 ms

side_12.jpg

side_12.jpg

1623 ms

side_03.jpg

side_03.jpg

1636 ms

side_02.jpg

side_02.jpg

1650 ms

side_04.jpg

side_04.jpg

1728 ms

icon.jpg

icon.jpg

1787 ms

bx_loader.gif

bx_loader.gif

1809 ms

controls.png

controls.png

1798 ms

embed

embed

61 ms

f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled_fastui.css

f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled_fastui.css

4 ms

f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled__en.js

f7e12ba16863d79ebc50b5ad512d0dd5embedcompiled__en.js

24 ms

client.js

client.js

55 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

postmessageRelay

postmessageRelay

43 ms

api.js

api.js

39 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

48 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

46 ms

icon01.jpg

icon01.jpg

1554 ms

logo-plus.png

logo-plus.png

26 ms

googlelogo_color_46x16dp.png

googlelogo_color_46x16dp.png

30 ms

blank.gif

blank.gif

17 ms

menu_arrow_open.gif

menu_arrow_open.gif

7 ms

icon_print.gif

icon_print.gif

9 ms

btn_menu6.gif

btn_menu6.gif

11 ms

combined_v22.png

combined_v22.png

31 ms

proxy.html

proxy.html

59 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

3 ms

events

events

68 ms

SEO Factors

izumi-tadashi.net SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Izumi-tadashi.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Izumi-tadashi.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

izumi-tadashi.net

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