Also mentioned by @MysticalApple. Unsure why this happens; is it a PWA image optimization attempt by safari?