1.4 sec in total
37 ms
1.1 sec
246 ms
Click here to check amazing Discuss Cooking content for United States. Otherwise, check out these important facts you probably never knew about discusscooking.com
Community platform by XenForo®
Visit discusscooking.comWe analyzed Discusscooking.com page load time and found that the first response time was 37 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
discusscooking.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value3.4 s
66/100
25%
Value9.5 s
12/100
10%
Value16,090 ms
0/100
30%
Value0.164
72/100
15%
Value31.1 s
0/100
10%
37 ms
196 ms
10 ms
35 ms
46 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 17% of them (22 requests) were addressed to the original Discusscooking.com, 34% (44 requests) were made to Socialknowledge.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (299 ms) relates to the external source Securepubads.g.doubleclick.net.
Page size can be reduced by 982.7 kB (66%)
1.5 MB
495.9 kB
In fact, the total size of Discusscooking.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 185.9 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 185.9 kB or 76% of the original size.
Potential reduce by 11.9 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. Discuss Cooking images are well optimized though.
Potential reduce by 723.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 723.8 kB or 71% of the original size.
Potential reduce by 61.0 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. Discusscooking.com needs all CSS files to be minified and compressed as it can save up to 61.0 kB or 81% of the original size.
Number of requests can be reduced by 49 (40%)
124
75
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discuss Cooking. 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 as a result speed up the page load time.
discusscooking.com
37 ms
www.discusscooking.com
196 ms
vbulletin_important.css
10 ms
yahoo-dom-event.js
35 ms
connection-min.js
46 ms
vbulletin_global.js
14 ms
ncode_imageresizer.js
7 ms
jquery.min.js
84 ms
vbulletin_md5.js
9 ms
show_ads.js
8 ms
glam_logo.js
9 ms
quant.js
6 ms
dc.js
110 ms
gpt.js
6 ms
pubads_impl_81.js
14 ms
container.html
79 ms
background.gif
76 ms
ads
299 ms
zrt_lookup.html
80 ms
show_ads_impl.js
84 ms
other_communities.png
48 ms
glamadapt_jsrv.act
37 ms
thumb_tsf.png
35 ms
thumb_dc.png
49 ms
thumb_mb.png
34 ms
thumb_aa2.png
35 ms
thumb_bbq.png
35 ms
thumb_er.png
48 ms
thumb_trf.png
47 ms
thumb_u22.png
49 ms
thumb_ski.png
48 ms
thumb_cityprofile.png
52 ms
thumb_ca.png
89 ms
thumb_me.png
55 ms
thumb_d90.png
87 ms
thumb_htc.png
54 ms
thumb_cct.png
55 ms
thumb_jg.png
86 ms
thumb_ford.png
101 ms
thumb_et.png
88 ms
thumb_irv.png
89 ms
thumb_air.png
89 ms
thumb_frf.png
102 ms
thumb_fgrv.png
102 ms
thumb_wtw.png
90 ms
thumb_jayco.png
102 ms
thumb_lcl.png
102 ms
thumb_escape.png
115 ms
thumb_hilo.png
113 ms
thumb_5wf.png
121 ms
thumb_rvpr.png
111 ms
thumb_tc.png
111 ms
thumb_rwo.png
112 ms
thumb_cro.png
113 ms
thumb_thor.png
115 ms
thumb_dutchmen.png
115 ms
thumb_skoolie.png
115 ms
discusscooking.gif
29 ms
googlesearch.gif
29 ms
search.gif
29 ms
tabbar.gif
29 ms
tabborder.gif
28 ms
drop.png
35 ms
menu_bullet.png
41 ms
gradient_alt.gif
40 ms
navbits_start.gif
42 ms
gradient_tcat.gif
40 ms
clear.gif
42 ms
collapse_tcat.gif
45 ms
gradient_thead.gif
80 ms
lastpost.gif
110 ms
cron.php
129 ms
__utm.gif
60 ms
thumb_slc.png
88 ms
thumb_cr.png
88 ms
thumb_cf.png
87 ms
GlamSelectDefaultAds.js
57 ms
thumb_rib.png
86 ms
thumb_boatmad.png
78 ms
thumb_trawler.png
77 ms
thumb_maxum.png
76 ms
thumb_cw2.png
75 ms
ads
155 ms
1_MM_Foodie_160x24_wht.gif
26 ms
jsadimp.gif
26 ms
osd.js
21 ms
spoutable.js
30 ms
pixel;r=921991525;a=p-10KpXr-UTOg_A;fpan=1;fpa=P0-1214271723-1456753864543;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456753864543;tzo=-180;ref=;url=http%3A%2F%2Fwww.discusscooking.com%2F;ogl=url.http%3A%2F%2Fwww%252Ediscusscooking%252Ecom%2F%2Ctitle.Discuss%20Cooking%20-%20Cooking%20Forums%2Cdescription.Cooking%20related%20forum%20where%20lovers%20of%20cooking%20can%20share%20recipes%252C%20ideas%20and%20help%20%2Ctype.article
26 ms
likebox.php
246 ms
c
9 ms
unit.js
19 ms
logo.png
32 ms
v2
58 ms
p
54 ms
abg.js
53 ms
000000_new_ico.gif
83 ms
expansion_embed.js
14 ms
ads
241 ms
m_js_controller.js
42 ms
v2
100 ms
favicon
65 ms
s
22 ms
googlelogo_color_112x36dp.png
36 ms
nessie_icon_tiamat_white.png
8 ms
x_button_blue2.png
8 ms
xYm_UD1pmAz.css
51 ms
TGpOWuX6Pv8.css
58 ms
_rx8naC75Dy.js
73 ms
x5F9OMjKyLw.js
100 ms
ICDbTSzjQEg.js
97 ms
TTCre3391I0.js
99 ms
p
15 ms
c2s
156 ms
283658_435115356511738_944676103_n.jpg
66 ms
523755_435101553179785_958655605_n.jpg
70 ms
12654277_964213423660140_3690485236692229823_n.jpg
68 ms
12662533_10153236311136401_6728050789532169798_n.jpg
69 ms
1471098_10203313280578081_8563650356210360179_n.jpg
68 ms
12718274_1522935848009335_7120849515999681614_n.jpg
78 ms
12243436_10208321136453118_2875224300250010634_n.jpg
79 ms
12647335_672700522833579_6704589800749053305_n.jpg
79 ms
12631474_1711752915703687_2523554767978563971_n.jpg
78 ms
wL6VQj7Ab77.png
29 ms
s7jcwEQH7Sx.png
29 ms
bsredirect5.js
52 ms
adj
101 ms
beacon
101 ms
I6-MnjEovm5.js
55 ms
vlXaquuXMrr.js
54 ms
bst2tv3.html
53 ms
discusscooking.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[accesskey] values are not unique
[id] attributes on active, focusable elements are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
discusscooking.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
discusscooking.com SEO score
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discusscooking.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 Discusscooking.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.
discusscooking.com
Open Graph data is detected on the main page of Discuss Cooking. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: