Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

chart.ly

Easily Create Beautiful Charts and Dashboards with Chartly

Page Load Speed

1.8 sec in total

First Response

155 ms

Resources Loaded

808 ms

Page Rendered

798 ms

About Website

Welcome to chart.ly homepage info - get ready to check Chart best content right away, or after learning these important things about chart.ly

Charty gives you the ability to build integrated dashboards, bringing all of your data into one place.

Visit chart.ly

Key Findings

We analyzed Chart.ly page load time and found that the first response time was 155 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 30% of websites can load faster.

Performance Metrics

chart.ly performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

chart.ly

155 ms

chart.ly

101 ms

css

73 ms

bootstrap.min.css

59 ms

fontawesome-all-25d0aeaff193b56725b20dbdb972d27d565e0eacdde85a6d849b3a3de46d5bd3.js

129 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 58% of them (22 requests) were addressed to the original Chart.ly, 16% (6 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (222 ms) belongs to the original domain Chart.ly.

Page Optimization Overview & Recommendations

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

Content Size

3.5 MB

After Optimization

2.5 MB

In fact, the total size of Chart.ly main page is 3.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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 29.0 kB

  • Original 39.0 kB
  • After minification 35.6 kB
  • After compression 10.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 29.0 kB or 74% of the original size.

Image Optimization

-41%

Potential reduce by 943.1 kB

  • Original 2.3 MB
  • After minification 1.4 MB

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, Chart needs image optimization as it can save up to 943.1 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.1 MB

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

-0%

Potential reduce by 26 B

  • Original 6.6 kB
  • After minification 6.6 kB
  • After compression 6.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. Chart.ly has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (40%)

Requests Now

30

After Optimization

18

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chart. 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 as a result speed up the page load time.

Accessibility Review

chart.ly accessibility score

90

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

chart.ly 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

Missing source maps for large first-party JavaScript

SEO Factors

chart.ly SEO score

87

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chart.ly 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 Chart.ly main page’s claimed encoding is . 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

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