Tools & Wizards About Us
johnnpaaul.podbean.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

johnnpaaul.podbean.com

My Podcast Site

Page Load Speed

1.5 sec in total

First Response

396 ms

Resources Loaded

680 ms

Page Rendered

407 ms

johnnpaaul.podbean.com screenshot

About Website

Visit johnnpaaul.podbean.com now to see the best up-to-date Johnnpaaul Podbean content for United States and also check out these interesting facts you probably never knew about johnnpaaul.podbean.com

New podcast weblog

Visit johnnpaaul.podbean.com

Key Findings

We analyzed Johnnpaaul.podbean.com page load time and found that the first response time was 396 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

johnnpaaul.podbean.com performance score

0

Network Requests Diagram

johnnpaaul.podbean.com

396 ms

jquery-1.8.0.min.js

19 ms

mediaelement-and-player.min.js

16 ms

mediaelementplayer.css

13 ms

fonts.css

12 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 28% of them (15 requests) were addressed to the original Johnnpaaul.podbean.com, 23% (12 requests) were made to Podbean.com and 15% (8 requests) were made to D8g345wuhgd7e.cloudfront.net. The less responsive or slowest element that took the longest time to load (396 ms) belongs to the original domain Johnnpaaul.podbean.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 667.9 kB (55%)

Content Size

1.2 MB

After Optimization

540.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnnpaaul.podbean.com main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 636.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 73.1 kB

  • Original 100.0 kB
  • After minification 97.6 kB
  • After compression 26.8 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 73.1 kB or 73% of the original size.

Image Optimization

-8%

Potential reduce by 21.5 kB

  • Original 284.9 kB
  • After minification 263.4 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. Johnnpaaul Podbean images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 418.0 kB

  • Original 636.4 kB
  • After minification 635.0 kB
  • After compression 218.4 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 418.0 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 155.3 kB

  • Original 187.1 kB
  • After minification 174.8 kB
  • After compression 31.8 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. Johnnpaaul.podbean.com needs all CSS files to be minified and compressed as it can save up to 155.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (44%)

Requests Now

43

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johnnpaaul.podbean.com

johnnpaaul.podbean.com

396 ms

jquery-1.8.0.min.js

jquery-1.8.0.min.js

19 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

16 ms

mediaelementplayer.css

mediaelementplayer.css

13 ms

fonts.css

fonts.css

12 ms

aplayer.css

aplayer.css

13 ms

blogstyle.css

blogstyle.css

33 ms

bootstrap.min.css

bootstrap.min.css

36 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

33 ms

css

css

42 ms

fonticon.css

fonticon.css

41 ms

style.css

style.css

32 ms

follow-widgets.js

follow-widgets.js

40 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

36 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

30 ms

bootstrap.min.js

bootstrap.min.js

35 ms

addthis_widget.js

addthis_widget.js

36 ms

share.js

share.js

29 ms

blogtoolbar.php

blogtoolbar.php

165 ms

fonticon.css

fonticon.css

17 ms

body-bg.png

body-bg.png

129 ms

powered_by_podbean.jpg

powered_by_podbean.jpg

127 ms

filesPlays

filesPlays

123 ms

loginInfo

loginInfo

42 ms

loginInfo

loginInfo

42 ms

getBlogFollowingList

getBlogFollowingList

119 ms

getBlogFollowerList

getBlogFollowerList

65 ms

getEpisodeLikeStatus

getEpisodeLikeStatus

72 ms

filesPlays

filesPlays

30 ms

300lo.json

300lo.json

49 ms

icon_pdf.png

icon_pdf.png

16 ms

icon_other.png

icon_other.png

19 ms

iphone-app.png

iphone-app.png

39 ms

android-app-sm.png

android-app-sm.png

19 ms

detail_banner.jpg

detail_banner.jpg

44 ms

miiduu_468x60.gif

miiduu_468x60.gif

16 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

18 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

23 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

41 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

48 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

41 ms

fonticon.woff

fonticon.woff

12 ms

icomoon.woff

icomoon.woff

12 ms

sh.953eb77977227bfd253ee158.html

sh.953eb77977227bfd253ee158.html

37 ms

toolbar.css

toolbar.css

11 ms

toolbar-logo-SM.png

toolbar-logo-SM.png

18 ms

toolbar-logo.png

toolbar-logo.png

12 ms

icon_pdf.png

icon_pdf.png

28 ms

toolbar-bg.png

toolbar-bg.png

25 ms

icon_other.png

icon_other.png

26 ms

h-divider.png

h-divider.png

5 ms

icon-explore.png

icon-explore.png

4 ms

icon-podcast.png

icon-podcast.png

3 ms

SEO Factors

johnnpaaul.podbean.com SEO score

0

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 Johnnpaaul.podbean.com 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 Johnnpaaul.podbean.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

johnnpaaul.podbean.com

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