Image Optimization still coming through even though I no longer use next/image

[JamesSingleton]

Summary

I use Sanity CMS and since they can handle image optimization, I switched over to using the sanity-image library as my website was hitting the 1,000 images almost every single time the period refreshed. I switched to this around September 5th and if you take a look at the image below, you will see that for Redshirt Sports, there are still requests coming through for it.

The only place I use next/image in my application is for react-tweet but all of these requests are for Sanity.io URLs.

Example

No response

Steps to Reproduce

N/A

[amyegan]

Hi @JamesSingleton! Do you have a minimal reproducible example that we can use to help with debugging?

[JamesSingleton]

@amyegan, I don't even know how I would provide a minimal reproducible example for this to be honest. The only place I am using next/image in my application is for react-tweet per the documentation. Like I mentioned I moved away from using next/image on September 5th but somehow almost 50% of my image utilization is coming from this particular website.

For example, these images were optimized today:

• https://cdn.sanity.io/images/8pbt9f8w/production/22cabf9908a0fb6b176211e6ee6f71b1671de231-1920x1280.webp?rect=0,78,1920,1125&w=1024&h=600&fit=min&auto=format
• https://cdn.sanity.io/images/8pbt9f8w/production/888db9ff532ad9cb9cb2d1dd8e3483020b94c1cf-1920x1280.webp?rect=153,0,1707,1280&w=640&h=480&q=40&fit=min&auto=format
• https://cdn.sanity.io/images/8pbt9f8w/production/e59c1a002fc7761c394913a6686fe28f02f55c1b-1395x785.webp?rect=0,44,1395,698&w=400&h=200&q=40&fit=min&auto=format
• https://cdn.sanity.io/images/8pbt9f8w/production/fc77136e00b1a78b93ca6fdf916036cc5a19ec15-1920x1080.webp?rect=240,0,1440,1080&w=640&h=480&q=40&fit=min&auto=format

I don't know if there is some super old cache somewhere that is still referencing code that is using next/image or what.

[JamesSingleton]

@amyegan following up on this on what's the best approach to get some help on this. I am at 50% usage

I am still only using next/image in my react-tweet component like that documentation says. However, it's optimizing things like https://cdn.sanity.io/images/8pbt9f8w/production/da1457e3c70ff469e01d8bdb601827fb0860a886-1920x1080.webp?rect=0,60,1920,960&w=400&h=200&q=40&fit=min&auto=format

https://cdn.sanity.io/images/8pbt9f8w/production/ccff2cea01ff119554c769578f3f44035a57a2fd-2000x1333.jpg?rect=112,0,1777,1333&w=640&h=480&q=40&fit=min&auto=format

These articles were published over a year ago.

[amyegan]

I'm still not able to reproduce the issue in my test project. If you're able to provide a minimal reproducible example, that would help me investigate the issue.

Without knowing more, the things I can recommend to try are:

• Add unoptimized to the images
• Check if anything is accessing an older deployment's unique generated URL

[JamesSingleton]

Ah! How can I see if something is accessing an older deployment URL? That might be it, I remember seeing a generated URL showing up in some of my SEO reports before.

[JamesSingleton]

Hi @amyegan,

Circling back to this as it has been about 2 weeks and I am still seeing image optimization requests for a project that no longer uses next/image and was curious if there is any way to see what URL users are hitting in order to cause this image optimization request.

[JamesSingleton]

Hoping I can still get some help from Vercel support about image optimization requests coming in for a website that no longer uses Vercel for image optimization

[leerob]

Closing a PR does not delete the Preview Deployment. Are you confident there is no usage of next/image that is optimizing images in your project? If you want to narrow it down further, you can delete past preview deployments from the dashboard or through the API.

[JamesSingleton]

These are the only references for next/image in my repo

with that second one being

const TweetComponents: TwitterComponents = {
  AvatarImg: (props) => <Image {...props} alt={props.alt} />,
  MediaImg: (props) => <Image {...props} alt={props.alt} fill unoptimized />,
}

And these are not Tweet images, they are Sanity images. Oh I am going to have to manually click into every single deployment preview and delete them 🙈 what is the API route? Preview deployments go back 853 days for me.

[JamesSingleton]

I deleted the preview deployments from what was showing as "Active" for previous PRs that I had opened but closed 🤞🏼 that was the cause but should probably clean up 800+ days of preview URLs

[JamesSingleton]

So even though I deleted the ones listed as "active" I am still getting optimizations for this particular website 4 days afterwards. I am starting to think 1 of 2 things is happening:

1. There is some super old cached version floating around somewhere that keeps getting hit
2. One of my preview URLs that wasn't under "active" is getting hit. Unfortunately, I don't know if there is an easy way to figure that out.

[JamesSingleton]

Hi @leerob,

Just circling back to this. I was hopeful that maybe deleting the "Active Branches" would have worked. Unfortunately, it looks like I keep climbing closer and closer to that hard limit. I would prefer not to have to manually go through and delete the probably 300+ preview URLs 😓

[JamesSingleton]

I am going to go ahead and close this issue out. Just an FYI @leerob and @amyegan, after talking with Malte I turned on deployment protection around May 9th. Since then the image optimizations coming from this particular project have dropped significantly. It would be nice to see WHICH deployment branches were getting outside traffic though so I could go through and delete them.