Tools & Wizards About Us
howwasyourweek.libsyn.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

howwasyourweek.libsyn.com

How Was Your Week with Julie Klausner

Page Load Speed

2.9 sec in total

First Response

113 ms

Resources Loaded

1.5 sec

Page Rendered

1.3 sec

howwasyourweek.libsyn.com screenshot

About Website

Welcome to howwasyourweek.libsyn.com homepage info - get ready to check How Was Your Week Libsyn best content for United States right away, or after learning these important things about howwasyourweek.libsyn.com

In which Julie Klausner asks guests how their week was, and also we learn stuff and have fun.

Visit howwasyourweek.libsyn.com

Key Findings

We analyzed Howwasyourweek.libsyn.com page load time and found that the first response time was 113 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

howwasyourweek.libsyn.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

howwasyourweek.libsyn.com

113 ms

jquery.min.js

33 ms

jquery.validate.min.js

58 ms

jquery.simplemodal.js

64 ms

basic.css

63 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Howwasyourweek.libsyn.com, 23% (28 requests) were made to Html5-player.libsyn.com and 22% (27 requests) were made to Po.st. The less responsive or slowest element that took the longest time to load (688 ms) relates to the external source Html5-player.libsyn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 493.1 kB (56%)

Content Size

874.4 kB

After Optimization

381.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Howwasyourweek.libsyn.com main page is 874.4 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 321.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 134.7 kB

  • Original 154.0 kB
  • After minification 144.1 kB
  • After compression 19.3 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 134.7 kB or 87% of the original size.

Image Optimization

-24%

Potential reduce by 76.4 kB

  • Original 321.9 kB
  • After minification 245.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. Obviously, How Was Your Week Libsyn needs image optimization as it can save up to 76.4 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 188.3 kB

  • Original 287.2 kB
  • After minification 281.0 kB
  • After compression 98.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 188.3 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 93.6 kB

  • Original 111.3 kB
  • After minification 109.6 kB
  • After compression 17.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. Howwasyourweek.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.

Requests Breakdown

Number of requests can be reduced by 80 (68%)

Requests Now

118

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of How Was Your Week 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 40 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

howwasyourweek.libsyn.com

howwasyourweek.libsyn.com

113 ms

jquery.min.js

jquery.min.js

33 ms

jquery.validate.min.js

jquery.validate.min.js

58 ms

jquery.simplemodal.js

jquery.simplemodal.js

64 ms

basic.css

basic.css

63 ms

post-widget.js

post-widget.js

112 ms

ga.js

ga.js

33 ms

235 ms

236 ms

240 ms

237 ms

233 ms

233 ms

254 ms

246 ms

249 ms

282 ms

282 ms

287 ms

503 ms

502 ms

501 ms

500 ms

499 ms

498 ms

591 ms

650 ms

618 ms

602 ms

632 ms

659 ms

688 ms

pcp-sprite-ffffff.png

pcp-sprite-ffffff.png

187 ms

icon_argyle.png

icon_argyle.png

193 ms

__utm.gif

__utm.gif

158 ms

r1post.css

r1post.css

139 ms

status

status

38 ms

check-premium-episodes

check-premium-episodes

313 ms

HWYW_100x100px.png

HWYW_100x100px.png

39 ms

25px_comment_bubble_argyle.png

25px_comment_bubble_argyle.png

37 ms

post-native.png

post-native.png

61 ms

ra1-icoset.png

ra1-icoset.png

199 ms

set-16.png

set-16.png

199 ms

HWYW_770x290pxf.png

HWYW_770x290pxf.png

283 ms

css

css

58 ms

css

css

74 ms

jquery-ui.js

jquery-ui.js

21 ms

jquery-ui.css

jquery-ui.css

24 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

509 ms

jplayer.playlist.js

jplayer.playlist.js

479 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

484 ms

standard.css

standard.css

282 ms

p

p

34 ms

counter

counter

22 ms

counter

counter

22 ms

counter

counter

23 ms

counter

counter

24 ms

counter

counter

23 ms

counter

counter

22 ms

counter

counter

24 ms

counter

counter

23 ms

counter

counter

26 ms

counter

counter

24 ms

counter

counter

24 ms

counter

counter

23 ms

counter

counter

29 ms

counter

counter

141 ms

counter

counter

143 ms

counter

counter

142 ms

counter

counter

142 ms

counter

counter

142 ms

counter

counter

142 ms

counter

counter

145 ms

counter

counter

148 ms

counter

counter

147 ms

counter

counter

147 ms

counter

counter

147 ms

counter

counter

148 ms

p

p

136 ms

p

p

136 ms

p

p

136 ms

p

p

137 ms

p

p

135 ms

p

p

136 ms

p

p

142 ms

p

p

141 ms

p

p

142 ms

p

p

141 ms

p

p

141 ms

p

p

141 ms

p

p

146 ms

p

p

146 ms

p

p

162 ms

p

p

145 ms

p

p

163 ms

p

p

163 ms

p

p

163 ms

p

p

164 ms

p

p

163 ms

p

p

165 ms

p

p

165 ms

p

p

165 ms

copyPaste.js

copyPaste.js

45 ms

beacon.js

beacon.js

43 ms

shareQuote.js

shareQuote.js

27 ms

share2quote.css

share2quote.css

243 ms

player-play-45px.png

player-play-45px.png

202 ms

ui-bg_highlight-soft_75_cccccc_1x100.png

ui-bg_highlight-soft_75_cccccc_1x100.png

201 ms

player-pause-45px.png

player-pause-45px.png

63 ms

slider-handle-45px.png

slider-handle-45px.png

63 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

62 ms

player-libsyn-45px.png

player-libsyn-45px.png

69 ms

p23

p23

67 ms

pixel

pixel

68 ms

ucm

ucm

237 ms

tap.php

tap.php

56 ms

sd

sd

55 ms

pixel

pixel

57 ms

rmxucm

rmxucm

54 ms

ucm

ucm

57 ms

status

status

33 ms

Accessibility Review

howwasyourweek.libsyn.com accessibility score

75

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

howwasyourweek.libsyn.com best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

howwasyourweek.libsyn.com SEO score

87

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Howwasyourweek.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 Howwasyourweek.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.

Social Sharing Optimization

howwasyourweek.libsyn.com

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