Every resized or converted version is generated on its first request and cached, and the page itself is cached for anonymous visitors after its first render. A deploy or a cache purge resets both. Expect it, and warm the key pages after a deploy by requesting them; keep the set of sizes small so there are fewer versions to generate; and put the same call order (resize, then convert) in every template, or the cache holds every image twice.
Answer
Images
The first visitor to a page waits noticeably longer than the second
More in Images
- An image URL with resize parameters returns the original size
- Images from the old site did not come across during migration
- A grey placeholder box appears on production
- My image came out as a picture tag with sources I did not ask for
- A WebP version is being served to a browser that cannot display it
Was this page helpful?
Your answer goes to the docs team.