4.5 sec in total
168 ms
3.6 sec
748 ms
Welcome to drupaldude.com homepage info - get ready to check Drupaldude best content right away, or after learning these important things about drupaldude.com
Visit drupaldude.comWe analyzed Drupaldude.com page load time and found that the first response time was 168 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
drupaldude.com performance score
168 ms
424 ms
304 ms
297 ms
295 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 50% of them (52 requests) were addressed to the original Drupaldude.com, 19% (20 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (792 ms) belongs to the original domain Drupaldude.com.
Page size can be reduced by 346.2 kB (57%)
608.8 kB
262.7 kB
In fact, the total size of Drupaldude.com main page is 608.8 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. 70% of websites need less resources to load. Javascripts take 199.3 kB which makes up the majority of the site volume.
Potential reduce by 60.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. 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 60.3 kB or 86% of the original size.
Potential reduce by 18.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. Drupaldude images are well optimized though.
Potential reduce by 138.9 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 138.9 kB or 70% of the original size.
Potential reduce by 128.3 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. Drupaldude.com needs all CSS files to be minified and compressed as it can save up to 128.3 kB or 86% of the original size.
Number of requests can be reduced by 69 (70%)
99
30
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drupaldude. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
drupaldude.com
168 ms
www.drupaldude.com
424 ms
views.css
304 ms
content-module.css
297 ms
filefield.css
295 ms
fivestar.css
333 ms
small.css
362 ms
lightbox.css
307 ms
node.css
345 ms
poll.css
393 ms
defaults.css
372 ms
system.css
402 ms
system-menus.css
407 ms
user.css
438 ms
ctools.css
573 ms
jquerymenu.css
474 ms
style.css
465 ms
typography.css
476 ms
superfish.css
475 ms
superfish-navbar.css
569 ms
superfish-vertical.css
584 ms
acquia-prosper-style.css
664 ms
blue.css
635 ms
grid16-960.css
675 ms
local.css
649 ms
js_a607a361a9846bac158361bd4aa23798.js
792 ms
show_ads.js
9 ms
adsense_click.js
750 ms
js_dbad26c97197d118ae1686db47855f7e.js
758 ms
re_.js
159 ms
blogger.js
180 ms
thedrupaldude.json
187 ms
secondary-menu-bg.png
245 ms
search-bg.png
244 ms
search-icon.png
243 ms
acquia_prosper_logo.png
242 ms
ad-ipad.jpg
263 ms
App_Store_Badge_EN.jpg
265 ms
book.jpg
267 ms
ad-iphone.jpg
269 ms
delicious.png
275 ms
stumbleit.png
273 ms
reddit.png
275 ms
newsvine.png
277 ms
facebook.png
277 ms
google.png
279 ms
yahoo.png
341 ms
technorati.png
339 ms
feed.png
345 ms
powered-blue-80x15.png
344 ms
ca-pub-4797213982418533.js
73 ms
zrt_lookup.html
210 ms
show_ads_impl.js
89 ms
list-level-1.png
305 ms
button-bg.png
303 ms
pager-bg.png
261 ms
pager-next.png
259 ms
pager-last.png
372 ms
ads
308 ms
osd.js
31 ms
likebox.php
705 ms
ads
493 ms
menu-block-leaf.png
128 ms
ads
355 ms
ads
309 ms
ga.js
72 ms
m_js_controller.js
287 ms
abg.js
312 ms
__utm.gif
53 ms
googlelogo_color_112x36dp.png
216 ms
8371884818957705746
171 ms
favicon
271 ms
favicon
200 ms
nessie_icon_tiamat_white.png
138 ms
s
116 ms
x_button_blue2.png
52 ms
410ucuAGgaJ.css
233 ms
pERLJfhzcxv.css
246 ms
Czh0gDTFcBt.css
267 ms
Ek6lpayKeeB.css
358 ms
EoarYgA68t4.css
300 ms
FAHeNGXgPup.js
401 ms
FJmpeSpHpjS.js
399 ms
0wM5s1Khldu.js
295 ms
1bNoFZUdlYZ.js
294 ms
njO1TPvGzoR.js
397 ms
1QuX41zDRrx.js
395 ms
Oagsvfb4VWi.js
399 ms
m-2AbGY1fWh.js
572 ms
1FCa-btixu2.js
515 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
20 ms
45552_102056376521467_8163358_n.jpg
285 ms
safe_image.php
413 ms
safe_image.php
439 ms
12439227_869622859818105_8609983497494309222_n.jpg
296 ms
12508824_908695745874991_382913305816866666_n.jpg
303 ms
10469948_1441424436110573_6513311959075128992_n.jpg
292 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
68 ms
QDwYpIaRyfG.png
241 ms
pimRBh7B6ER.png
238 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
24 ms
ui
48 ms
activeview
23 ms
drupaldude.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drupaldude.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Drupaldude.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.
drupaldude.com
Open Graph description is not detected on the main page of Drupaldude. 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: