Tools & Wizards About Us
cnex.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cnex.jp

「C-NEX」サービス終了のお知らせ│FXならヤフーグループのYJFX!

Page Load Speed

14.9 sec in total

First Response

1.7 sec

Resources Loaded

13.1 sec

Page Rendered

190 ms

cnex.jp screenshot

About Website

Welcome to cnex.jp homepage info - get ready to check C NEX best content for Japan right away, or after learning these important things about cnex.jp

スキャルピング向け「C-NEX」。FX・外国為替ならYJFX!【公式サイト】。C-NEXはYJFX!が提供するスキャルピング向けのFXサービスです。取引上限・取引数量無制限でハイスピード取引に対応しており、高い約定力を誇ります。

Visit cnex.jp

Key Findings

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

Performance Metrics

cnex.jp performance score

0

Network Requests Diagram

cnex.jp

1653 ms

www.cnex.jp

5517 ms

main.css

327 ms

common_style.css

324 ms

FB.css

345 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 88% of them (65 requests) were addressed to the original Cnex.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Cnex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.1 kB (19%)

Content Size

1.1 MB

After Optimization

869.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 17.5 kB

  • Original 24.5 kB
  • After minification 20.4 kB
  • After compression 7.1 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 4.1 kB, which is 17% 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 17.5 kB or 71% of the original size.

Image Optimization

-3%

Potential reduce by 26.2 kB

  • Original 794.1 kB
  • After minification 768.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. C NEX images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 135.3 kB

  • Original 223.5 kB
  • After minification 210.3 kB
  • After compression 88.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 135.3 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 25.1 kB

  • Original 31.1 kB
  • After minification 21.4 kB
  • After compression 6.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. Cnex.jp needs all CSS files to be minified and compressed as it can save up to 25.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (48%)

Requests Now

71

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cnex.jp

cnex.jp

1653 ms

www.cnex.jp

www.cnex.jp

5517 ms

main.css

main.css

327 ms

common_style.css

common_style.css

324 ms

FB.css

FB.css

345 ms

loop.css

loop.css

367 ms

style_03.css

style_03.css

367 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

531 ms

over.js

over.js

623 ms

jquery-1.4.1.min.js

jquery-1.4.1.min.js

974 ms

FB.js

FB.js

823 ms

swfobject.js

swfobject.js

685 ms

login.js

login.js

727 ms

s_code.js

s_code.js

3561 ms

common.css

common.css

632 ms

styles.css

styles.css

708 ms

modules.css

modules.css

747 ms

new_logo.png

new_logo.png

2655 ms

yjfx_logo.png

yjfx_logo.png

2654 ms

header_btn01.jpg

header_btn01.jpg

2655 ms

header_btn02_01.gif

header_btn02_01.gif

2656 ms

header_btn02_02.gif

header_btn02_02.gif

2657 ms

merit.png

merit.png

2658 ms

service.png

service.png

2659 ms

manual.png

manual.png

2659 ms

market.png

market.png

2660 ms

tokutei.png

tokutei.png

2661 ms

tex_yimg.png

tex_yimg.png

2671 ms

kouza_btn.png

kouza_btn.png

2668 ms

hojin_02.png

hojin_02.png

2662 ms

demo_02.png

demo_02.png

2662 ms

voc.png

voc.png

2665 ms

main_right3.jpg

main_right3.jpg

2663 ms

login_title01.jpg

login_title01.jpg

2663 ms

login_title02.jpg

login_title02.jpg

2664 ms

id.gif

id.gif

2665 ms

pass.gif

pass.gif

2665 ms

login_btn.jpg

login_btn.jpg

2666 ms

topics_title01.jpg

topics_title01.jpg

2667 ms

table_title.gif

table_title.gif

2668 ms

banner01-02.jpg

banner01-02.jpg

2669 ms

banner02-02.gif

banner02-02.gif

2670 ms

banner03-02.gif

banner03-02.gif

2670 ms

banner04-02.gif

banner04-02.gif

2670 ms

banner05-02.gif

banner05-02.gif

2671 ms

footernavi01.jpg

footernavi01.jpg

2671 ms

footernavi02.jpg

footernavi02.jpg

2672 ms

footernavi03.jpg

footernavi03.jpg

2673 ms

footernavi04.jpg

footernavi04.jpg

2672 ms

footernavi05.jpg

footernavi05.jpg

2673 ms

footer_btn.gif

footer_btn.gif

2674 ms

gtm.js

gtm.js

2623 ms

address02.gif

address02.gif

2733 ms

tag.js

tag.js

7 ms

tag

tag

90 ms

spacer.gif

spacer.gif

184 ms

footerlogo.gif

footerlogo.gif

172 ms

arrow_001.png

arrow_001.png

322 ms

header_main.png

header_main.png

2266 ms

login_bg.jpg

login_bg.jpg

327 ms

formbg.gif

formbg.gif

430 ms

loginicon.gif

loginicon.gif

474 ms

topics_title02.jpg

topics_title02.jpg

522 ms

topics_bg.jpg

topics_bg.jpg

969 ms

table01_bk.gif

table01_bk.gif

671 ms

bottom_menu_icon.gif

bottom_menu_icon.gif

770 ms

footer_topbg.gif

footer_topbg.gif

772 ms

footer_bottom.gif

footer_bottom.gif

850 ms

analytics.js

analytics.js

29 ms

s34699535926338

s34699535926338

20 ms

conversion.js

conversion.js

1590 ms

collect

collect

12 ms

collect

collect

51 ms

conversion.js

conversion.js

630 ms

SEO Factors

cnex.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

Social Sharing Optimization

cnex.jp

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