3.6 sec in total
758 ms
2.6 sec
288 ms
Click here to check amazing Whatthe Fonk content. Otherwise, check out these important facts you probably never knew about whatthefonk.com
Being in the website building business, I like to "keep in the know" and read various resources informing on where website trends are moving. Many companies I work with want to be able to post on thei...
Visit whatthefonk.comWe analyzed Whatthefonk.com page load time and found that the first response time was 758 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.
whatthefonk.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value2.3 s
93/100
25%
Value3.3 s
91/100
10%
Value30 ms
100/100
30%
Value0.002
100/100
15%
Value2.7 s
97/100
10%
758 ms
41 ms
108 ms
91 ms
95 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 22% of them (18 requests) were addressed to the original Whatthefonk.com, 9% (7 requests) were made to Px.owneriq.net and 7% (6 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source I0.wp.com.
Page size can be reduced by 1.2 MB (71%)
1.6 MB
480.1 kB
In fact, the total size of Whatthefonk.com main page is 1.6 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 220.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. 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 220.5 kB or 90% of the original size.
Potential reduce by 7.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. Whatthe Fonk images are well optimized though.
Potential reduce by 862.8 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 862.8 kB or 74% of the original size.
Potential reduce by 68.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. Whatthefonk.com needs all CSS files to be minified and compressed as it can save up to 68.8 kB or 82% of the original size.
Number of requests can be reduced by 52 (73%)
71
19
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatthe Fonk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
whatthefonk.com
758 ms
shareaholic.js
41 ms
wp-emoji-release.min.js
108 ms
styles.css
91 ms
style.css
95 ms
jetpack.css
180 ms
jquery.js
344 ms
jquery-migrate.min.js
139 ms
a4e39a108160839f598ef73d28c002f8.json
66 ms
photon.js
161 ms
jquery.form.min.js
97 ms
scripts.js
106 ms
devicepx-jetpack.js
6 ms
gprofiles.js
58 ms
wpgroho.js
107 ms
masonry.min.js
148 ms
jquery.masonry.min.js
149 ms
functions.js
151 ms
mobile-nav.min.js
161 ms
e-201611.js
5 ms
W3TechsSurvey.png
387 ms
AmazonPromotionalCredit.png
174 ms
IMG_2770.jpg
1273 ms
ridge.gif
114 ms
WhatTheFonk2-300x83.png
113 ms
button-back.gif
113 ms
DoveMenCare.jpg
375 ms
WordPress.jpeg
166 ms
MLK.jpg
378 ms
Screen-Shot-2014-03-20-at-9.51.41-PM.png
377 ms
ga.js
7 ms
shrMain.min.js
41 ms
__utm.gif
53 ms
hovercard.css
70 ms
services.css
72 ms
jquery.min.js
57 ms
g.gif
133 ms
analytics.js
87 ms
pageview.gif
63 ms
app.js
12 ms
app.js
37 ms
vglnk.js
67 ms
partners.js
65 ms
angular.min.js
21 ms
user_info
96 ms
pixel.gif
80 ms
sholic.js
146 ms
usermatch
264 ms
beacon.js
48 ms
pixel.gif
76 ms
cms-sh2c.html
92 ms
shareaholic-icons.woff
5 ms
ping_match.gif
23 ms
2964
34 ms
eexelate.js
71 ms
60 ms
pixel
46 ms
pixel
36 ms
ep
60 ms
ep
63 ms
match-result
42 ms
usermatch
177 ms
rs
5 ms
ecc
65 ms
pixel
14 ms
cm
31 ms
casale
101 ms
Vu8IQsAoJUIAAWqDCJgAAADy%26607
165 ms
153 ms
i.gif
149 ms
pixelssl.htm
196 ms
crum
228 ms
ping
48 ms
crum
219 ms
casale
5 ms
crum
230 ms
rum
229 ms
domains
51 ms
bounce
19 ms
crum
238 ms
ddcssl.htm
130 ms
crum
87 ms
whatthefonk.com accessibility score
whatthefonk.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
whatthefonk.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
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 Whatthefonk.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 Whatthefonk.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.
whatthefonk.com
Open Graph data is detected on the main page of Whatthe Fonk. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: