2.6 sec in total
53 ms
2.3 sec
282 ms
Visit whatdoesjohnknow.com now to see the best up-to-date Whatdoesjohnknow content and also check out these interesting facts you probably never knew about whatdoesjohnknow.com
Explore the world of bourbon, scotch, and beyond with Whisky Advocates in-depth articles, informative videos, and thousands of reviews.
Visit whatdoesjohnknow.comWe analyzed Whatdoesjohnknow.com page load time and found that the first response time was 53 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
whatdoesjohnknow.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value13.7 s
0/100
25%
Value10.8 s
7/100
10%
Value780 ms
37/100
30%
Value0.022
100/100
15%
Value19.5 s
2/100
10%
53 ms
82 ms
1227 ms
40 ms
44 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whatdoesjohnknow.com, 85% (80 requests) were made to Whiskyadvocate.com and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Whiskyadvocate.com.
Page size can be reduced by 798.2 kB (43%)
1.8 MB
1.0 MB
In fact, the total size of Whatdoesjohnknow.com main page is 1.8 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 792.2 kB which makes up the majority of the site volume.
Potential reduce by 101.6 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 16.0 kB, which is 13% 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 101.6 kB or 82% of the original size.
Potential reduce by 53.6 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. Whatdoesjohnknow images are well optimized though.
Potential reduce by 512.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 512.1 kB or 68% of the original size.
Potential reduce by 130.9 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. Whatdoesjohnknow.com needs all CSS files to be minified and compressed as it can save up to 130.9 kB or 73% of the original size.
Number of requests can be reduced by 47 (55%)
85
38
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatdoesjohnknow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
whatdoesjohnknow.com
53 ms
www.whiskyadvocateblog.com
82 ms
whiskyadvocate.com
1227 ms
style.css
40 ms
flexslider.css
44 ms
css
60 ms
jquery-1.8.3.min.js
51 ms
jquery.flexslider.js
40 ms
jquery.carouFredSel-6.1.0-packed.js
45 ms
functions.js
41 ms
formidablepro.css
42 ms
thickbox.css
40 ms
wpsc-default.css
45 ms
compatibility.css
40 ms
styles.css
41 ms
addtoany.min.css
43 ms
gold_cart.css
43 ms
jquery.js
44 ms
jquery-migrate.min.js
47 ms
wp-e-commerce.js
43 ms
jquery.livequery.js
45 ms
user.js
43 ms
thickbox.js
41 ms
jquery.query.js
42 ms
gold_cart.js
44 ms
dashicons.min.css
49 ms
thickbox.css
46 ms
FancyZoom.js
46 ms
FancyZoomHTML.js
47 ms
adddomloadevent.js
47 ms
jquery.form.min.js
45 ms
scripts.js
47 ms
thickbox.js
46 ms
underscore.min.js
244 ms
shortcode.min.js
46 ms
media-upload.min.js
46 ms
core.min.js
49 ms
widget.min.js
46 ms
tabs.min.js
49 ms
style.css
40 ms
utils.min.js
230 ms
editor.min.js
231 ms
wp-emoji-release.min.js
325 ms
ga.js
279 ms
gpt.js
270 ms
page.js
220 ms
header.png
209 ms
logo.png
208 ms
search.png
209 ms
arrow.png
210 ms
f.png
212 ms
t.png
213 ms
wf-300x250.jpg
211 ms
big-arrow.png
212 ms
timthumb.php
217 ms
timthumb.php
214 ms
timthumb.php
213 ms
timthumb.php
217 ms
timthumb.php
216 ms
timthumb.php
219 ms
timthumb.php
221 ms
islay.jpg
213 ms
widget-arrow.png
215 ms
img2.jpg
217 ms
box-img1.png
215 ms
medium-arrow.png
214 ms
tasting1-148x148.jpg
215 ms
cut-crystal-2-148x148.jpg
215 ms
hats-148x148.jpg
215 ms
whiskyfest-polo-shirt-148x148.jpg
218 ms
Bar-towel11-14-148x148.jpg
217 ms
nosing-glasses-set-of-six-148x148.jpg
217 ms
glencairn-whisky-nosing-glasses-148x148.jpg
217 ms
glencairn-wide-bowl-148x148.jpg
220 ms
wide-bottom-set-of-six-148x148.jpg
220 ms
water-jug-148x148.jpg
219 ms
bottega-whisky-tots-148x148.jpg
220 ms
neat-glass-148x148.jpg
225 ms
subscribe.png
225 ms
bullet.png
223 ms
helveticaneue-thin-webfont.woff
212 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
110 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
111 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
110 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
110 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
111 ms
pubads_impl_82.js
104 ms
__utm.gif
149 ms
container.html
194 ms
loadingAnimation.gif
30 ms
zoom-spin-1.png
25 ms
spacer.gif
22 ms
closebox.png
23 ms
zoom-caption-fill.png
23 ms
whatdoesjohnknow.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Form elements do not have associated labels
whatdoesjohnknow.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
whatdoesjohnknow.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
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 Whatdoesjohnknow.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 Whatdoesjohnknow.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.
whatdoesjohnknow.com
Open Graph data is detected on the main page of Whatdoesjohnknow. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: