We are actually exceeding our quota, with 50% of the quota being used up by http://localhost:5050/
My guess is that this is our development version. Is it possible for us to avoid hitting the cloudinary when developing and instead use a stub?
Also, for the event details page, I noticed that we do not apply a transform. Such a transform could downsample rather large images and also preserve bandwidth. @InciteDemocracy mentioned that we could reduce the image size design wise since some are huge and overwhelm the space visually (I could be wrong). Maybe a max width/height while preserving the aspect ratio would be a good solution?
This is for sure a stopgap measure since exceeding bandwidth on dev instances is a bad sign for any full scale launch, but this at least buys us some time to either use some form of caching
We are actually exceeding our quota, with 50% of the quota being used up by http://localhost:5050/
My guess is that this is our development version. Is it possible for us to avoid hitting the cloudinary when developing and instead use a stub?
Also, for the event details page, I noticed that we do not apply a transform. Such a transform could downsample rather large images and also preserve bandwidth. @InciteDemocracy mentioned that we could reduce the image size design wise since some are huge and overwhelm the space visually (I could be wrong). Maybe a max width/height while preserving the aspect ratio would be a good solution?
This is for sure a stopgap measure since exceeding bandwidth on dev instances is a bad sign for any full scale launch, but this at least buys us some time to either use some form of caching