Tools & Wizards About Us
pca.st screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pca.st

Web Player - Pocket Casts

Page Load Speed

2.1 sec in total

First Response

9 ms

Resources Loaded

1.5 sec

Page Rendered

537 ms

pca.st screenshot

About Website

Visit pca.st now to see the best up-to-date Pca content for United States and also check out these interesting facts you probably never knew about pca.st

Listen to your favorite podcasts online, in your browser. Discover the world's most powerful podcast player.

Visit pca.st

Key Findings

We analyzed Pca.st page load time and found that the first response time was 9 ms and then it took 2.1 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

pca.st performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

pca.st

9 ms

pca.st

29 ms

www.pocketcasts.com

83 ms

pocketcasts.com

42 ms

style.min.css

180 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Pca.st, 37% (25 requests) were made to Pocketcasts.com and 28% (19 requests) were made to 149729932.v2.pressablecdn.com. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Pocketcasts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.4 kB (26%)

Content Size

835.6 kB

After Optimization

617.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pca.st main page is 835.6 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. 55% of websites need less resources to load. Images take 439.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 107.5 kB

  • Original 138.0 kB
  • After minification 136.4 kB
  • After compression 30.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 107.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 221 B

  • Original 439.4 kB
  • After minification 439.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. Pca images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 100.1 kB

  • Original 206.9 kB
  • After minification 202.4 kB
  • After compression 106.9 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 100.1 kB or 48% of the original size.

CSS Optimization

-21%

Potential reduce by 10.6 kB

  • Original 51.2 kB
  • After minification 44.3 kB
  • After compression 40.7 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. Pca.st needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (39%)

Requests Now

57

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pca.st

pca.st

9 ms

pca.st

pca.st

29 ms

www.pocketcasts.com

www.pocketcasts.com

83 ms

pocketcasts.com

pocketcasts.com

42 ms

style.min.css

style.min.css

180 ms

style.min.css

style.min.css

193 ms

app-compat.css

app-compat.css

201 ms

ponyfill.css

ponyfill.css

208 ms

theme.css

theme.css

203 ms

jetpack.css

jetpack.css

210 ms

pocketcasts.com

pocketcasts.com

661 ms

hero-image-xl.jpg

hero-image-xl.jpg

206 ms

hooks.min.js

hooks.min.js

182 ms

i18n.min.js

i18n.min.js

169 ms

i18n-loader.js

i18n-loader.js

203 ms

js

js

226 ms

mc-validate.js

mc-validate.js

219 ms

wp-polyfill.min.js

wp-polyfill.min.js

164 ms

url.min.js

url.min.js

165 ms

jp-search.js

jp-search.js

198 ms

w.js

w.js

189 ms

popper.js

popper.js

205 ms

app.js

app.js

205 ms

paddle.js

paddle.js

204 ms

smooth-scroll.js

smooth-scroll.js

209 ms

tracks.js

tracks.js

209 ms

e-202431.js

e-202431.js

196 ms

promo-icon.svg

promo-icon.svg

131 ms

free-icon.svg

free-icon.svg

131 ms

easy-icon.svg

easy-icon.svg

130 ms

curated-icon.svg

curated-icon.svg

133 ms

newspaper-icon.svg

newspaper-icon.svg

132 ms

lifehacker-dark.svg

lifehacker-dark.svg

170 ms

nyt.svg

nyt.svg

174 ms

the-verge.svg

the-verge.svg

171 ms

wired.svg

wired.svg

173 ms

smh.svg

smh.svg

171 ms

fast-company.svg

fast-company.svg

184 ms

time.svg

time.svg

192 ms

pc-magazine.svg

pc-magazine.svg

178 ms

business-insider.svg

business-insider.svg

185 ms

lifehacker.svg

lifehacker.svg

180 ms

engadget.svg

engadget.svg

195 ms

android-authority.svg

android-authority.svg

196 ms

mkbhd.svg

mkbhd.svg

197 ms

roundel.svg

roundel.svg

200 ms

logo-footer.svg

logo-footer.svg

199 ms

support.svg

support.svg

201 ms

automattic-logo.svg

automattic-logo.svg

203 ms

hero-image-md.jpg

hero-image-md.jpg

191 ms

hero-image-xs.jpg

hero-image-xs.jpg

193 ms

orange-phone.png

orange-phone.png

200 ms

ZDNet_logo_2022_2.png

ZDNet_logo_2022_2.png

175 ms

google-play.svg

google-play.svg

56 ms

app-store.svg

app-store.svg

55 ms

g.gif

g.gif

52 ms

w.js

w.js

25 ms

track.js

track.js

51 ms

g.gif

g.gif

42 ms

Retina-Book.woff

Retina-Book.woff

40 ms

Retina-Medium.woff

Retina-Medium.woff

26 ms

Retina-Light.woff

Retina-Light.woff

24 ms

Retina-ExLight.woff

Retina-ExLight.woff

26 ms

Retina-BooThink.woff

Retina-BooThink.woff

646 ms

Retina-Bold.woff

Retina-Bold.woff

26 ms

g.gif

g.gif

24 ms

track.gif

track.gif

30 ms

Accessibility Review

pca.st accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

pca.st best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pca.st SEO score

93

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

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 Pca.st 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 Pca.st 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

pca.st

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