Analyze IP分散サーバーなら123サーバー - 【無料お試し】 | 123Server

クラスCで分散した国内IPアドレス、海外IPアドレスを最大1,300IP分散可能。より自然な分散を追求し、国内IP分散では、DNS分散やサーバーロケーション分散も可能です。サーバー契約数 353,365台の実績。

Page load speed analysis

  • 54/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    161 ms

  • Resources loaded

    3.4 sec

  • Page rendered

    265 ms

  • Total page load time

    3.9 sec

Welcome to homepage info - get ready to check 123 Japanserver best content for Japan right away, or after learning these important things about

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

Page optimization

  • HTML 28.7 kB
    Images 471.4 kB
    Javascripts 197.1 kB
    CSS 36.1 kB

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

    • Original 28.7 kB
    • After minification 23.2 kB
    • After compression 6.1 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 5.5 kB, which is 19% 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 22.7 kB or 79% of the original size.

    • Original 471.4 kB
    • After optimization 193.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. Obviously, 123 Japanserver needs image optimization as it can save up to 277.9 kB or 59% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 197.1 kB
    • After minification 178.0 kB
    • After compression 63.2 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 133.9 kB or 68% of the original size.

    • Original 36.1 kB
    • After minification 20.9 kB
    • After compression 5.8 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 30.2 kB or 84% of the original size.

Network requests diagram

  • common.css
  • layout.css
  • style.css
  • colorbox.css
  • jquery.js
  • plugins.js
  • jquery.navigation.js
  • jquery.tile.js
  • jquery.colorbox-min.js
  • jquery.placeholder.min.js
  • common.js
  • top.css
  • xoops.js
  • track.js
  • bg_line_dotted.gif
  • header_tollfree.gif
  • ci.gif
  • icon_arrow03.gif
  • utility_news.gif
  • utility_corporate.gif
  • utility_tos.gif
  • utility_contact.gif
  • header_login_123.gif
  • header_login_btn.gif
  • header_login_japan.gif
  • header_login_world.gif
  • header_login_domain.gif
  • gnavi_home.gif
  • gnavi_123.gif
  • gnavi_japan.gif
  • gnavi_support.gif
  • bg_shadow_top.gif
  • side_ttl.jpg
  • lnavi_top.gif
  • lnavi_single.gif
  • lnavi_multi.gif
  • lnavi_flow.gif
  • lnavi_faq.gif
  • lnavi_news.gif
  • bg_side_support.gif
  • side_support_ttl.gif
  • side_support_text.gif
  • side_photo.png
  • bg_side_support_tollfree.png
  • side_support_tel.gif
  • side_support_time.gif
  • side_support_btn.gif
  • side_btn_compare.gif
  • side_btn_report.gif
  • ga.js
  • side_btn_reason.gif
  • bg_main_top.jpg
  • main_ttl.jpg
  • main_lead.jpg
  • __utm.gif
  • __utm.gif
  • bg_main_l.gif
  • main_single_sttl.gif
  • main_single_text.gif
  • main_single_img_01.png
  • bg_main_l_btn.gif
  • btn_detail.png
  • bg_main_r.gif
  • main_multi_sttl.gif
  • main_multi_text.gif
  • main_multi_img_01.png
  • bg_main_r_btn.gif
  • 710_130_03_b.jpg
  • sttl_feature.gif
  • wordpress.gif
  • feature_text01.gif
  • feature_icon01.gif
  • feature_text02.gif
  • feature_icon02.gif
  • feature_text03.png
  • feature_icon03.png
  • feature_text06.gif
  • feature_icon06.gif
  • feature_text08.gif
  • feature_icon08.gif
  • feature_text07.gif
  • feature_icon07.gif
  • feature_text10.gif
  • feature_icon10_01.png
  • feature_text09.gif
  • feature_icon09.gif
  • feature_text04.gif
  • feature_icon04.gif
  • feature_text13.gif
  • feature_icon13.gif
  • feature_text14.gif
  • feature_icon14.gif
  • feature_text05.gif
  • feature_icon05.gif
  • sttl_faq.gif
  • btn_list.gif
  • icon_rss20.gif
  • sttl_news.gif
  • icon_arrow01.gif
  • btn_return_top.gif
  • bg_shadow_bottom.gif
  • bg_footer.jpg
  • footer_tollfree.png
  • footer_btn_contact.png
  • sttl_seo.gif
  • icon_arrow02.gif
  • gnavi_home_on.gif
  • gnavi_123_on.gif
  • gnavi_japan_in.gif
  • gnavi_support_on.gif
  • lnavi_top_on.gif
  • lnavi_single_on.gif
  • lnavi_multi_on.gif
  • lnavi_flow_on.gif
  • lnavi_faq_on.gif
  • lnavi_news_on.gif
  • header_login_btn_on.gif
  • side_support_btn_on.gif
  • side_btn_compare_on.gif
  • side_btn_report_on.gif
  • side_btn_reason_on.gif
  • btn_detail_on.png
  • btn_list_on.gif
  • footer_btn_contact_on.png
  • print.css

Our browser made a total of 127 requests to load all elements on the main page. We found that 97% of them (123 requests) were addressed to the original, 2% (3 requests) were made to and 1% (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 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123 Japanserver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.









Possible request optimization











Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address

This IP address is dedicated to This is the best domain hosting practice .

Good result

IP Trace

DNS records

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

86400 Mname:
Serial: 2020050900
Refresh: 3600
Retry: 7200
Expire: 1209600
Minimum-ttl: 86400
MX 14400 Pri: 0

Language and encoding

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

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.

Poor result

Visitor World Map

Country of origin for 96.6% of all visits is Japan. Unfortunately, we cannot track the location of server and thus cannot define if the distance between their user base and server can potentially affect the page load time

Good result

Poor result

Social Sharing Optimization

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

Share this report in social media

Analyze another website