150K worth of JS doesn’t seem too bad in my eyes, considering the level of interactivity here (not just for the filtering, but also for the input dialog). Almost half of the 150K is actual data, which is embedded into the JS file directly.
To put things into perspective: the preview images are around 20–60K each, so if you scroll the entire list, you end up downloading ~5M. If at all, this is where I’d start to look at in terms of optimising bandwidth.
Comments
150K worth of JS doesn’t seem too bad in my eyes, considering the level of interactivity here (not just for the filtering, but also for the input dialog). Almost half of the 150K is actual data, which is embedded into the JS file directly.
To put things into perspective: the preview images are around 20–60K each, so if you scroll the entire list, you end up downloading ~5M. If at all, this is where I’d start to look at in terms of optimising bandwidth.
I did not realize half the payload was the data itself!