Tools & Wizards About Us
tanutanuchan.seesaa.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tanutanuchan.seesaa.net

元ホストの暴露ブログ・ホストとの恋愛が気になる貴女に！

Page Load Speed

9.4 sec in total

First Response

726 ms

Resources Loaded

8.2 sec

Page Rendered

435 ms

tanutanuchan.seesaa.net screenshot

About Website

Welcome to tanutanuchan.seesaa.net homepage info - get ready to check Tanutanuchan Seesaa best content for Japan right away, or after learning these important things about tanutanuchan.seesaa.net

元ホストの僕が見た夜の世界の裏側やホストクラブの楽しみ方、ホストとの恋愛テクニックなどを暴露していきます。

Visit tanutanuchan.seesaa.net

Key Findings

We analyzed Tanutanuchan.seesaa.net page load time and found that the first response time was 726 ms and then it took 8.7 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

tanutanuchan.seesaa.net performance score

0

Network Requests Diagram

tanutanuchan.seesaa.net

726 ms

styles-index.css

484 ms

user-common.css

416 ms

ad_plugin.js

417 ms

ads.js

7 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Tanutanuchan.seesaa.net, 21% (13 requests) were made to Tanutanuchan.up.seesaa.net and 13% (8 requests) were made to Blog.seesaa.jp. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Spnet2-1.i-mobile.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.0 kB (29%)

Content Size

499.5 kB

After Optimization

353.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tanutanuchan.seesaa.net main page is 499.5 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. 20% of websites need less resources to load. Images take 346.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 34.8 kB

  • Original 45.3 kB
  • After minification 38.6 kB
  • After compression 10.5 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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.8 kB or 77% of the original size.

Image Optimization

-13%

Potential reduce by 45.5 kB

  • Original 346.0 kB
  • After minification 300.5 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, Tanutanuchan Seesaa needs image optimization as it can save up to 45.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-50%

Potential reduce by 37.4 kB

  • Original 74.6 kB
  • After minification 74.5 kB
  • After compression 37.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 37.4 kB or 50% of the original size.

CSS Optimization

-84%

Potential reduce by 28.4 kB

  • Original 33.7 kB
  • After minification 22.6 kB
  • After compression 5.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. Tanutanuchan.seesaa.net needs all CSS files to be minified and compressed as it can save up to 28.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tanutanuchan.seesaa.net

tanutanuchan.seesaa.net

726 ms

styles-index.css

styles-index.css

484 ms

user-common.css

user-common.css

416 ms

ad_plugin.js

ad_plugin.js

417 ms

ads.js

ads.js

7 ms

article_search.js

article_search.js

393 ms

adstir.js

adstir.js

617 ms

analytics-seesaa-net.js

analytics-seesaa-net.js

419 ms

analytics.js

analytics.js

11 ms

NewScript

NewScript

355 ms

koakumabaner.png

koakumabaner.png

1091 ms

br_c_9174_1.gif

br_c_9174_1.gif

396 ms

bgt

bgt

309 ms

0.jpg

0.jpg

305 ms

styles-index.css

styles-index.css

173 ms

motohosutoshousaibottone.png

motohosutoshousaibottone.png

480 ms

E383A1E383ABE3839EE382ACE38390E3838AE383BC.png

E383A1E383ABE3839EE382ACE38390E3838AE383BC.png

666 ms

E3819FE381AC.png

E3819FE381AC.png

834 ms

E382B9E383AAE383A0.png

E382B9E383AAE383A0.png

673 ms

fan_read.gif

fan_read.gif

151 ms

fan_received.gif

fan_received.gif

148 ms

seesaablog.gif

seesaablog.gif

189 ms

000menu.png

000menu.png

491 ms

collect

collect

32 ms

000home.png

000home.png

440 ms

3black-plug-in3.gif

3black-plug-in3.gif

447 ms

motohosutotitle-aeb40.png

motohosutotitle-aeb40.png

456 ms

motohosutogrobal.png

motohosutogrobal.png

574 ms

motohosutocontener.png

motohosutocontener.png

629 ms

motohosutotopinfo.png

motohosutotopinfo.png

730 ms

motohosutosaisinnkizipoint.png

motohosutosaisinnkizipoint.png

783 ms

motohosutokizititle.png

motohosutokizititle.png

786 ms

listCategoryArticle.gif

listCategoryArticle.gif

235 ms

adcore.js

adcore.js

3 ms

adcore_pc.js

adcore_pc.js

4 ms

adcore_pc_inline.js

adcore_pc_inline.js

4 ms

ad_spot.aspx

ad_spot.aspx

6931 ms

motohosutosidebartitle.png

motohosutosidebartitle.png

791 ms

000pageup.png

000pageup.png

414 ms

000rss.png

000rss.png

425 ms

000book.png

000book.png

454 ms

000mail.png

000mail.png

562 ms

E784A1E9A18C-96f17.png

E784A1E9A18C-96f17.png

857 ms

ico_y.gif

ico_y.gif

208 ms

ad

ad

1419 ms

NewReceive

NewReceive

374 ms

sh.adingo.jp

sh.adingo.jp

349 ms

sync

sync

351 ms

u.html

u.html

32 ms

i.adingo.jp

i.adingo.jp

325 ms

i.adingo.jp

i.adingo.jp

408 ms

ad_1_right_0.gif

ad_1_right_0.gif

514 ms

collect

collect

5 ms

collect

collect

56 ms

cs

cs

769 ms

308 ms

627 ms

600 ms

154 ms

style.css

style.css

181 ms

ad_creative.ashx

ad_creative.ashx

9 ms

RestoreXidToMediaStorage.html

RestoreXidToMediaStorage.html

7 ms

SEO Factors

tanutanuchan.seesaa.net SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tanutanuchan.seesaa.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 Tanutanuchan.seesaa.net main page’s claimed encoding is shift_jis. 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

tanutanuchan.seesaa.net

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