Why image size decides page speed

Images are usually the heaviest part of a web page. A single unresized phone photo can weigh more than all the page's text, styles and scripts combined. Visitors on mobile data wait for every byte, and search engines measure how quickly the main content appears.

The browser will happily shrink a 4000-pixel photo to fit a 800-pixel column, but the visitor still downloads all 4000 pixels. Resizing before uploading removes that waste.

Find the width the image is actually shown at

Measure the space in your layout:

  • Content images inside an article column are often 650 to 900 CSS pixels wide on desktop.
  • Full-width hero images may span 1200 to 1600 CSS pixels or more.
  • Thumbnails and cards are often 300 to 400 CSS pixels wide.
  • Logos are usually small, and often better as SVG. See SVG versus PNG.

To measure, right-click the image area in your browser and choose Inspect; the displayed width appears next to the element. Or check the theme's documentation for its content width.

Account for high-density screens

Phones and many laptops have screens with two or three device pixels per CSS pixel. An image displayed 800 CSS pixels wide looks sharpest on those screens when it has about 1600 real pixels. A practical rule:

Resize to about twice the displayed width, but rarely beyond 2000 to 2400 pixels.

PlacementDisplayed widthGood file width
Article image800 px1600 px
Hero banner1400 px2000 to 2400 px
Card thumbnail360 px720 px
Avatar96 px192 to 256 px

If your platform supports responsive images (the srcset attribute, which many content management systems generate automatically), upload one good large version and let the system create smaller ones.

Resize with Convertios

The Image Resizer runs in your browser, so images are not uploaded:

  1. Choose an image.
  2. Enter a width in pixels with Keep aspect ratio turned on, or use Scale (%).
  3. Optionally crop by dragging a box on the preview, or rotate the image.
  4. Pick an output format: same as original, JPG, PNG (keeps transparency) or WebP (keeps transparency).
  5. Download and check the result.

Do not enlarge small images to fill a larger space. Upscaling makes them soft; choose a different layout or a better source image instead.

Then compress

Resizing removes surplus pixels; compression removes surplus detail. For photos, export JPG or WebP and use the image compressor with a target size. For many content images, 100 to 300 KB is a reasonable target after resizing. Our guide to reducing image size without losing visible quality explains how to judge the result.

WebP usually gives smaller files than JPG for the same visual quality and is supported by modern browsers. The Image Converter can create WebP versions.

Other habits that keep pages fast

  • Set width and height on images in your HTML or page builder, so the layout does not jump while images load.
  • Lazy-load images below the fold so they download only when visitors scroll near them. Most platforms offer this.
  • Use descriptive file names and alt text, for example blue-ceramic-mug.jpg and alt text that describes the image for people who cannot see it.
  • Avoid text inside images where possible; real text is sharper, translatable and accessible.

Quick checklist

  • Measure displayed width; resize to about 2×.
  • Keep the aspect ratio locked unless you intend to crop.
  • JPG or WebP for photos, PNG or SVG for graphics.
  • Compress after resizing and check at real size.
  • Social platforms have their own sizes; see social media image sizes.