Tools & Wizards About Us
chartlog.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

chartlog.com

#1 Journaling and Analytics Software for Traders | Chartlog

Page Load Speed

1.9 sec in total

First Response

32 ms

Resources Loaded

1.3 sec

Page Rendered

525 ms

chartlog.com screenshot

About Website

Visit chartlog.com now to see the best up-to-date Chartlog content for Israel and also check out these interesting facts you probably never knew about chartlog.com

The best journaling and analytics software for traders. Create an account for free and upgrade to pro when ready. Make better trading decisions now.

Visit chartlog.com

Key Findings

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

Performance Metrics

chartlog.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

chartlog.com

32 ms

chartlog.com

16 ms

www.chartlog.com

344 ms

bootstrap.min.css

73 ms

slick.css

16 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 45% of them (26 requests) were addressed to the original Chartlog.com, 9% (5 requests) were made to Pro.fontawesome.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (668 ms) relates to the external source Cdn.mouseflow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 420.5 kB (28%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chartlog.com main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.6 kB

  • Original 45.2 kB
  • After minification 38.3 kB
  • After compression 9.6 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 6.9 kB, which is 15% 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 35.6 kB or 79% of the original size.

Image Optimization

-27%

Potential reduce by 308.5 kB

  • Original 1.1 MB
  • After minification 823.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. Obviously, Chartlog needs image optimization as it can save up to 308.5 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-29%

Potential reduce by 75.5 kB

  • Original 263.2 kB
  • After minification 263.2 kB
  • After compression 187.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 75.5 kB or 29% of the original size.

CSS Optimization

-3%

Potential reduce by 972 B

  • Original 37.6 kB
  • After minification 37.6 kB
  • After compression 36.6 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. Chartlog.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

43

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chartlog.com

chartlog.com

32 ms

chartlog.com

chartlog.com

16 ms

www.chartlog.com

www.chartlog.com

344 ms

bootstrap.min.css

bootstrap.min.css

73 ms

slick.css

slick.css

16 ms

slick-theme.css

slick-theme.css

48 ms

main.css

main.css

39 ms

css2

css2

79 ms

animate.min.css

animate.min.css

65 ms

all.css

all.css

82 ms

jquery.min.js

jquery.min.js

62 ms

popper.min.js

popper.min.js

79 ms

JqueryCore.js

JqueryCore.js

50 ms

inputfields.min.js

inputfields.min.js

56 ms

form-builder-d.js

form-builder-d.js

57 ms

bootstrap.min.js

bootstrap.min.js

77 ms

lm.js

lm.js

60 ms

js

js

130 ms

js

js

287 ms

embed.php

embed.php

130 ms

embed.php

embed.php

181 ms

slick.min.js

slick.min.js

57 ms

jquery.cookie.js

jquery.cookie.js

56 ms

parameters.js

parameters.js

56 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

254 ms

fbevents.js

fbevents.js

202 ms

stat.js

stat.js

252 ms

logo_black.svg

logo_black.svg

35 ms

interactivebrokers.svg

interactivebrokers.svg

32 ms

tdameritrade.png

tdameritrade.png

33 ms

dastrader.svg

dastrader.svg

30 ms

webull.svg

webull.svg

36 ms

hero-home-bg.png

hero-home-bg.png

326 ms

chartlog-journal.png

chartlog-journal.png

235 ms

best-trading-journal.png

best-trading-journal.png

163 ms

andrew-aziz.jpg

andrew-aziz.jpg

198 ms

ed.jpeg

ed.jpeg

199 ms

max-madaz.jpg

max-madaz.jpg

160 ms

logo_gray.svg

logo_gray.svg

233 ms

js

js

249 ms

analytics.js

analytics.js

342 ms

js

js

273 ms

diffuser.js

diffuser.js

307 ms

f19ea3a2-c39c-442a-8bc3-3560c53119e0.js

f19ea3a2-c39c-442a-8bc3-3560c53119e0.js

668 ms

main.js

main.js

371 ms

ajax-loader.gif

ajax-loader.gif

125 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

228 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

229 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

257 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

258 ms

fa-solid-900.woff

fa-solid-900.woff

158 ms

fa-regular-400.woff

fa-regular-400.woff

203 ms

fa-light-300.woff

fa-light-300.woff

207 ms

fa-brands-400.woff

fa-brands-400.woff

203 ms

slick.woff

slick.woff

116 ms

collect

collect

26 ms

collect

collect

35 ms

prism.app-us1.com

prism.app-us1.com

129 ms

Accessibility Review

chartlog.com accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

chartlog.com 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

chartlog.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chartlog.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Chartlog.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

chartlog.com

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