Tools & Wizards About Us
traders.co.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

traders.co.jp

ホーム | トレーダーズ・ウェブ

Page Load Speed

9 sec in total

First Response

443 ms

Resources Loaded

7.8 sec

Page Rendered

768 ms

traders.co.jp screenshot

About Website

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

「トレーダーズ・ウェブ」は株式投資の情報サイトです。日経平均の見通しや株価予想を中心に、IPO、注目銘柄、決算発表、レーティング、米国株の情報なども提供しています。

Visit traders.co.jp

Key Findings

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

Performance Metrics

traders.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value3,450 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

traders.co.jp

443 ms

traders.co.jp

2440 ms

gtm.js

45 ms

bootstrap.min.css

2603 ms

jquery-3.5.1.min.js

18 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 56% of them (40 requests) were addressed to the original Traders.co.jp, 13% (9 requests) were made to Historical.traders.co.jp and 8% (6 requests) were made to Media.traders.co.jp. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Traders.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 227.5 kB (20%)

Content Size

1.1 MB

After Optimization

883.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Traders.co.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 703.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 134.8 kB

  • Original 151.3 kB
  • After minification 83.7 kB
  • After compression 16.4 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 67.6 kB, which is 45% 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 134.8 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 10.0 kB

  • Original 703.7 kB
  • After minification 693.7 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. Traders images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 76.2 kB

  • Original 216.3 kB
  • After minification 216.2 kB
  • After compression 140.1 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 76.2 kB or 35% of the original size.

CSS Optimization

-16%

Potential reduce by 6.4 kB

  • Original 39.2 kB
  • After minification 39.2 kB
  • After compression 32.8 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. Traders.co.jp needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (37%)

Requests Now

70

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

traders.co.jp

traders.co.jp

443 ms

traders.co.jp

traders.co.jp

2440 ms

gtm.js

gtm.js

45 ms

bootstrap.min.css

bootstrap.min.css

2603 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

18 ms

jquery-ui.min.js

jquery-ui.min.js

22 ms

ios_safari_fix.js

ios_safari_fix.js

585 ms

tw_news_common.min.css

tw_news_common.min.css

586 ms

tw_ipo_common.min.css

tw_ipo_common.min.css

590 ms

tw_column_common.min.css

tw_column_common.min.css

585 ms

js

js

59 ms

adsbygoogle.js

adsbygoogle.js

120 ms

util.js

util.js

173 ms

common.js

common.js

177 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

17 ms

iStock-514721460_c.jpg

iStock-514721460_c.jpg

1024 ms

13_20221222164654475583.jpg

13_20221222164654475583.jpg

771 ms

15_20221222164729663905.jpg

15_20221222164729663905.jpg

1110 ms

17_20221222164809805584.jpg

17_20221222164809805584.jpg

791 ms

18_20221222164833353058.jpg

18_20221222164833353058.jpg

947 ms

29_20221228094453406168.jpg

29_20221228094453406168.jpg

796 ms

30_20221228094514797241.jpg

30_20221228094514797241.jpg

809 ms

iStock-468537922.jpg

iStock-468537922.jpg

914 ms

twlogo.svg

twlogo.svg

174 ms

search.svg

search.svg

184 ms

rating.svg

rating.svg

176 ms

earnings_rev.svg

earnings_rev.svg

180 ms

earnings_calendar.svg

earnings_calendar.svg

177 ms

ipo_schedule.svg

ipo_schedule.svg

181 ms

screening.svg

screening.svg

343 ms

adr.svg

adr.svg

346 ms

banner3_pc.svg

banner3_pc.svg

3691 ms

banner3_sp.svg

banner3_sp.svg

2461 ms

window.svg

window.svg

347 ms

no1.svg

no1.svg

356 ms

no2.svg

no2.svg

513 ms

no3.svg

no3.svg

516 ms

tweye71.jpg

tweye71.jpg

690 ms

tweye53.jpg

tweye53.jpg

885 ms

tweye66.jpg

tweye66.jpg

1369 ms

tweye70.jpg

tweye70.jpg

1032 ms

tweye30.jpg

tweye30.jpg

864 ms

tweye34.jpg

tweye34.jpg

1042 ms

logo_imakara.svg

logo_imakara.svg

1062 ms

down.svg

down.svg

1203 ms

up.svg

up.svg

1215 ms

stay.svg

stay.svg

1237 ms

compass_up.svg

compass_up.svg

1374 ms

logo_fx.svg

logo_fx.svg

1388 ms

logo_niki.png

logo_niki.png

1441 ms

pagetop.svg

pagetop.svg

1537 ms

mhira-000000029_c.jpg

mhira-000000029_c.jpg

844 ms

matsu-000000003_c.jpg

matsu-000000003_c.jpg

1013 ms

iStock-147060934.jpg

iStock-147060934.jpg

1052 ms

iStock-539090008.jpg

iStock-539090008.jpg

1115 ms

arrow.svg

arrow.svg

1497 ms

arrow.svg

arrow.svg

1512 ms

chart.php

chart.php

694 ms

chart.php

chart.php

711 ms

chart.php

chart.php

730 ms

chart.php

chart.php

736 ms

scrollable.svg

scrollable.svg

1499 ms

analytics.js

analytics.js

16 ms

collect

collect

13 ms

collect

collect

19 ms

ga-audiences

ga-audiences

42 ms

jquery.min.js

jquery.min.js

20 ms

TWChartSimple.min.js

TWChartSimple.min.js

668 ms

hgate.php

hgate.php

914 ms

hgate.php

hgate.php

520 ms

hgate.php

hgate.php

782 ms

hgate.php

hgate.php

690 ms

Accessibility Review

traders.co.jp accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

traders.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

traders.co.jp SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Traders.co.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 Traders.co.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

traders.co.jp

Open Graph data is detected on the main page of Traders. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: