Resize Before You Compress: The Bigger Win
Compression makes each pixel cheaper. Resizing removes pixels nobody was going to see. If an image is 6000 pixels wide and displays at 800, resizing is worth several times more than any quality setting.
Find the real display size
A full-width image on a 1440px page occupies at most 1440 CSS pixels. Serving 6000 is shipping four times the width and roughly sixteen times the pixels. Open your page, inspect the image, and read its rendered width — that is the number that matters.
Double it for high-density screens
A phone with a 3× display needs three device pixels per CSS pixel. Serving 2× the display width is a good compromise: sharp on most screens, far smaller than the camera original. Serving 3× costs a lot of bytes for a difference almost nobody can see.
Resize first, then compress
Order matters. Resizing first means the encoder has fewer pixels to work on, so the same quality setting produces a smaller file with less visible damage. The compressor does this in one pass when you enable the resize limit.
Never upscale
Resizing up adds pixels that carry no new information: the file grows and the image does not get sharper. The tool never upscales — a small image asked for a 1920px limit stays at its original size.