Tools & Wizards About Us
chartable.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

chartable.com

Chartable: Podcast Analytics & Attribution - Chartable

Page Load Speed

2.1 sec in total

First Response

338 ms

Resources Loaded

1.3 sec

Page Rendered

435 ms

chartable.com screenshot

About Website

Welcome to chartable.com homepage info - get ready to check Chartable best content for United States right away, or after learning these important things about chartable.com

Podcast analytics and attribution for publishers & advertisers. Plus podcast charts from Apple Podcasts and Spotify around the world, and an amazing Podcast API, and tools for publishers to grow their...

Visit chartable.com

Key Findings

We analyzed Chartable.com page load time and found that the first response time was 338 ms and then it took 1.7 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

chartable.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.162

72/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

chartable.com

338 ms

css

37 ms

28 ms

application-4cd383a0.css

60 ms

application-fef3b52c6a952293a9e0.js

312 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 74% of them (32 requests) were addressed to the original Chartable.com, 9% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (338 ms) belongs to the original domain Chartable.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.0 kB (1%)

Content Size

2.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chartable.com main page is 2.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. 40% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 18.8 kB

  • Original 27.3 kB
  • After minification 27.3 kB
  • After compression 8.5 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 18.8 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 115 B

  • Original 515.2 kB
  • After minification 515.1 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. Chartable images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 95 B

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 1.9 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 0 B

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

Requests Breakdown

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

Requests Now

37

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chartable.com

chartable.com

338 ms

css

css

37 ms

28 ms

application-4cd383a0.css

application-4cd383a0.css

60 ms

application-fef3b52c6a952293a9e0.js

application-fef3b52c6a952293a9e0.js

312 ms

js

js

72 ms

email-decode.min.js

email-decode.min.js

94 ms

widget-v2.js

widget-v2.js

130 ms

rollbar.min.js

rollbar.min.js

74 ms

logo-text-gray-26b195a25ce6db1e678f9b15b0a34ed038d8dd81c0e6c9d70c3a17145d1a797f.png

logo-text-gray-26b195a25ce6db1e678f9b15b0a34ed038d8dd81c0e6c9d70c3a17145d1a797f.png

59 ms

iheart-logo-0681494d6526457294f35bf1584b668decba040f82c9a72aa4e9ac971f2a415a.png

iheart-logo-0681494d6526457294f35bf1584b668decba040f82c9a72aa4e9ac971f2a415a.png

59 ms

vox-media-logo-fd64ebf31136424ab54ae8780ec56bcdac36d835e0138bc9ece0e7f98a82f574.png

vox-media-logo-fd64ebf31136424ab54ae8780ec56bcdac36d835e0138bc9ece0e7f98a82f574.png

59 ms

wondery-logo-f9809c30c6aae65c4727a377d33fb73f3fb5c0b11db0101ededf56c72eebde30.png

wondery-logo-f9809c30c6aae65c4727a377d33fb73f3fb5c0b11db0101ededf56c72eebde30.png

90 ms

pacific-logo-790472acc8b1a80dd44374580eb4c4cdf484a0fa73881581b18412e24e4cbedd.png

pacific-logo-790472acc8b1a80dd44374580eb4c4cdf484a0fa73881581b18412e24e4cbedd.png

97 ms

cadence13-logo-0b5d5755ec1be75a744cc6801f07a0fb62529ebcbd430db8ab7ee1701cfa1593.png

cadence13-logo-0b5d5755ec1be75a744cc6801f07a0fb62529ebcbd430db8ab7ee1701cfa1593.png

94 ms

waitwhat-logo-efc613d31c48413b8694d60f40fb4ce5ae6809817cace9598668e0ada8cb4252.png

waitwhat-logo-efc613d31c48413b8694d60f40fb4ce5ae6809817cace9598668e0ada8cb4252.png

145 ms

foreverdog-logo-612a85acdba8981c3a5d2306b638bd5ac46078399b1546b8b2eee7e9f3160b6a.png

foreverdog-logo-612a85acdba8981c3a5d2306b638bd5ac46078399b1546b8b2eee7e9f3160b6a.png

117 ms

pushkin-logo-3bfbf17e9df248ebc9b603a5901b8b0b1400160505330e9eeaa2d11eed53b020.png

pushkin-logo-3bfbf17e9df248ebc9b603a5901b8b0b1400160505330e9eeaa2d11eed53b020.png

115 ms

teamcoco-logo-6a6e8d044689690d5a589936afcb789b70e832dde936d00c517c7e076a791d9e.png

teamcoco-logo-6a6e8d044689690d5a589936afcb789b70e832dde936d00c517c7e076a791d9e.png

122 ms

axios-logo-f4db7a89218e4c9770a9579539e19362fb5123f69c4b2e36fea4a6fe08d6ae6c.png

axios-logo-f4db7a89218e4c9770a9579539e19362fb5123f69c4b2e36fea4a6fe08d6ae6c.png

128 ms

sonoro-logo-b46d83c61c871ee7123caee610ab02fe92554fe6ffe104fe4efc13663ce1fd08.svg

sonoro-logo-b46d83c61c871ee7123caee610ab02fe92554fe6ffe104fe4efc13663ce1fd08.svg

128 ms

betches-logo-98d17a732037f9263db2dfdea1431c254bdd6d47e0db1098d9b4ca092fd82bbd.svg

betches-logo-98d17a732037f9263db2dfdea1431c254bdd6d47e0db1098d9b4ca092fd82bbd.svg

147 ms

rooster-teeth-logo-0a9c443ff572e7ea7cb01270b8c88cde2f0286dc8e0a72ed401574c539d6b088.png

rooster-teeth-logo-0a9c443ff572e7ea7cb01270b8c88cde2f0286dc8e0a72ed401574c539d6b088.png

150 ms

dashboard-610d0af1cde84e13ed9666da1586370f98bf65d07d415d4f63af0fdd2a123f29.png

dashboard-610d0af1cde84e13ed9666da1586370f98bf65d07d415d4f63af0fdd2a123f29.png

154 ms

the-verge-6f3b01bd713c52556b64486286b73e41e92249c41d0e71a689dbed74915086ac.png

the-verge-6f3b01bd713c52556b64486286b73e41e92249c41d0e71a689dbed74915086ac.png

161 ms

digiday-logo-870a8ca023e05bcf081e2f698b879ea79e979d3d1a23ef7cc29bd1f47eaa9e4f.png

digiday-logo-870a8ca023e05bcf081e2f698b879ea79e979d3d1a23ef7cc29bd1f47eaa9e4f.png

163 ms

wsj-logo-41b3e38f99f05aae2a98255fc3bf1158104c018e4047ab57281dfb56e806d618.svg

wsj-logo-41b3e38f99f05aae2a98255fc3bf1158104c018e4047ab57281dfb56e806d618.svg

179 ms

techcrunch-logo-adc4fb1b89d75de4f044bcc1d73324da6bc1b5f0523d89c4cc507ad6d6e4cd59.png

techcrunch-logo-adc4fb1b89d75de4f044bcc1d73324da6bc1b5f0523d89c4cc507ad6d6e4cd59.png

180 ms

quartz-logo-b8894b53b254ef01c53658cbd62115bf0e936fd62c23cc6475b4dfb7dbee22c1.png

quartz-logo-b8894b53b254ef01c53658cbd62115bf0e936fd62c23cc6475b4dfb7dbee22c1.png

186 ms

washington-post-logo-356cb7100bde1abcdcebe9d6ddcce3fff506552c858e3493a4fea4e903bc2e91.jpg

washington-post-logo-356cb7100bde1abcdcebe9d6ddcce3fff506552c858e3493a4fea4e903bc2e91.jpg

185 ms

bloomberg-logo-9e5332d3e1c95e84408d88e22935391ce7a08007c4102c2b2731a89d58a6629b.png

bloomberg-logo-9e5332d3e1c95e84408d88e22935391ce7a08007c4102c2b2731a89d58a6629b.png

193 ms

nyt-logo-142eaf78b383dbd2a45a9ea3b13ba4e1a28a477d9afc64b6fdd086296be995f9.png

nyt-logo-142eaf78b383dbd2a45a9ea3b13ba4e1a28a477d9afc64b6fdd086296be995f9.png

201 ms

businessinsider-7215bbc8f9f7d026d8d102b86bce2573382ba070f73eac5e45e1a13d5557576e.png

businessinsider-7215bbc8f9f7d026d8d102b86bce2573382ba070f73eac5e45e1a13d5557576e.png

215 ms

podnews-2ef5f5a45fff1ceab1398aa237bf4424b077184759182f5319b14f76d2570751.png

podnews-2ef5f5a45fff1ceab1398aa237bf4424b077184759182f5319b14f76d2570751.png

219 ms

hotpod-49d25f2304f84111abef19a596679349a21c69824cdb85cc0d5ae80ab571d72a.png

hotpod-49d25f2304f84111abef19a596679349a21c69824cdb85cc0d5ae80ab571d72a.png

220 ms

iab-5b91a11e1be82ad7c72691d02ba2cf7f3a3859a1d5c5a5b39122091e43c96f39.png

iab-5b91a11e1be82ad7c72691d02ba2cf7f3a3859a1d5c5a5b39122091e43c96f39.png

315 ms

soc2-aaebd39e4fa4fa30809af15e04daac0985035a8ee7864f3921d63517cf84d551.png

soc2-aaebd39e4fa4fa30809af15e04daac0985035a8ee7864f3921d63517cf84d551.png

229 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjg.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjg.woff

30 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjg.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjg.woff

39 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjg.woff

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjg.woff

43 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHQ.woff

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHQ.woff

45 ms

hotjar-3269189.js

hotjar-3269189.js

100 ms

61 ms

Accessibility Review

chartable.com accessibility score

82

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

chartable.com best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

chartable.com SEO score

89

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

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

    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 Chartable.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 Chartable.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

chartable.com

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