Tools & Wizards About Us
cae.jsol.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cae.jsol.co.jp

CAEソリューション ： JSOL

Page Load Speed

5 sec in total

First Response

623 ms

Resources Loaded

4.1 sec

Page Rendered

204 ms

cae.jsol.co.jp screenshot

About Website

Welcome to cae.jsol.co.jp homepage info - get ready to check Cae JSOL best content for Japan right away, or after learning these important things about cae.jsol.co.jp

株式会社JSOLは、お客様の「ものづくり」を最先端なシミュレーション技術によりサポートします。CAE分野において、ソフトウェアの開発から技術サポート、コンサルティング、受託解析まで様々なソリューションをご提供します。

Visit cae.jsol.co.jp

Key Findings

We analyzed Cae.jsol.co.jp page load time and found that the first response time was 623 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

cae.jsol.co.jp performance score

0

Network Requests Diagram

cae.jsol.co.jp

623 ms

base.css

332 ms

common.css

500 ms

header.css

357 ms

footer.css

361 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original Cae.jsol.co.jp, 5% (4 requests) were made to Google-analytics.com and 4% (3 requests) were made to Jsol-publicsite-heatmap.appspot.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Cae.jsol.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.3 kB (30%)

Content Size

993.7 kB

After Optimization

694.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cae.jsol.co.jp main page is 993.7 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 596.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 49.9 kB

  • Original 63.2 kB
  • After minification 56.6 kB
  • After compression 13.2 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. 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 49.9 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 26.3 kB

  • Original 596.4 kB
  • After minification 570.1 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. Cae JSOL images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 183.5 kB

  • Original 285.8 kB
  • After minification 264.9 kB
  • After compression 102.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 183.5 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 39.6 kB

  • Original 48.4 kB
  • After minification 35.5 kB
  • After compression 8.9 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. Cae.jsol.co.jp needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cae.jsol.co.jp

cae.jsol.co.jp

623 ms

base.css

base.css

332 ms

common.css

common.css

500 ms

header.css

header.css

357 ms

footer.css

footer.css

361 ms

top.css

top.css

371 ms

jquery.min.js

jquery.min.js

904 ms

jquery.carouFredSel-6.2.1.js

jquery.carouFredSel-6.2.1.js

826 ms

top_news_json.js

top_news_json.js

537 ms

main.js

main.js

719 ms

smt2e.min.js

smt2e.min.js

396 ms

btn_head_search.gif

btn_head_search.gif

183 ms

jsol_logo.png

jsol_logo.png

186 ms

cae_solution.png

cae_solution.png

187 ms

CAEweb_top_bnr.jpg

CAEweb_top_bnr.jpg

1180 ms

top_virfac_bnr.jpg

top_virfac_bnr.jpg

606 ms

teiki-seminar_201602.jpg

teiki-seminar_201602.jpg

675 ms

201603_slide03.jpg

201603_slide03.jpg

907 ms

keyVisual_jmag.gif

keyVisual_jmag.gif

744 ms

ttl_contact.gif

ttl_contact.gif

390 ms

btn_contact.png

btn_contact.png

606 ms

tel_contact.gif

tel_contact.gif

736 ms

btn_ttl_01.gif

btn_ttl_01.gif

755 ms

btn_ttl_02.gif

btn_ttl_02.gif

840 ms

btn_ttl_03.gif

btn_ttl_03.gif

917 ms

btn_ttl_04.gif

btn_ttl_04.gif

928 ms

btn_ttl_05.gif

btn_ttl_05.gif

938 ms

btn_ttl_06.gif

btn_ttl_06.gif

1005 ms

btn_ttl_07.gif

btn_ttl_07.gif

1086 ms

btn_ttl_08.gif

btn_ttl_08.gif

1096 ms

logo_ntt.gif

logo_ntt.gif

1110 ms

logo_nihon.gif

logo_nihon.gif

1117 ms

gtm.js

gtm.js

64 ms

shadow_450.png

shadow_450.png

1155 ms

arrow_s.gif

arrow_s.gif

1253 ms

arrow_n.gif

arrow_n.gif

1261 ms

gnavi_bg1.png

gnavi_bg1.png

1276 ms

gnavi_bg2.png

gnavi_bg2.png

1285 ms

gnavi01.png

gnavi01.png

1321 ms

gnavi02.png

gnavi02.png

1327 ms

gnavi03.png

gnavi03.png

1433 ms

gnavi04.png

gnavi04.png

1440 ms

gnavi05.png

gnavi05.png

1456 ms

gnavi06.png

gnavi06.png

1463 ms

arrow_list.gif

arrow_list.gif

1483 ms

btn_bg_cae.png

btn_bg_cae.png

1494 ms

btn_bg_jyushi.png

btn_bg_jyushi.png

1614 ms

btn_bg_column.png

btn_bg_column.png

1620 ms

smt-aux.min.js

smt-aux.min.js

88 ms

ga.js

ga.js

26 ms

sync_suggest.js

sync_suggest.js

494 ms

__utm.gif

__utm.gif

46 ms

analytics.js

analytics.js

17 ms

collect

collect

57 ms

collect

collect

19 ms

collect

collect

62 ms

smt-record.min.js

smt-record.min.js

90 ms

btn_bg_event.png

btn_bg_event.png

1475 ms

btn_bg_support.png

btn_bg_support.png

1478 ms

btn_bg_product.png

btn_bg_product.png

1484 ms

btn_bg_dl.png

btn_bg_dl.png

1296 ms

news.json

news.json

1576 ms

btn_bg_access.png

btn_bg_access.png

1215 ms

arrow_t.gif

arrow_t.gif

1163 ms

shadow_ft.jpg

shadow_ft.jpg

1109 ms

arrow_l.gif

arrow_l.gif

1092 ms

list_img_foot.jpg

list_img_foot.jpg

1095 ms

ico_bar_w.gif

ico_bar_w.gif

1162 ms

shadow_fb.jpg

shadow_fb.jpg

1094 ms

arrow_wh.gif

arrow_wh.gif

1100 ms

pager_on.png

pager_on.png

1097 ms

pager_of.png

pager_of.png

1076 ms

pic_new.gif

pic_new.gif

182 ms

pic_user.gif

pic_user.gif

191 ms

arrow_o.gif

arrow_o.gif

182 ms

print_style.css

print_style.css

182 ms

btn_contact_on.png

btn_contact_on.png

182 ms

SEO Factors

cae.jsol.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

Social Sharing Optimization

cae.jsol.co.jp

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