Tools & Wizards About Us
whyarewehere.tv screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

whyarewehere.tv

Why Are We Here? Science, Meaning and Truth | Why are we here?

Page Load Speed

4.6 sec in total

First Response

374 ms

Resources Loaded

3 sec

Page Rendered

1.2 sec

whyarewehere.tv screenshot

About Website

Welcome to whyarewehere.tv homepage info - get ready to check Why Are We Here best content right away, or after learning these important things about whyarewehere.tv

Why Are We Here? (2017) featuring leading scientists & philosophers discussing questions about science, our universe, knowledge, truth, morality & humanity.

Visit whyarewehere.tv

Key Findings

We analyzed Whyarewehere.tv page load time and found that the first response time was 374 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whyarewehere.tv performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value8.1 s

20/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

whyarewehere.tv

374 ms

www.whyarewehere.tv

277 ms

www.whyarewehere.tv

550 ms

gtm.js

80 ms

wuh4eif.css

117 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 54% of them (45 requests) were addressed to the original Whyarewehere.tv, 24% (20 requests) were made to Use.typekit.net and 13% (11 requests) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Whyarewehere.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (16%)

Content Size

9.4 MB

After Optimization

7.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whyarewehere.tv main page is 9.4 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. 55% of websites need less resources to load. Images take 9.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 56.5 kB

  • Original 65.0 kB
  • After minification 45.3 kB
  • After compression 8.5 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 19.7 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 56.5 kB or 87% of the original size.

Image Optimization

-16%

Potential reduce by 1.4 MB

  • Original 9.2 MB
  • After minification 7.7 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. Obviously, Why Are We Here needs image optimization as it can save up to 1.4 MB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-10%

Potential reduce by 16.2 kB

  • Original 167.6 kB
  • After minification 162.5 kB
  • After compression 151.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 286 B

  • Original 26.1 kB
  • After minification 26.1 kB
  • After compression 25.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. Whyarewehere.tv has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (43%)

Requests Now

70

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whyarewehere.tv

whyarewehere.tv

374 ms

www.whyarewehere.tv

www.whyarewehere.tv

277 ms

www.whyarewehere.tv

www.whyarewehere.tv

550 ms

gtm.js

gtm.js

80 ms

wuh4eif.css

wuh4eif.css

117 ms

ysx8ubk.css

ysx8ubk.css

222 ms

itf1eks.css

itf1eks.css

214 ms

chx7pok.css

chx7pok.css

224 ms

ljx1hpi.css

ljx1hpi.css

181 ms

wwr8ouv.css

wwr8ouv.css

193 ms

gdx3olw.css

gdx3olw.css

183 ms

ano8phv.css

ano8phv.css

312 ms

lve0vvl.css

lve0vvl.css

228 ms

hho0pwe.css

hho0pwe.css

297 ms

ief7khh.css

ief7khh.css

296 ms

font-awesome.min.css

font-awesome.min.css

38 ms

DependencyHandler.axd

DependencyHandler.axd

96 ms

fixes-overwrite.css

fixes-overwrite.css

360 ms

jquery.min.js

jquery.min.js

515 ms

DependencyHandler.axd

DependencyHandler.axd

641 ms

froogaloop.js

froogaloop.js

282 ms

DependencyHandler.axd

DependencyHandler.axd

812 ms

count.js

count.js

25 ms

p.css

p.css

21 ms

p.css

p.css

3 ms

p.css

p.css

3 ms

p.css

p.css

2 ms

p.css

p.css

3 ms

p.css

p.css

3 ms

p.css

p.css

2 ms

p.css

p.css

3 ms

p.css

p.css

3 ms

p.css

p.css

3 ms

p.css

p.css

3 ms

analytics.js

analytics.js

110 ms

whyarewehere.png

whyarewehere.png

141 ms

search-white.png

search-white.png

174 ms

close-white.png

close-white.png

435 ms

wawh-header-tablet.png

wawh-header-tablet.png

553 ms

face2.png

face2.png

355 ms

1-about-science.png

1-about-science.png

994 ms

still_scientism-intro.jpg

still_scientism-intro.jpg

384 ms

still_reductionism.jpg

still_reductionism.jpg

553 ms

emergence.png

emergence.png

907 ms

still_science-and-narrartive.jpg

still_science-and-narrartive.jpg

702 ms

2-our-universe.png

2-our-universe.png

753 ms

still_fine-tuning.jpg

still_fine-tuning.jpg

601 ms

still_convergence.jpg

still_convergence.jpg

633 ms

still_co-operation.jpg

still_co-operation.jpg

708 ms

10.png

10.png

813 ms

still_mathematics.jpg

still_mathematics.jpg

895 ms

non-material-realities.png

non-material-realities.png

917 ms

still_god-intro.jpg

still_god-intro.jpg

887 ms

4-knowledge-truth2-mark.png

4-knowledge-truth2-mark.png

1059 ms

still_the-limits-of-knowledge.jpg

still_the-limits-of-knowledge.jpg

1007 ms

still_beauty-and-truth.jpg

still_beauty-and-truth.jpg

1047 ms

still_different-beauties.jpg

still_different-beauties.jpg

1036 ms

still_the-sublime.jpg

still_the-sublime.jpg

1064 ms

morality.png

morality.png

1229 ms

still_moral-truths.jpg

still_moral-truths.jpg

1212 ms

still_moral-instincts.jpg

still_moral-instincts.jpg

1216 ms

still_moral-decisions.jpg

still_moral-decisions.jpg

1226 ms

still_science-and-morailty.jpg

still_science-and-morailty.jpg

1195 ms

11.png

11.png

1171 ms

still_the-human-species.jpg

still_the-human-species.jpg

1283 ms

still_meaning-introsub01.jpg

still_meaning-introsub01.jpg

1321 ms

jane-goodall-2.jpg

jane-goodall-2.jpg

1381 ms

alex-rosenberg.jpg

alex-rosenberg.jpg

1336 ms

d

d

69 ms

d

d

68 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

69 ms

d

d

30 ms

d

d

29 ms

d

d

30 ms

d

d

30 ms

d

d

31 ms

d

d

31 ms

d

d

32 ms

collect

collect

38 ms

homepage-wide-1.png

homepage-wide-1.png

1257 ms

2-platos-cave-2.jpg

2-platos-cave-2.jpg

1187 ms

water-background.jpg

water-background.jpg

1208 ms

arrow-white.png

arrow-white.png

1144 ms

Accessibility Review

whyarewehere.tv accessibility score

68

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

whyarewehere.tv best practices score

83

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

SEO Factors

whyarewehere.tv SEO score

85

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

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Whyarewehere.tv 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 Whyarewehere.tv 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

whyarewehere.tv

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