Tools & Wizards About Us
tamtam.seesaa.net screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tamtam.seesaa.net

TAMTAM time

Page Load Speed

34.9 sec in total

First Response

945 ms

Resources Loaded

24.8 sec

Page Rendered

9.1 sec

tamtam.seesaa.net screenshot

About Website

Click here to check amazing TAMTAM Seesaa content for Japan. Otherwise, check out these important facts you probably never knew about tamtam.seesaa.net

talking about motorcycle, everyday life, etc.

Visit tamtam.seesaa.net

Key Findings

We analyzed Tamtam.seesaa.net page load time and found that the first response time was 945 ms and then it took 34 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

tamtam.seesaa.net performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value18.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value40.3 s

0/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

tamtam.seesaa.net

945 ms

styles-index.css

426 ms

common_header.js

325 ms

ad_plugin.js

328 ms

bl-bookmarks.js

493 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tamtam.seesaa.net, 28% (22 requests) were made to Blog.seesaa.jp and 13% (10 requests) were made to Tamtam.up.n.seesaa.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Tagfriends.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.8 kB (22%)

Content Size

1.0 MB

After Optimization

815.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 59.9 kB

  • Original 77.5 kB
  • After minification 67.6 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 9.9 kB, which is 13% 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 59.9 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 25.9 kB

  • Original 759.9 kB
  • After minification 734.0 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. TAMTAM Seesaa images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 130.5 kB

  • Original 191.8 kB
  • After minification 168.2 kB
  • After compression 61.3 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 130.5 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 12.5 kB

  • Original 15.5 kB
  • After minification 12.1 kB
  • After compression 3.0 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. Tamtam.seesaa.net needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (57%)

Requests Now

74

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TAMTAM 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 26 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tamtam.seesaa.net

tamtam.seesaa.net

945 ms

styles-index.css

styles-index.css

426 ms

common_header.js

common_header.js

325 ms

ad_plugin.js

ad_plugin.js

328 ms

bl-bookmarks.js

bl-bookmarks.js

493 ms

geobp.js

geobp.js

378 ms

article_search.js

article_search.js

179 ms

badge.js.gne

badge.js.gne

75 ms

5765e150e8.js

5765e150e8.js

549 ms

ID001000027249

ID001000027249

20169 ms

yawaraka_bph.js

yawaraka_bph.js

557 ms

trace_searcher.js

trace_searcher.js

196 ms

square_viasearch_seesaa_fluct.js

square_viasearch_seesaa_fluct.js

613 ms

adstir.js

adstir.js

370 ms

analytics-seesaa-net.js

analytics-seesaa-net.js

418 ms

DSC02450.jpg

DSC02450.jpg

1093 ms

tamtam-2013-05-18T19:44:04-1.jpg

tamtam-2013-05-18T19:44:04-1.jpg

1828 ms

tamtam-2013-03-20T15:20:21-1.jpg

tamtam-2013-03-20T15:20:21-1.jpg

979 ms

tamtam-2013-02-16T17:44:16-1.jpg

tamtam-2013-02-16T17:44:16-1.jpg

1827 ms

2013-01-052009.58.08-thumbnail2.jpg

2013-01-052009.58.08-thumbnail2.jpg

943 ms

tamtam-2012-12-15T12:43:09-1.jpg

tamtam-2012-12-15T12:43:09-1.jpg

943 ms

tamtam-2012-12-11T14:38:52-1.jpg

tamtam-2012-12-11T14:38:52-1.jpg

941 ms

tamtam-2012-12-11T14:38:52-2.jpg

tamtam-2012-12-11T14:38:52-2.jpg

1127 ms

tamtam-2012-08-30T12:32:34-1.jpg

tamtam-2012-08-30T12:32:34-1.jpg

1090 ms

tamtam-2012-07-28T17:50:29-1.jpg

tamtam-2012-07-28T17:50:29-1.jpg

1089 ms

tamtam-2012-07-22T08:05:11-1.jpg

tamtam-2012-07-22T08:05:11-1.jpg

1125 ms

P1030494-thumbnail2.jpg

P1030494-thumbnail2.jpg

972 ms

fan_read.gif

fan_read.gif

203 ms

fan_received.gif

fan_received.gif

214 ms

seesaablog.gif

seesaablog.gif

231 ms

common-header.css

common-header.css

252 ms

ot_square.pl

ot_square.pl

395 ms

AdLantisLoader.js

AdLantisLoader.js

412 ms

common_header_sb.js

common_header_sb.js

297 ms

1.gif

1.gif

362 ms

ico_pr2.gif

ico_pr2.gif

161 ms

ico_pr3.gif

ico_pr3.gif

162 ms

embed.js

embed.js

910 ms

common_header_sb.css

common_header_sb.css

172 ms

www.livedoor.com

www.livedoor.com

654 ms

common_header_sb1.gif

common_header_sb1.gif

340 ms

common_header_sb.gif

common_header_sb.gif

340 ms

blog_bg.jpg

blog_bg.jpg

341 ms

blog_top.jpg

blog_top.jpg

340 ms

blog_bottom.jpg

blog_bottom.jpg

366 ms

side_title.jpg

side_title.jpg

332 ms

bookmark_button.js

bookmark_button.js

509 ms

sdk.js

sdk.js

482 ms

widgets.js

widgets.js

226 ms

ico_y.gif

ico_y.gif

231 ms

fpi.js

fpi.js

191 ms

badge_code.js

badge_code.js

200 ms

153 ms

delivery

delivery

186 ms

xd_arbiter.php

xd_arbiter.php

277 ms

xd_arbiter.php

xd_arbiter.php

493 ms

trackfeedbargreen.gif

trackfeedbargreen.gif

392 ms

trace_searcher.css

trace_searcher.css

374 ms

ad

ad

379 ms

ad

ad

233 ms

sh.adingo.jp

sh.adingo.jp

362 ms

sync

sync

554 ms

i.adingo.jp

i.adingo.jp

459 ms

i.adingo.jp

i.adingo.jp

567 ms

analytics.js

analytics.js

133 ms

adlantis.www.js

adlantis.www.js

712 ms

swfobject.js

swfobject.js

735 ms

collect

collect

103 ms

collect

collect

403 ms

601 ms

load_script

load_script

610 ms

777 ms

load_iframe

load_iframe

414 ms

ads_premium.js

ads_premium.js

70 ms

adcore.js

adcore.js

260 ms

adcore_pc.js

adcore_pc.js

276 ms

156 ms

adcore_pc_infeed_inline.js

adcore_pc_infeed_inline.js

54 ms

Accessibility Review

tamtam.seesaa.net accessibility score

43

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

tamtam.seesaa.net best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tamtam.seesaa.net SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Tamtam.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 Tamtam.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

tamtam.seesaa.net

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