Tools & Wizards About Us
classic.tradingcharts.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% 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

  • 85

    SEO

    Google-friendlier than
    55% of websites

classic.tradingcharts.com

Commodity Prices / Quotes & Commodity Charts - Free

Page Load Speed

1.7 sec in total

First Response

73 ms

Resources Loaded

1.5 sec

Page Rendered

85 ms

classic.tradingcharts.com screenshot

About Website

Click here to check amazing Classic Trading Charts content for United States. Otherwise, check out these important facts you probably never knew about classic.tradingcharts.com

Free! commodity prices and charts courtesy of TradingCharts (TFC Commodity Charts). We track many major commodities and financial indicators, making the information available in the form of free commo...

Visit classic.tradingcharts.com

Key Findings

We analyzed Classic.tradingcharts.com page load time and found that the first response time was 73 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

classic.tradingcharts.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value4,110 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

classic.tradingcharts.com

73 ms

classic.tradingcharts.com

73 ms

futures.tradingcharts.com

48 ms

futures.tradingcharts.com

133 ms

getQuote.json

135 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Classic.tradingcharts.com, 66% (31 requests) were made to Cdn.tradingcharts.com and 11% (5 requests) were made to Ondemand.websol.barchart.com. The less responsive or slowest element that took the longest time to load (476 ms) relates to the external source Cdn.tradingcharts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.6 kB (16%)

Content Size

555.5 kB

After Optimization

465.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classic.tradingcharts.com main page is 555.5 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. Javascripts take 387.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 70.4 kB

  • Original 90.3 kB
  • After minification 84.0 kB
  • After compression 20.0 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 70.4 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 1.0 kB

  • Original 42.3 kB
  • After minification 41.2 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. Classic Trading Charts images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 387.4 kB
  • After minification 387.4 kB
  • After compression 385.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-46%

Potential reduce by 16.5 kB

  • Original 35.5 kB
  • After minification 35.3 kB
  • After compression 19.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. Classic.tradingcharts.com needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

classic.tradingcharts.com

classic.tradingcharts.com

73 ms

classic.tradingcharts.com

classic.tradingcharts.com

73 ms

futures.tradingcharts.com

futures.tradingcharts.com

48 ms

futures.tradingcharts.com

futures.tradingcharts.com

133 ms

getQuote.json

getQuote.json

135 ms

gtm.js

gtm.js

67 ms

uat.js

uat.js

53 ms

jquery.min.js

jquery.min.js

43 ms

anychart.min.js

anychart.min.js

476 ms

tcfutures_utils.js

tcfutures_utils.js

177 ms

fut_ticker.js

fut_ticker.js

435 ms

tradingcharts-emailsignup.js

tradingcharts-emailsignup.js

13 ms

feV7.css

feV7.css

208 ms

site_bgV1.gif

site_bgV1.gif

16 ms

logo_blue.png

logo_blue.png

14 ms

search.png

search.png

15 ms

extremes_up.png

extremes_up.png

15 ms

ICEsprites2-2x_logo_white.png

ICEsprites2-2x_logo_white.png

28 ms

cmegroup-logo-2xinvers181x.png

cmegroup-logo-2xinvers181x.png

28 ms

close_icon_stickyfooter.gif

close_icon_stickyfooter.gif

26 ms

open_icon_stickyfooter.gif

open_icon_stickyfooter.gif

28 ms

heading_bg_gradV1.jpg

heading_bg_gradV1.jpg

13 ms

getLeaders.json

getLeaders.json

50 ms

fe_mini_charts.css

fe_mini_charts.css

67 ms

extremes_dn.png

extremes_dn.png

3 ms

heading_bg_grad.jpg

heading_bg_grad.jpg

28 ms

movers_tab_active.gif

movers_tab_active.gif

29 ms

shakers_tab_ma.gif

shakers_tab_ma.gif

31 ms

populars_tab.gif

populars_tab.gif

29 ms

quotebox.gif

quotebox.gif

30 ms

movers_tab_sa.gif

movers_tab_sa.gif

29 ms

shakers_tab_active.gif

shakers_tab_active.gif

31 ms

populars_tab_sa.gif

populars_tab_sa.gif

30 ms

movers_tab.gif

movers_tab.gif

33 ms

shakers_tab_pa.gif

shakers_tab_pa.gif

33 ms

populars_tab_active.gif

populars_tab_active.gif

32 ms

bg_grad_home.jpg

bg_grad_home.jpg

31 ms

fe_footer_links_bgV1.jpg

fe_footer_links_bgV1.jpg

31 ms

ga.js

ga.js

17 ms

feV7_mobile.css

feV7_mobile.css

76 ms

getQuote.json

getQuote.json

64 ms

getQuote.json

getQuote.json

58 ms

footer_common_functions.php

footer_common_functions.php

31 ms

__utm.gif

__utm.gif

12 ms

getHistory.json

getHistory.json

66 ms

ajax-loader.gif

ajax-loader.gif

4 ms

fe_mini_charts_mobile.css

fe_mini_charts_mobile.css

171 ms

Accessibility Review

classic.tradingcharts.com 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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

classic.tradingcharts.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

classic.tradingcharts.com SEO score

85

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classic.tradingcharts.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Classic.tradingcharts.com 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

classic.tradingcharts.com

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