Tools & Wizards About Us
itoman.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

itoman.com

【公式】イトマンスイミングスクール 水泳教室

Page Load Speed

11.2 sec in total

First Response

2.9 sec

Resources Loaded

7.9 sec

Page Rendered

458 ms

itoman.com screenshot

About Website

Visit itoman.com now to see the best up-to-date Itoman content for Japan and also check out these interesting facts you probably never knew about itoman.com

大橋悠依選手、入江陵介選手、塩浦慎理選手、中村克選手らオリンピック選手も所属するスイミングスクールです。ベビーから大人まで一人一人に合わせた水泳指導で、心と体を育みます。今なら2日間受講無料招待中！

Visit itoman.com

Key Findings

We analyzed Itoman.com page load time and found that the first response time was 2.9 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

itoman.com performance score

0

Network Requests Diagram

itoman.com

2866 ms

redirect_rev.js

1226 ms

index.css

492 ms

jquery-min.js

1439 ms

functions.js

336 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 78% of them (93 requests) were addressed to the original Itoman.com, 12% (14 requests) were made to Toshin.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Itoman.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.1 kB (30%)

Content Size

1.2 MB

After Optimization

809.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 134.5 kB

  • Original 155.8 kB
  • After minification 144.9 kB
  • After compression 21.3 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 134.5 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 32.5 kB

  • Original 766.3 kB
  • After minification 733.8 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. Itoman images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 170.8 kB

  • Original 221.0 kB
  • After minification 155.6 kB
  • After compression 50.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 170.8 kB or 77% of the original size.

CSS Optimization

-79%

Potential reduce by 16.3 kB

  • Original 20.5 kB
  • After minification 14.5 kB
  • After compression 4.3 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. Itoman.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (36%)

Requests Now

113

After Optimization

72

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

itoman.com

itoman.com

2866 ms

redirect_rev.js

redirect_rev.js

1226 ms

index.css

index.css

492 ms

jquery-min.js

jquery-min.js

1439 ms

functions.js

functions.js

336 ms

joc_win.js

joc_win.js

349 ms

swfobject.js

swfobject.js

1695 ms

jquery.js

jquery.js

1476 ms

jquery.timers.js

jquery.timers.js

780 ms

koushakensaku.css

koushakensaku.css

380 ms

tab.js

tab.js

344 ms

reset.css

reset.css

178 ms

share.css

share.css

497 ms

ban_top.gif

ban_top.gif

185 ms

toiawase.jpg

toiawase.jpg

241 ms

syunki_3.jpg

syunki_3.jpg

1151 ms

20140830_joc.png

20140830_joc.png

637 ms

forChild.png

forChild.png

332 ms

baby.jpg

baby.jpg

338 ms

youji.jpg

youji.jpg

337 ms

midStu.jpg

midStu.jpg

346 ms

coach.jpg

coach.jpg

651 ms

taiso.png

taiso.png

735 ms

kodomojuku.png

kodomojuku.png

696 ms

forAdule.png

forAdule.png

681 ms

sankaku.png

sankaku.png

851 ms

fitness.png

fitness.png

990 ms

LeftButton.png

LeftButton.png

1028 ms

RightButton.png

RightButton.png

1017 ms

ListDisp_On.png

ListDisp_On.png

1034 ms

CenterBox_Top.png

CenterBox_Top.png

1046 ms

CenterBox_Left.png

CenterBox_Left.png

1193 ms

CenterBox_Right.png

CenterBox_Right.png

1311 ms

CenterBox_Bottom.png

CenterBox_Bottom.png

1355 ms

TopButton.png

TopButton.png

1379 ms

BottomButton.png

BottomButton.png

1359 ms

name_text.jpg

name_text.jpg

1379 ms

fitness.jpg

fitness.jpg

1504 ms

hokkaido.jpg

hokkaido.jpg

1663 ms

sankaku.jpg

sankaku.jpg

1691 ms

tohoku.jpg

tohoku.jpg

1698 ms

kanto.jpg

kanto.jpg

1690 ms

tokai.jpg

tokai.jpg

1712 ms

kinki.jpg

kinki.jpg

1814 ms

top_fitness_201409.jpg

top_fitness_201409.jpg

1972 ms

top_baby.jpg

top_baby.jpg

2499 ms

joc_summer.jpg

joc_summer.jpg

2356 ms

announce_header.gif

announce_header.gif

2036 ms

announce_all_on.jpg

announce_all_on.jpg

2065 ms

announce_hokkaido_off.jpg

announce_hokkaido_off.jpg

2120 ms

gtm.js

gtm.js

76 ms

announce_tohoku_off.jpg

announce_tohoku_off.jpg

2308 ms

conversion_async.js

conversion_async.js

17 ms

analytics.js

analytics.js

23 ms

44 ms

collect

collect

10 ms

collect

collect

65 ms

collect

collect

23 ms

collect

collect

55 ms

36 ms

ga-audiences

ga-audiences

19 ms

ga-audiences

ga-audiences

25 ms

announce_kanto_off.jpg

announce_kanto_off.jpg

2024 ms

announce_tokai_off.jpg

announce_tokai_off.jpg

2055 ms

announce_kinki_off.jpg

announce_kinki_off.jpg

2101 ms

header.jpg

header.jpg

2609 ms

1.png

1.png

350 ms

2.png

2.png

484 ms

nagase_inf.jpg

nagase_inf.jpg

210 ms

3.png

3.png

524 ms

4.png

4.png

536 ms

5.png

5.png

541 ms

6.png

6.png

562 ms

7.png

7.png

393 ms

8.png

8.png

518 ms

9.png

9.png

576 ms

10.png

10.png

688 ms

11.png

11.png

702 ms

12.png

12.png

712 ms

jquery.csv.js

jquery.csv.js

722 ms

s_code.js

s_code.js

2153 ms

sitecatalyst.js

sitecatalyst.js

2064 ms

tracking_code.js

tracking_code.js

2389 ms

siteLogo.png

siteLogo.png

2231 ms

mainNavi_20091102.gif

mainNavi_20091102.gif

2631 ms

link_footer.gif

link_footer.gif

2277 ms

container_base.jpg

container_base.jpg

3151 ms

inner_base.png

inner_base.png

2232 ms

section_base.gif

section_base.gif

2264 ms

Bg.jpg

Bg.jpg

2491 ms

Arrow.gif

Arrow.gif

2366 ms

Bg.png

Bg.png

3008 ms

RightButtonBg.png

RightButtonBg.png

2436 ms

ListDisp_Bg.png

ListDisp_Bg.png

2333 ms

link_sensyu.jpgf

link_sensyu.jpgf

2376 ms

whatsnew_header.gif

whatsnew_header.gif

2502 ms

link_whatsnew.gif

link_whatsnew.gif

2566 ms

sensyu_head.jpg

sensyu_head.jpg

2910 ms

sensyu_all_on.jpg

sensyu_all_on.jpg

2564 ms

sensyu_hokkaido_off.jpg

sensyu_hokkaido_off.jpg

2527 ms

sensyu_tohoku_off.jpg

sensyu_tohoku_off.jpg

2589 ms

sensyu_kanto_off.jpg

sensyu_kanto_off.jpg

2643 ms

sensyu_tokai_off.jpg

sensyu_tokai_off.jpg

2665 ms

sensyu_kinki_off.jpg

sensyu_kinki_off.jpg

2714 ms

sensyu_syokai_off.jpg

sensyu_syokai_off.jpg

2840 ms

sensyu_blog_off.jpg

sensyu_blog_off.jpg

2646 ms

sensyu_irie.jpg

sensyu_irie.jpg

2746 ms

sensyu_araki.jpg

sensyu_araki.jpg

2887 ms

sensyu_sotodate.jpg

sensyu_sotodate.jpg

2702 ms

schoolinfo_header.gif

schoolinfo_header.gif

2472 ms

forchildren.jpg

forchildren.jpg

2597 ms

foradult.jpg

foradult.jpg

2629 ms

taiso.jpg

taiso.jpg

2720 ms

fitness.jpg

fitness.jpg

2709 ms

catch_taikenjugyou.gif

catch_taikenjugyou.gif

3033 ms

panel_water.jpg

panel_water.jpg

2739 ms

panel_aed.jpg

panel_aed.jpg

2597 ms

service_golf.gif

service_golf.gif

2420 ms

NowTimeLoadVars_itomanTopMainvisual.php

NowTimeLoadVars_itomanTopMainvisual.php

186 ms

SEO Factors

itoman.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itoman.com 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 Itoman.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

itoman.com

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