2 sec in total
158 ms
1.7 sec
114 ms
Welcome to whatcamebefore.com homepage info - get ready to check What Came Before best content for United States right away, or after learning these important things about whatcamebefore.com
Watch the video that will change your life! TV and movie star Steve-O introduces you to someone you'll never forget.
Visit whatcamebefore.comWe analyzed Whatcamebefore.com page load time and found that the first response time was 158 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
whatcamebefore.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.8 s
54/100
25%
Value33.0 s
0/100
10%
Value42,880 ms
0/100
30%
Value0.001
100/100
15%
Value53.8 s
0/100
10%
158 ms
72 ms
24 ms
44 ms
49 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 Whatcamebefore.com, 8% (4 requests) were made to W.sharethis.com and 6% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (616 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 631.2 kB (72%)
874.1 kB
242.9 kB
In fact, the total size of Whatcamebefore.com main page is 874.1 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. 45% of websites need less resources to load. Javascripts take 540.0 kB which makes up the majority of the site volume.
Potential reduce by 16.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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 12% 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 16.3 kB or 72% of the original size.
Potential reduce by 2.8 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, What Came Before needs image optimization as it can save up to 2.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 373.0 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 373.0 kB or 69% of the original size.
Potential reduce by 239.1 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. Whatcamebefore.com needs all CSS files to be minified and compressed as it can save up to 239.1 kB or 83% of the original size.
Number of requests can be reduced by 25 (53%)
47
22
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Came Before. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
whatcamebefore.com
158 ms
www.whatcamebefore.com
72 ms
normalize.css
24 ms
main.css
44 ms
modernizr-2.6.1.min.js
49 ms
buttons.js
12 ms
jquery.min.js
28 ms
plugins.js
98 ms
main.js
98 ms
all.js
285 ms
back_tile.jpg
90 ms
what_came_before.jpg
99 ms
share_on_fb_BUTTON.gif
91 ms
free_veg_guide_BUTTON.gif
91 ms
overlay_tile.png
92 ms
tweet_video_BUTTON.gif
92 ms
FreeVegetarianInformation.gif
98 ms
farmSanc_logo.png
99 ms
ga.js
85 ms
getAllAppDefault.esi
59 ms
pNxcylWLEH8
97 ms
__utm.gif
19 ms
getSegment.php
168 ms
checkOAuth.esi
57 ms
www-embed-player-vflfNyN_r.css
57 ms
www-embed-player.js
81 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
55 ms
ad_status.js
57 ms
t.dhj
90 ms
159 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
83 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
82 ms
xd_arbiter.php
249 ms
xd_arbiter.php
432 ms
t.dhj
26 ms
cm
21 ms
x35248
109 ms
s-3271.xgi
16 ms
hbpix
36 ms
13 ms
xrefid.xgi
7 ms
pixel
21 ms
14 ms
pixel
20 ms
2981
23 ms
ping
60 ms
like.php
85 ms
qeKvIRsJabD.js
552 ms
LVx-xkvaJ0b.png
616 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
14 ms
buttons.ab966a004186897711de4a5ed256c924.css
6 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
3 ms
st.1188278743c14064d5e8ae56c8ada29c.js
6 ms
whatcamebefore.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
whatcamebefore.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
whatcamebefore.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatcamebefore.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 Whatcamebefore.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
whatcamebefore.com
Open Graph data is detected on the main page of What Came Before. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: