When SpeedSize is integrated into your website, it accesses your original media files through public URLs. If necessary, SpeedSize can also work with non-public content via authenticated access, though it is primarily designed to handle public content.
SpeedSize fetches the original media file when a user requests the asset for the first time. This on-demand fetching means that SpeedSize does not proactively download all images or videos from your site. Fetching is invoked solely by user requests, ensuring that only actively needed files are accessed.
Typically, SpeedSize fetches the original file only once, storing a local copy for internal replication and future use. However, to ensure the best possible latency, the file may be additionally requested from the origin by SpeedSize's edge computing instances early on before the file is replicated internally.
Once the file is replicated, it is cached and ready to serve, ensuring that all subsequent requests are handled from the cache with the fastest load times.