Tools & Wizards About Us
toriho-dai.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

toriho-dai.com

403 Error - Forbidden

Page Load Speed

5.3 sec in total

First Response

515 ms

Resources Loaded

4.4 sec

Page Rendered

357 ms

toriho-dai.com screenshot

About Website

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

フリー素材！ネットショップ、ECサイトに最適！！｜新規開店、リニューアルなどにボタン、アイコン、バナーなどなど、必要な素材がすべて無料！商用利用可！加工OK！

Visit toriho-dai.com

Key Findings

We analyzed Toriho-dai.com page load time and found that the first response time was 515 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

toriho-dai.com performance score

0

Network Requests Diagram

toriho-dai.com

515 ms

www.toriho-dai.com

703 ms

styles.css

164 ms

mt.js

333 ms

over.js

324 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 49% of them (64 requests) were addressed to the original Toriho-dai.com, 5% (7 requests) were made to Googleads.g.doubleclick.net and 5% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Www29.a8.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.5 kB (65%)

Content Size

523.7 kB

After Optimization

181.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Toriho-dai.com main page is 523.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 362.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 34.2 kB

  • Original 44.6 kB
  • After minification 40.9 kB
  • After compression 10.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 34.2 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 817 B

  • Original 47.5 kB
  • After minification 46.7 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. Toriho Dai images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 248.8 kB

  • Original 362.6 kB
  • After minification 336.6 kB
  • After compression 113.8 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 248.8 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 58.6 kB

  • Original 69.1 kB
  • After minification 34.5 kB
  • After compression 10.4 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. Toriho-dai.com needs all CSS files to be minified and compressed as it can save up to 58.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (65%)

Requests Now

101

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toriho-dai.com

toriho-dai.com

515 ms

www.toriho-dai.com

www.toriho-dai.com

703 ms

styles.css

styles.css

164 ms

mt.js

mt.js

333 ms

over.js

over.js

324 ms

show_ads.js

show_ads.js

9 ms

styles.css

styles.css

173 ms

addclips.js

addclips.js

843 ms

form.php

form.php

589 ms

0702c2038140b24284e2a851227866d0f163ea36

0702c2038140b24284e2a851227866d0f163ea36

356 ms

over.js

over.js

195 ms

mt.js

mt.js

518 ms

0-import.css

0-import.css

209 ms

0-import.css

0-import.css

180 ms

help.css

help.css

173 ms

sio.css

sio.css

373 ms

blog.css

blog.css

299 ms

1-element.css

1-element.css

322 ms

2-class.css

2-class.css

324 ms

3-context.css

3-context.css

328 ms

4-layout.css

4-layout.css

344 ms

5-module.css

5-module.css

475 ms

1-subSkin.css

1-subSkin.css

175 ms

mod_gNavi.css

mod_gNavi.css

191 ms

mod_multiCol-Type1.css

mod_multiCol-Type1.css

186 ms

2-singleUtilities.css

2-singleUtilities.css

172 ms

top_back.png

top_back.png

187 ms

B001JJCKC2.09.TZZZZZZZ.jpg

B001JJCKC2.09.TZZZZZZZ.jpg

71 ms

ir

ir

185 ms

0.gif

0.gif

794 ms

bgt

bgt

1289 ms

0.gif

0.gif

344 ms

B001JJCKEU.09.TZZZZZZZ.jpg

B001JJCKEU.09.TZZZZZZZ.jpg

69 ms

top_header_back.gif

top_header_back.gif

183 ms

top_header.gif

top_header.gif

210 ms

index_h2_back.png

index_h2_back.png

336 ms

top_img.png

top_img.png

334 ms

guide_1.gif

guide_1.gif

366 ms

guide_2.gif

guide_2.gif

381 ms

index_h3_4.gif

index_h3_4.gif

363 ms

new.gif

new.gif

425 ms

step4_11.gif

step4_11.gif

492 ms

time5_11.gif

time5_11.gif

494 ms

return1_11.gif

return1_11.gif

571 ms

up.gif

up.gif

567 ms

index_h3_2.gif

index_h3_2.gif

554 ms

index_h3_3.gif

index_h3_3.gif

623 ms

favorite_on.gif

favorite_on.gif

688 ms

sideblog_bana.gif

sideblog_bana.gif

689 ms

cus_banner.gif

cus_banner.gif

745 ms

ca-pub-7509083233701676.js

ca-pub-7509083233701676.js

58 ms

zrt_lookup.html

zrt_lookup.html

47 ms

show_ads_impl.js

show_ads_impl.js

63 ms

arrow0101.gif

arrow0101.gif

194 ms

tittle_arrow.gif

tittle_arrow.gif

700 ms

addclips.css

addclips.css

524 ms

addclips_0.gif

addclips_0.gif

508 ms

ads

ads

144 ms

arrow5_6.gif

arrow5_6.gif

653 ms

osd.js

osd.js

11 ms

ads

ads

147 ms

ads

ads

190 ms

top_header_back.gif

top_header_back.gif

218 ms

top_back.png

top_back.png

200 ms

ads

ads

145 ms

top_header.gif

top_header.gif

348 ms

abg.js

abg.js

28 ms

top_img.png

top_img.png

571 ms

index_h2_back.png

index_h2_back.png

234 ms

index_h3_4.gif

index_h3_4.gif

197 ms

guide_1.gif

guide_1.gif

204 ms

guide_2.gif

guide_2.gif

242 ms

new.gif

new.gif

294 ms

step4_11.gif

step4_11.gif

231 ms

time5_11.gif

time5_11.gif

247 ms

index_h3_2.gif

index_h3_2.gif

198 ms

up.gif

up.gif

251 ms

return1_11.gif

return1_11.gif

333 ms

brmark.gif

brmark.gif

405 ms

icon_feed.gif

icon_feed.gif

305 ms

ads

ads

227 ms

index_h3_3.gif

index_h3_3.gif

288 ms

ga.js

ga.js

39 ms

__utm.gif

__utm.gif

11 ms

favorite_on.gif

favorite_on.gif

236 ms

sideblog_bana.gif

sideblog_bana.gif

595 ms

tittle_arrow.gif

tittle_arrow.gif

340 ms

cus_banner.gif

cus_banner.gif

329 ms

arrow5_6.gif

arrow5_6.gif

282 ms

128 ms

adj

adj

106 ms

beacon

beacon

92 ms

27 ms

0

0

90 ms

pixel

pixel

25 ms

lidar.js

lidar.js

26 ms

sbhK2lTE.js

sbhK2lTE.js

23 ms

dvbs_src.js

dvbs_src.js

185 ms

verify_selector.js

verify_selector.js

158 ms

blank.gif

blank.gif

149 ms

pixel

pixel

56 ms

pixel

pixel

56 ms

cTrvNaRi.html

cTrvNaRi.html

27 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

26 ms

bst2tv3.html

bst2tv3.html

166 ms

verify.js

verify.js

53 ms

sd

sd

36 ms

click%253Fd%253DAPEucNVCyjDkD-uRpx1CJGoyid1Z5VvpUO9w9ZP0cZwtZe5Xt204ROD686qGbEl0p0YJ3lLvqot5_j63GVih_W96sismuFfQrg%2526r1%253D;ord=1456765540;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

click%253Fd%253DAPEucNVCyjDkD-uRpx1CJGoyid1Z5VvpUO9w9ZP0cZwtZe5Xt204ROD686qGbEl0p0YJ3lLvqot5_j63GVih_W96sismuFfQrg%2526r1%253D;ord=1456765540;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

61 ms

verifyr.js

verifyr.js

36 ms

beacon.js

beacon.js

32 ms

0

0

12 ms

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

78 ms

dvtp_src.js

dvtp_src.js

59 ms

durly.js

durly.js

263 ms

dvtp_src_internal25.js

dvtp_src_internal25.js

56 ms

OptiFree_160x600.html

OptiFree_160x600.html

144 ms

t2tv7.html

t2tv7.html

99 ms

visit.js

visit.js

65 ms

copy.png

copy.png

11 ms

water.jpg

water.jpg

26 ms

packs.jpg

packs.jpg

38 ms

legal.gif

legal.gif

35 ms

ba.js

ba.js

48 ms

4.gif

4.gif

76 ms

avs5634.js

avs5634.js

49 ms

event.gif

event.gif

60 ms

query.js

query.js

58 ms

event.gif

event.gif

55 ms

52158.js

52158.js

57 ms

event.jpg

event.jpg

29 ms

query.js

query.js

35 ms

SEO Factors

toriho-dai.com SEO score

0

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 Toriho-dai.com 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 Toriho-dai.com 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

toriho-dai.com

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