Analyze Seesaa - シーサー株式会社サービス一覧


Page load speed analysis

  • 58/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    685 ms

  • Resources loaded

    2.6 sec

  • Page rendered

    128 ms

  • Total page load time

    3.4 sec

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

We analyzed page load time and found that the first response time was 685 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Page optimization

  • HTML 14.6 kB
    Images 788.8 kB
    Javascripts 121.1 kB
    CSS 70.2 kB

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

    • Original 14.6 kB
    • After minification 12.6 kB
    • After compression 3.4 kB

    HTML optimization

    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 2.0 kB, which is 14% 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 11.2 kB or 77% of the original size.

    • Original 788.8 kB
    • After optimization 710.5 kB

    Image optimization

    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. Seesaa images are well optimized though.

    • Original 121.1 kB
    • After minification 120.8 kB
    • After compression 41.6 kB

    JavaScript optimization

    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 79.5 kB or 66% of the original size.

    • Original 70.2 kB
    • After minification 60.6 kB
    • After compression 12.6 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 57.5 kB or 82% of the original size.

Network requests diagram

  • normalize.css
  • styles.css
  • jquery.min.js
  • main.js
  • img_logo.gif
  • img_seesaa.gif
  • bnr_gamesq.png
  • bnr_mangakit.png
  • bnr_bakusou.png
  • bnr_boomapp.png
  • bnr_forkn.jpg
  • img_logo-gamesq.png
  • img_logo-instantx.png
  • img_logo-bakusou.png
  • img_logo-tabhanabi.png
  • img_logo-taphanabiworld.png
  • img_logo-retum.png
  • img_logo-reception.png
  • img_logo-mangakit.png
  • img_logo-anycounter.png
  • img_logo-eyecam.png
  • img_logo-roulette.png
  • img_logo-blog.png
  • img_logo-shitaraba.png
  • img_logo-seesaawiki.png
  • img_logo-boomapp.gif
  • img_logo-boomappgames.png
  • img_logo-download.png
  • img_logo-forkn.png
  • img_logo-puble.png
  • img_logo-arkr.png
  • img_logo-fontview.png
  • img_logo-1set.gif
  • bg_header.jpg
  • bg_head-comment.gif
  • btn_gamesq.png
  • btn_mangakit.png
  • btn_bakusou.png
  • btn_boomapp.png
  • btn_forkn2.png
  • bg_footer.gif
  • bg_footermenu.gif

Our browser made a total of 43 requests to load all elements on the main page. We found that 98% of them (42 requests) were addressed to the original, 2% (1 request) were made to The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain

Additional info on


The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seesaa. According to our analytics all requests are already optimized.









Possible request optimization











Normal result

IP address uses IP addresses which are currently shared with 15 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 60
A 60
A 60
A 60
NS 86400

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 80.1% of all visits is Japan. It lies approximately 4840 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

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

Language and encoding

Good result


JA ja language flag


JA ja language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.

Share this report in social media

Analyze another website