2.5 sec in total
248 ms
1.9 sec
277 ms
Welcome to ivehadthat.com homepage info - get ready to check Ivehadthat best content for United States right away, or after learning these important things about ivehadthat.com
Cigars, whiskey, craft beer, discussion forums and a community journal of all the cigars, bourbon, scotch, and beer we have tried.
Visit ivehadthat.comWe analyzed Ivehadthat.com page load time and found that the first response time was 248 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ivehadthat.com performance score
248 ms
136 ms
114 ms
109 ms
174 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 34% of them (20 requests) were addressed to the original Ivehadthat.com, 12% (7 requests) were made to Apis.google.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (610 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 264.9 kB (47%)
567.4 kB
302.5 kB
In fact, the total size of Ivehadthat.com main page is 567.4 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. 60% of websites need less resources to load. Javascripts take 375.5 kB which makes up the majority of the site volume.
Potential reduce by 38.7 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 38.7 kB or 76% of the original size.
Potential reduce by 11.4 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. Ivehadthat images are well optimized though.
Potential reduce by 192.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 192.4 kB or 51% of the original size.
Potential reduce by 22.4 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. Ivehadthat.com needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 82% of the original size.
Number of requests can be reduced by 25 (48%)
52
27
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ivehadthat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ivehadthat.com
248 ms
css.php
136 ms
css.php
114 ms
css.php
109 ms
jquery-1.11.0.min.js
174 ms
xenforo.js
213 ms
jquery.cookie.js
68 ms
functions.js
101 ms
css
27 ms
font-awesome.css
6 ms
adsbygoogle.js
7 ms
ga.js
8 ms
__utm.gif
15 ms
noise_2.png
53 ms
icon_16.png
52 ms
logo.png
55 ms
logo-cigar.png
51 ms
logo-beer.png
55 ms
logo-whiskey.png
53 ms
nodeicons.png
87 ms
cigars-bourbon-craft-beer-925x150.jpg
207 ms
iTunes-Button.png
87 ms
Android-Button.png
86 ms
social_sprite.png
85 ms
ca-pub-3016814245862061.js
163 ms
zrt_lookup.html
216 ms
show_ads_impl.js
159 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
145 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
144 ms
fontawesome-webfont.woff
30 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
200 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
200 ms
counter.js
56 ms
t.php
180 ms
sdk.js
371 ms
client:plusone.js
165 ms
widgets.js
77 ms
ads
278 ms
osd.js
33 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
9 ms
deferred.php
234 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
17 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
27 ms
fastbutton
125 ms
postmessageRelay
41 ms
3193398744-postmessagerelay.js
58 ms
rpc:shindig_random.js
36 ms
jot
125 ms
cb=gapi.loaded_0
57 ms
cb=gapi.loaded_1
29 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
66 ms
cb=gapi.loaded_0
38 ms
132 ms
xd_arbiter.php
213 ms
xd_arbiter.php
416 ms
like.php
91 ms
TY3MhkXpWJ-.js
546 ms
LVx-xkvaJ0b.png
610 ms
ivehadthat.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ivehadthat.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 Ivehadthat.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.
ivehadthat.com
Open Graph description is not detected on the main page of Ivehadthat. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: