8.9 sec in total
224 ms
7.7 sec
975 ms
Visit podcast.app now to see the best up-to-date Podcast content for United States and also check out these interesting facts you probably never knew about podcast.app
Listen to your favorite podcasts online.
Visit podcast.appWe analyzed Podcast.app page load time and found that the first response time was 224 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
podcast.app performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value6.0 s
13/100
25%
Value2.4 s
98/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value5.0 s
77/100
10%
224 ms
101 ms
127 ms
161 ms
42 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 41% of them (24 requests) were addressed to the original Podcast.app, 12% (7 requests) were made to Fonts.gstatic.com and 10% (6 requests) were made to Podcast-api-images.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Podcast.app.
Page size can be reduced by 68.9 kB (14%)
508.8 kB
439.9 kB
In fact, the total size of Podcast.app main page is 508.8 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. 65% of websites need less resources to load. Images take 387.2 kB which makes up the majority of the site volume.
Potential reduce by 33.1 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 12.6 kB, which is 30% 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 33.1 kB or 78% of the original size.
Potential reduce by 34.9 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. Podcast images are well optimized though.
Potential reduce by 900 B
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.
Number of requests can be reduced by 14 (28%)
50
36
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Podcast. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
podcast.app
224 ms
bootstrap.min.css
101 ms
css
127 ms
css
161 ms
project.css
42 ms
js
135 ms
jquery.min.js
157 ms
tether.min.js
214 ms
bootstrap.min.js
100 ms
fbevents.js
248 ms
hero-background.png
6637 ms
podcast_logo_15_300x300.jpg
443 ms
ThePodcastApp-icon.png
304 ms
app-store.svg
6610 ms
google-play.png
302 ms
AppHero.png
304 ms
categories-arts.png
302 ms
categories-business.png
349 ms
categories-comedy.png
358 ms
categories-education.png
357 ms
categories-games-hobbies.png
359 ms
categories-government-organizations.png
7026 ms
categories-health.png
388 ms
categories-kids-family.png
387 ms
categories-music.png
398 ms
categories-news-politics.png
564 ms
categories-religion-spirituality.png
6924 ms
categories-science-medicine.png
6928 ms
categories-society-culture.png
699 ms
categories-sports-recreation.png
804 ms
categories-tv-film.png
805 ms
categories-technology.png
7264 ms
waves-separator.png
6637 ms
podcast_logo_357812_300x300.jpeg
563 ms
podcast_logo_733313_300x300.jpeg
566 ms
podcast_logo_732412_300x300.jpeg
565 ms
podcast_logo_49_300x300.jpeg
563 ms
podcast_logo_689047_300x300.jpg
562 ms
analytics.js
289 ms
js
180 ms
js
164 ms
JTURjIg1_i6t8kCHKm45_bZF3gnD-w.ttf
209 ms
JTURjIg1_i6t8kCHKm45_ZpC3gnD-w.ttf
211 ms
JTUSjIg1_i6t8kCHKm459Wlhzg.ttf
348 ms
JTURjIg1_i6t8kCHKm45_cJD3gnD-w.ttf
349 ms
JTURjIg1_i6t8kCHKm45_aZA3gnD-w.ttf
349 ms
JTUQjIg1_i6t8kCHKm45_QpRyS7j.ttf
351 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
351 ms
271816340372213
270 ms
js
55 ms
conversion_async.js
51 ms
collect
274 ms
323 ms
collect
175 ms
53 ms
65 ms
ga-audiences
16 ms
3 ms
nr-1184.min.js
24 ms
podcast.app accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
podcast.app best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
podcast.app SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Podcast.app 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 Podcast.app 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.
podcast.app
Open Graph description is not detected on the main page of Podcast. 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: