list of tools on slide -
advanced aggreggator – advagg – supposed to help with the disappearing CSS! – http://drupal.org/project/advagg
D7 projects: agrcache, core_library
“don’t know if you’ve ever been woken up because your site didn’t look right” – eep. At least I’ve never had that.
the air conditioning in this room IS REALLY LOUD.
problems with not knowing if cache has cleared or not.
gzip, minification, longer browser cache lifetime (sounds like some weird conflict issues between Drupal cache/CSS filename rewriting and browser cache), use google’s cdn for jquery (can that work with ssl?), smart bundling – if you do one change, it’ll only push out new files related to that change – 404 css/js protection – I’m pretty sure that’s a big part of the vanishing CSS issue.
(I wonder if this will help with the vanishing menus.)
css embedded images module – reduces http requests – up to 24k of images (IE restrictions!), so good for tiny layout bits & pieces
Oh, and a bit of quick Googling turns up that the jquery CDN will work over SSL.
cdn module, cookieless_subdomain – so not sending cookies when sending images, makes easier to have parallel domains? either/or: NOT BOTH.
(could/would we run our own cdn?)
files proxy module, file conveyor – not sure if it would be useful in my situation.
changes to .htaccess to extend expiration – “access plus 1 year” – images, css, js – some discussion about query strings and cdns, an issue thread in cdn module queue.
gzip – can be done at php level (inside Drupal) or at apache. sample rules.
if mod_expires, disable etags, if not, enable etags.
putting scripts at the bottom, better to use a module than to do it in the theme: headjs (6 only), labjs (6 and 7?). but some issues with panels, wysiwyg editors. can trim about a second off time. we could probably use it; I’ve done some editing inside panels, but it’s really really rare. headjs requires advagg.
optimizing images – although it sounds like that’s an issue with images uploaded and processed with imagemagick. but might be worth looking into. patch for imageapi. also imageinfo_cache.
advagg_add_css_inline() – not sure about use case for that.
split components across domains, with cdn module. yep, that’s exactly what I thinking that would be. (hilariously, this harks back to an argument C & I got into years and years ago…in which I was completely wrong. thanks, Shelley! but it was good to understand better.)
jquery plugin lazyload.
don’t scale images in html. not generally a problem for me, but might be good for intranet; image resize filter.
favicon in core is 400% bigger than needed. ::facepalm::
showslow.com – every 24 hours, get yslow score, see over time.
google page speed – which I saw in the analytics training I was at earlier this week!
some sprite recommendations – I’m not sure if we have anything that would be good with that.
inline image tags – so, wait, printing the binary code inside the html? – particularly for mobile – although that seems like the opposite of the cdn recommendation.