4.5 sec in total
189 ms
3 sec
1.3 sec
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.tvWe analyzed Whyarewehere.tv page load time and found that the first response time was 189 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whyarewehere.tv performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value9.2 s
1/100
25%
Value8.8 s
15/100
10%
Value140 ms
96/100
30%
Value0.001
100/100
15%
Value9.3 s
32/100
10%
189 ms
178 ms
811 ms
54 ms
90 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 size can be reduced by 1.6 MB (16%)
9.5 MB
7.9 MB
In fact, the total size of Whyarewehere.tv main page is 9.5 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.
Potential reduce by 56.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.
Potential reduce by 1.4 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.
Potential reduce by 63.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 63.9 kB or 30% of the original size.
Potential reduce by 559 B
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.
Number of requests can be reduced by 30 (43%)
70
40
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.
whyarewehere.tv
189 ms
www.whyarewehere.tv
178 ms
www.whyarewehere.tv
811 ms
gtm.js
54 ms
wuh4eif.css
90 ms
ysx8ubk.css
160 ms
itf1eks.css
152 ms
chx7pok.css
183 ms
ljx1hpi.css
155 ms
wwr8ouv.css
143 ms
gdx3olw.css
203 ms
ano8phv.css
233 ms
lve0vvl.css
209 ms
hho0pwe.css
247 ms
ief7khh.css
224 ms
font-awesome.min.css
39 ms
DependencyHandler.axd
423 ms
fixes-overwrite.css
394 ms
jquery.min.js
170 ms
DependencyHandler.axd
494 ms
froogaloop.js
292 ms
DependencyHandler.axd
564 ms
count.js
31 ms
p.css
39 ms
p.css
3 ms
p.css
5 ms
p.css
3 ms
p.css
3 ms
p.css
3 ms
p.css
2 ms
p.css
8 ms
p.css
2 ms
p.css
2 ms
p.css
2 ms
analytics.js
126 ms
whyarewehere.png
156 ms
search-white.png
156 ms
close-white.png
156 ms
wawh-header-tablet.png
491 ms
face2.png
677 ms
1-about-science.png
664 ms
still_scientism-intro.jpg
288 ms
still_reductionism.jpg
489 ms
emergence.png
722 ms
still_science-and-narrartive.jpg
489 ms
2-our-universe.png
749 ms
still_fine-tuning.jpg
569 ms
still_convergence.jpg
579 ms
still_co-operation.jpg
723 ms
10.png
757 ms
still_mathematics.jpg
792 ms
non-material-realities.png
997 ms
still_god-intro.jpg
852 ms
4-knowledge-truth2-mark.png
1121 ms
still_the-limits-of-knowledge.jpg
893 ms
still_beauty-and-truth.jpg
914 ms
still_different-beauties.jpg
943 ms
still_the-sublime.jpg
1050 ms
morality.png
1301 ms
still_moral-truths.jpg
1055 ms
still_moral-instincts.jpg
1073 ms
still_moral-decisions.jpg
1129 ms
still_science-and-morailty.jpg
1252 ms
11.png
1243 ms
still_the-human-species.jpg
1214 ms
still_meaning-introsub01.jpg
1273 ms
jane-goodall-2.jpg
1275 ms
alex-rosenberg.jpg
1350 ms
homepage-wide-1.png
1359 ms
d
79 ms
d
153 ms
fontawesome-webfont.woff
121 ms
d
62 ms
d
36 ms
d
63 ms
d
365 ms
d
164 ms
d
60 ms
d
63 ms
2-platos-cave-2.jpg
1313 ms
collect
36 ms
water-background.jpg
1239 ms
arrow-white.png
1229 ms
whyarewehere.tv accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
whyarewehere.tv 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
whyarewehere.tv SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
EN
EN
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.
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: