I researched the problem further and found a side benefit of using blobcache. To enable blobcache you edit the web.fig file and set the blobcache line to be enabled. for instance:
<blobcache enabled="true" path="\.(gif|jpg|png|css|js)$" location="C:\blobCache" maxsize="10">
I read up more on blobcache and found that there is a parameter called max-age which if ommitted defaults to, you guessed it 86400. If 1 day is not right then you can specify your own time in seconds.
<blobcache enabled="true" path="\.(gif|jpg|png|css|js)$" location="C:\blobCache" maxsize="10" max-age="86400">
So using blobcache kills two birds with one stone. Not only does it remove the overhead of sql requests and responses by keeping the files locally, but it also allow the clients browser cache to store these files for a set period.
This solved my problem! I can only think that the blobcache feature should be turned on by default instead of off. Performace of pages in sharepoint is not the greatest and this makes a big difference, especially for WAN or remote users.