Nov 24, 2020
"Unable to Locate Resource" coming up for many images that are compressed and served as WebP
I checked and it wasn't our Instagram feed throwing up an error. I've got all images smushed, resized, served as WebP, AND lazy-loading. All possible render-blocking code is deferred. I'm using Autoptimize to optimize code, handle WebP and lazy-load; WP Fastest Cache for caching; and Smush (free) for image optimization. The images in question are all visible on the front-end and the files exist in the directory.
I'm unsure what to check next.
Details
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
All Replies (3)
Nov 24, 2020
Not sure what we can offer without seeing it.
Can you share your URL?
Nov 24, 2020
Hmm, I tried rendering the page with webpagetest.com (after running pagespeed insights, where see the same messages)
Its nitce in that it records a full waterfall of http requests.
It seems most of the cdn.shortpixel.ai requests result in a 302 redirect, apprently back to your domain.
Some of these images then take about 50seconds to come back from your server. Look from about request 55.
Seems your server is a bit overwhelmed. Also note that fully loaded, the page is downloading close to 40Mb of data. that is far from optimized.
That sounds like a LONG time Possibly too long for Lighthouse, such that it "timesout"?