1.4 sec in total
88 ms
852 ms
436 ms
Visit wtfpod.libsyn.com now to see the best up-to-date WTF Pod Libsyn content for United States and also check out these interesting facts you probably never knew about wtfpod.libsyn.com
Marc Maron welcomes comedians, actors, directors, writers, authors, musicians and folks from all walks of life to his home for amazingly revealing conversations. Marc's probing, comprehensive intervie...
Visit wtfpod.libsyn.comWe analyzed Wtfpod.libsyn.com page load time and found that the first response time was 88 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
wtfpod.libsyn.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value2.9 s
80/100
25%
Value3.5 s
88/100
10%
Value490 ms
59/100
30%
Value0.22
57/100
15%
Value5.8 s
66/100
10%
88 ms
32 ms
57 ms
62 ms
73 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wtfpod.libsyn.com, 18% (14 requests) were made to Po.st and 16% (13 requests) were made to Html5-player.libsyn.com. The less responsive or slowest element that took the longest time to load (434 ms) relates to the external source My.libsyn.com.
Page size can be reduced by 379.5 kB (55%)
687.2 kB
307.8 kB
In fact, the total size of Wtfpod.libsyn.com main page is 687.2 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. 60% of websites need less resources to load. Javascripts take 287.2 kB which makes up the majority of the site volume.
Potential reduce by 64.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. 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 64.1 kB or 86% of the original size.
Potential reduce by 33.5 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. Obviously, WTF Pod Libsyn needs image optimization as it can save up to 33.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 188.3 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 188.3 kB or 66% of the original size.
Potential reduce by 93.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. Wtfpod.libsyn.com needs all CSS files to be minified and compressed as it can save up to 93.6 kB or 84% of the original size.
Number of requests can be reduced by 54 (70%)
77
23
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WTF Pod Libsyn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
wtfpod.libsyn.com
88 ms
jquery.min.js
32 ms
jquery.validate.min.js
57 ms
jquery.simplemodal.js
62 ms
basic.css
73 ms
post-widget.js
91 ms
ga.js
17 ms
171 ms
170 ms
169 ms
162 ms
172 ms
171 ms
234 ms
353 ms
351 ms
350 ms
icon_argyle.png
135 ms
r1post.css
110 ms
__utm.gif
58 ms
status
55 ms
check-premium-episodes
434 ms
post-native.png
58 ms
ra1-icoset.png
207 ms
set-16.png
204 ms
tiledbg.jpg
201 ms
25px_comment_bubble_argyle.png
56 ms
wtfpod-header.jpg
235 ms
css
52 ms
css
78 ms
jquery-ui.js
38 ms
jquery-ui.css
37 ms
jquery.jplayer.min.js
207 ms
jplayer.playlist.js
219 ms
jquery.mCustomScrollbar.concat.min.js
218 ms
standard.css
246 ms
counter
30 ms
counter
30 ms
counter
25 ms
counter
28 ms
counter
28 ms
counter
33 ms
counter
165 ms
counter
166 ms
counter
167 ms
counter
168 ms
p
158 ms
p
156 ms
p
155 ms
p
157 ms
p
156 ms
p
156 ms
p
156 ms
p
159 ms
p
159 ms
p
159 ms
copyPaste.js
149 ms
beacon.js
143 ms
p23
40 ms
shareQuote.js
28 ms
pixel
179 ms
ucm
7 ms
sd
4 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
166 ms
player-play-45px.png
87 ms
player-pause-45px.png
89 ms
slider-handle-45px.png
141 ms
ui-bg_flat_75_ffffff_40x100.png
86 ms
share2quote.css
86 ms
pixel
60 ms
rmxucm
57 ms
player-libsyn-45px.png
57 ms
tap.php
102 ms
ucm
20 ms
status
10 ms
status
9 ms
status
12 ms
p
6 ms
p
10 ms
p
4 ms
wtfpod.libsyn.com 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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wtfpod.libsyn.com 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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
wtfpod.libsyn.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wtfpod.libsyn.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 Wtfpod.libsyn.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.
wtfpod.libsyn.com
Open Graph data is detected on the main page of WTF Pod Libsyn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: