Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

panoply.fm

Panoply - A Premium Podcast Network - Panoply

Page Load Speed

4.8 sec in total

First Response

63 ms

Resources Loaded

2.9 sec

Page Rendered

1.8 sec

panoply.fm screenshot

About Website

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

Slate Magazine introduces Panoply, a podcast network that connects sophisticated listeners with top publishers and thinkers.

Visit panoply.fm

Key Findings

We analyzed Panoply.fm page load time and found that the first response time was 63 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

panoply.fm performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.272

45/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

panoply.fm

63 ms

www.panoply.fm

788 ms

style.css

3 ms

head.js

10 ms

scripts.min.js

65 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 32% of them (38 requests) were addressed to the original Panoply.fm, 65% (77 requests) were made to Podcasts-media-dev.s3.amazonaws.com and 2% (2 requests) were made to Cdn.krxd.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Panoply.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 720.2 kB (29%)

Content Size

2.5 MB

After Optimization

1.8 MB

In fact, the total size of Panoply.fm 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. 85% 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 183.3 kB

  • Original 211.3 kB
  • After minification 179.6 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 31.7 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 183.3 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 90.1 kB

  • Original 1.6 MB
  • After minification 1.5 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. Panoply images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 410.4 kB

  • Original 602.5 kB
  • After minification 601.0 kB
  • After compression 192.1 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 410.4 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 36.4 kB

  • Original 43.9 kB
  • After minification 43.2 kB
  • After compression 7.5 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. Panoply.fm needs all CSS files to be minified and compressed as it can save up to 36.4 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

113

After Optimization

100

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

Accessibility Review

panoply.fm accessibility score

86

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

Best Practices

panoply.fm best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

panoply.fm SEO score

92

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

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 Panoply.fm 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 Panoply.fm 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

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