I simply can’t wrap my head around why these statically served images are being delayed(see first image depicting network waterfall below). AFAIK, most of the served files are served parallel with http2, depending on what file initiates the fetch. Now, the images that are stalling are enqueued by the index, which is the same file that fetches the images that are loading just fine. I find that strange.
Important note: when everything is previously cached, all the images load as quickly as expected. But I still don’t understand what the issue is because:
Image of network waterfall
image of network waterfall
Image of total enqueue delay
image of total enqueue / delay
If it was a JS or CSS render block, wouldn’t the first two images also stall?
I can’t imagine it can be a cache issue, since the delayed images are very small file size SVG’s.
Considering the loose request constraints of http2, I can’t imagine that being an issue.
I’m simply trying to understand the mechanisms at hand here. They stall for a solid 200ms. That’s pretty substantial considering the page generally loads within less than a second. Ideally if possible I’d like to get rid of that stall to reduce the load time.
You need to sign in to view this answers
