As long as there is always a fresh call to the Airtable REST API with each visit, you should be fine.
If upon every visit your page requests the URL from API, this should be OK, but would be best suited for page with small number of visits.
If you expect high number of traffic it would be best to cache those images somewhere. Not sure what exactly you are using to build your page - but if React - Next JS has a fantastic cached and optimized image element (including responsive and format optimization):
As image source you could use NextJs API route, which would make request to Airtable API. This works with high traffic volume, but also also you can set how often to revalidate and re-request the image from Airtable.
As long as there is always a fresh call to the Airtable REST API with each visit, you should be fine.
Thank you! Yes at the moment I am requesting it with each visit. Do you think this might be an issue with Cloudfare?
If upon every visit your page requests the URL from API, this should be OK, but would be best suited for page with small number of visits.
If you expect high number of traffic it would be best to cache those images somewhere. Not sure what exactly you are using to build your page - but if React - Next JS has a fantastic cached and optimized image element (including responsive and format optimization):
As image source you could use NextJs API route, which would make request to Airtable API. This works with high traffic volume, but also also you can set how often to revalidate and re-request the image from Airtable.
That’s pretty neat, thank you! Sadly the client wanted the project to be built in Framer, so I can’t go the NextJS route. And because we don’t have access to routing inside Framer, I need to load info from Airtable using url params, with each visit, as there is no dynamic routing. Luckily, it is a very low traffic site.
