A couple other ideas include:

Showing the bitrate of MP3 files on the Library tab.

Using standard HTTP gzip encoding for search results or other traffic that could be compressed to save bandwidth. Web browsers send an "Accept-encoding: gzip" header to a server to tell it it's OK to send a compressed response. The server will optionally send a "Content-encoding: gzip" header in the response if the response is compressed.

The ability to edit the text string I've searched for if I typo something. I think my only option currently is to close the fscked up search tab and type it in again.