Wireframing, UX and Web apps
contrast.ie
contrast.ie
The most important point here, IMHO, is that wireframing should be done in a medium that you can change fast without much effort or fear.
This is why I don't like the whole HTML/CSS wireframing technique. That works great if you only have 1 or 2 directions to go in, but what if you're exploring 7? You end up having to manage 7 different html and css files. In fireworks, I just click "duplicate page" and nudge a few UI elements around.
Also, this is a great tool to share with project teams that think wireframing has no place in an Agile or "Lean" methodology. Wireframing can, as you have eloquently put, be very simple and FAST and is not considered a "deliverable", nor should it be. It's a means to the end result of a good solid set of requirements (both functional and UX).
Can't see what your running, but if you use WordPress, just install WP Super Cache instead of (or in addition to) everything in my article ;)