Analyze

asp.jcity.co.jp: JCity,Inc.(東京 恵比寿) | インターネットビジネスの構想を実現させるASPサービス

インターネットビジネスの構想を実現させるASPサービスを提供しています。

Page load speed analysis

  • 50/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    1.1 sec

  • Resources loaded

    5.7 sec

  • Page rendered

    238 ms

  • Total page load time

    7.1 sec

Click here to check amazing Asp JCity content for Japan. Otherwise, check out these important facts you probably never knew about asp.jcity.co.jp

We analyzed Asp.jcity.co.jp page load time and found that the first response time was 1.1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Page optimization

  • HTML 32.2 kB
    Images 487.0 kB
    Javascripts 98.8 kB
    CSS 7.1 kB

    In fact, the total size of Asp.jcity.co.jp main page is 625.0 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. 35% of websites need less resources to load. Images take 487.0 kB which makes up the majority of the site volume.

    • Original 32.2 kB
    • After minification 31.0 kB
    • After compression 7.5 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. 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 24.6 kB or 77% of the original size.

    • Original 487.0 kB
    • After optimization 471.0 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. Asp JCity images are well optimized though.

    • Original 98.8 kB
    • After minification 98.7 kB
    • After compression 36.9 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 61.9 kB or 63% of the original size.

    • Original 7.1 kB
    • After minification 5.9 kB
    • After compression 1.7 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. Asp.jcity.co.jp needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 76% of the original size.

Network requests diagram

  • www.jcity.co.jp
  • rollover.js
  • jcity.css
  • style_index.css
  • conversion.js
  • footer_inquiry.css
  • space.gif
  • headimage.jpg
  • b_home.gif
  • b_service.gif
  • b_site.gif
  • b_company.gif
  • b_inquiry.gif
  • space-t12.gif
  • mail_title.gif
  • space-t04.gif
  • b_entry.gif
  • space-t10.gif
  • web_title.gif
  • b_web_next.gif
  • space-t15.gif
  • brand_title1.jpg
  • brand_title2.jpg
  • b_brand.gif
  • b_brand_next.gif
  • hp_title.jpg
  • b_consult.gif
  • space-t06.gif
  • b_form.gif
  • b_charge.gif
  • space-t03.gif
  • ban_fo.png
  • ban_mm.png
  • topBnr_industrial.jpg
  • banner_tv.jpg
  • space-t30.gif
  • newtop-shikumi_r1_c1.jpg
  • mail_anim.gif
  • b_mailtitle.gif
  • b_mailnext.gif
  • ga.js
  • b_formicon.gif
  • __utm.gif
  • dc.js
  • __utm.gif
  • collect
  • b_formtitle.gif
  • b_formnext.gif
  • system_anim.gif
  • b_systemtitle.gif
  • b_systemnext.gif
  • b_seminaricon.gif
  • b_seminartitle.gif
  • b_seminarnext.gif
  • b_hpicon.gif
  • b_hptitle.gif
  • b_hpnext.gif
  • b_carticon.gif
  • b_carttitle.gif
  • b_cartnext.gif
  • b_goodsicon.gif
  • b_goodstitle.gif
  • b_goodsnext.gif
  • space-t25.gif
  • img_tel.jpg
  • btn_dl_inquiry.jpg
  • space-t20.gif
  • space-t10.gif
  • newleft-back_r1_c1.gif
  • newleft-back_r2_c1.gif
  • bg_dl_inquiry.jpg
  • icon_black.jpg
  • headlink_r2_c1.jpg
  • headlink_r2_c2.jpg
  • headlink_r2_c3.jpg
  • headlink_r2_c4.jpg
  • headlink_r2_c5.jpg
  • headlink_r2_c6.jpg
  • newleftbanar_r2_c4.jpg
  • newleftbanar_r3_c4.jpg
  • newleftbanar_r4_c3.jpg
  • newleftbanar_r5_c3.jpg
  • newleftbanar_r6_c3.jpg
  • newleftbanar_r7_c3.jpg
  • newleftbanar_r8_c3.jpg
  • newtop-icon_r2_c1.jpg
  • newtop-copy_r1_c2.jpg
  • newtop-icon_r2_c2.jpg
  • newtop-copy_r2_c2.jpg
  • newtop-icon_r2_c3.jpg
  • newtop-copy_r3_c2.jpg
  • newtop-icon_r2_c4.jpg
  • newtop-copy_r4_c2.jpg
  • newtop-icon_r2_c5.jpg
  • newtop-copy_r5_c2.jpg
  • newtop-icon_r2_c6.jpg
  • newtop-copy_r6_c2.jpg
  • newtop-icon_r2_c7.jpg
  • newtop-copy_r7_c2.jpg
  • newtop-shikumi_r2_c1.jpg
  • newleft-mmbotan_r1_c2.jpg
  • newleft-sho_r2_c1.jpg
  • newtop-sho_r1_c2.gif
  • newtop-sho_r2_c2.gif
  • newtop-sho_r3_c2.gif
  • newtop-sho_r4_c2.gif
  • newtop-sho_r5_c2.gif
  • newtop-sho_r6_c2.gif
  • newtop-sho_r7_c2.gif
  • newleft-banarT_r2_c1.jpg
  • top-form-banar-RO.jpg

Our browser made a total of 113 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Asp.jcity.co.jp, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Jcity.co.jp.

Additional info on asp.jcity.co.jp

Requests

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

4

Javascripts

65

Images

3

CSS

1

AJAX

73

All

Possible request optimization

1

Javascripts

45

Images

3

CSS

1

AJAX

23

Optimized

50

All

Normal result

IP address

This IP address is dedicated to Asp.jcity.co.jp. This is the best domain hosting practice .

Normal result

IP Trace

asp.jcity.co.jp

112.140.51.32

DNS records

Type Host Target/ip TTL Other
A

asp.jcity.co.jp

112.140.51.32 288

Language and encoding

Poor result

Language

JA ja language flag

Detected

N/A  language flag

Claimed

Encoding

SHIFT_JIS

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asp.jcity.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Asp.jcity.co.jp 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.

HTTPS certificate

SSL Certificate

Asp.jcity.co.jp 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 100% of all visits is Japan. It’s good for Asp.jcity.co.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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

asp.jcity.co.jp

Share this report in social media

Analyze another website

Analyze