Access whobackwhen.com. Who Back When | A Doctor Who Podcast

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

whobackwhen.com

224 ms

whobackwhen.com

326 ms

style.min.css

326 ms

app-b489ab798a.css

368 ms

masterslider.main.css

278 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 51% of them (55 requests) were addressed to the original Whobackwhen.com, 6% (7 requests) were made to Youtube.com and 6% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Whobackwhen.com.

Content Size

3.2 MB

After Optimization

3.1 MB

In fact, the total size of Whobackwhen.com main page is 3.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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 65.0 kB

Original 80.7 kB
After minification 76.8 kB
After compression 15.7 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 65.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 5.7 kB

Original 2.6 MB
After minification 2.6 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. Who Back When images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 28.4 kB

Original 447.5 kB
After minification 444.4 kB
After compression 419.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. This website has mostly compressed JavaScripts.

CSS Optimization

-14%

Potential reduce by 17.6 kB

Original 126.3 kB
After minification 124.9 kB
After compression 108.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. Whobackwhen.com needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 14% of the original size.

Requests Now

103

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Whobackwhen.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 Whobackwhen.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

whobackwhen.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Who Back When | A Doctor Who Podcast - Official Site

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

whobackwhen.com

whobackwhen.com

style.min.css

app-b489ab798a.css

masterslider.main.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

whobackwhen.com

whobackwhen.com

style.min.css

app-b489ab798a.css

masterslider.main.css

custom.css

jquery.min.js

motion-ui.min.css

cookieconsent.min.css

cookieconsent.min.js

hero_menu_styles.css

css

platform.js

frontend_styles.css

hero_static_fonts.css

app-549db2cf85.js

comment-reply.min.js

jquery.easing.min.js

masterslider.min.js

frontend_script.js

frontend_dimensions.js

doctor-who-dido-humanoid.jpg

dinosaur-doctor-who-back-when.jpg

doctor-who-drwho-whobackwhen-the-master.jpg

trial-of-a-time-lord-doctor-who-back-when-2.jpg

post-overlay-blog.png

post-overlay-cast.png

key-to-time-banner-doctor-who-back-when.jpg

whobackwhen-merch-doctor-who-back-when.jpg

icon_rounded_150px.png

facebook.png

youtube.png

twitter.png

itunes.png

instagram.png

rss.png

uxariean-primitive-colony-in-space-doctor-who-back-when.jpg

great-intelligence-doctor-who-back-when.jpg

doctor-who-drwho-whobackwhen-fish-people-atlantis.jpg

doctor-who-cybermat.jpg

paternoster-gang-doctor-who-back-when.jpg

doctor-who-drwho-whobackwhen-ood.jpg

primord-inferno-classic-doctor-who-back-when.jpg