Why Are My Images Flagged as Low Resolution?

Saar Twito9 min read
Saar Twito
Saar TwitoFounder & SEO Engineer

Hi, I'm Saar - a software engineer, SEO specialist, and lecturer who loves building tools and teaching tech.

View author profile →

What Does "Serves Images With Low Resolution" Mean?#

It means at least one image on the page has fewer pixels than the screen needs to draw it sharply. The browser stretches the file to fill the space the layout gives it, and on a high-density screen a stretched image looks soft or blurry. The check passes as "Serves images with appropriate resolution" and fails as "Serves images with low resolution".

It compares two sizes. The natural size is the image file's own width and height in pixels. The displayed size is the width and height the image takes up on the page, in CSS pixels. Between them sits the screen's device pixel ratio (DPR): how many physical pixels it uses for each CSS pixel. MDN Web Docs describes a ratio of 1 as "a classic 96 DPI display", expects 2 on HiDPI and Retina displays, and notes that modern phones often report more than 2 (MDN, devicePixelRatio). An image displayed 400 CSS pixels wide on a DPR-2 screen is drawn with 800 physical pixels, so a narrower file has to be enlarged.

Key Facts (TL;DR)

  • The rule: an image fails when its natural width or height is below 75% of its displayed size × the screen's pixel ratio.
  • Pixel ratio cap: the ratio is rounded down to 1, 1.5 or 2. A DPR-3 phone is treated as 2, so the check never asks for more than a 2× file.
  • Small images are stricter: an image displayed at 64 × 64 CSS pixels or smaller must reach the full 100%, not 75%.
  • Only some images are checked: visible ones in the first screen. SVGs, CSS background images, images cropped with object-fit, pixel-art images and images whose srcset uses 2x-style descriptors are skipped.
  • Not a speed problem: the check sits in the Best Practices category (User Experience group), not Performance, so it never changes a performance score.
  • The opposite of oversized images: a file far larger than its display size wastes bytes; this check is about files that are too small.

How Is the Required Size Calculated?#

The check works out a minimum width and height for each image and compares them with the file's natural size. Both dimensions have to reach the minimum.

  1. Round the pixel ratio. A ratio of 2 or more counts as 2; from 1.5 up to 2 it counts as 1.5; anything lower counts as 1. A DPR-1.25 laptop is therefore judged like a DPR-1 screen, and a DPR-3 phone like a DPR-2 one.
  2. Pick the tolerance. An image displayed larger than 64 × 64 CSS pixels may be up to a quarter smaller than ideal, so its factor is 0.75. A smaller image — an icon, an avatar, a logo mark — gets no tolerance: its factor is 1.
  3. Multiply and round up. Minimum = factor × rounded ratio × displayed size, rounded up to a whole pixel, for the width and the height separately.

For a hero image displayed at 400 × 225 CSS pixels on a DPR-3 phone, the ratio counts as 2, so the file needs at least 600 × 338 pixels to pass. The audit report in Chrome DevTools also shows an "Expected size" column — here 800 × 450, the rounded ratio × the displayed size with no tolerance — which is the size to aim for.

ExampleDisplayed (CSS px)Screen DPR → counted asNeeds at leastExpected sizeFileResult
Hero image on a phone400 × 2253 → 2600 × 338800 × 450640 × 360Passes
The same hero, smaller file400 × 2253 → 2600 × 338800 × 450480 × 270Fails
Wider hero on a laptop800 × 4501.25 → 1600 × 338800 × 450640 × 360Passes
Avatar on a phone48 × 483 → 296 × 9696 × 9672 × 72Fails

The avatar row is the one that surprises people. A 72 × 72 file would clear a 75% tolerance on a 2× screen, but at 48 × 48 CSS pixels the avatar counts as a small image, so it needs the full 96 × 96.

Which Images Does the Check Look At?#

Not every image on the page is measured. An image has to pass each of these gates before its size is compared; one that drops out at any step is not reported, however blurry it is.

From image on the page to pass or failEach step removes images from the check; only those that reach the last step can fail.
  1. Displayed larger than 1 CSS pixel each way, with a known natural sizetracking pixels and images with no pixel size are left out
  2. Not an SVG and not a CSS background imageonly images with a pixel size of their own are compared
  3. Drawn with the default object-fit: fillimages cropped or letterboxed with object-fit: cover or contain are skipped
  4. Not drawn with image-rendering: pixelated or crisp-edgesdeliberately blocky pixel art is left alone
  5. No srcset with density descriptors (1x, 2x …)the page already offers a high-resolution choice
  6. Visible in the first screen and no larger than itimages below the fold are not measured
  7. Natural size compared with the required sizefails if the width or the height is short

Source: the image resolution audit's open-source code (image-size-responsive), read 2026-11-02.

Why Does Image Resolution Matter?#

  • Blurry images look broken. Product photos, screenshots and diagrams lose the detail people came to see, and text inside an image — a chart label, a screenshot of code — becomes hard to read.
  • Phones are high-density screens. A file sized for a DPR-1 monitor is stretched on every phone that reports a ratio of 2 or more.
  • Brand marks suffer most. Logos and avatars are small, so the check gives them no tolerance, and a soft logo is noticed at once.
  • It is cheap to fix. The fix is usually one extra file and one attribute. With srcset, a screen that does not need the larger file can keep loading the small one.

How to Fix Low-Resolution Images#

1. Offer a 2× file for fixed-size images

For an image that is always shown at the same CSS size — a logo, an avatar, a badge — add a srcset with density descriptors. When srcset uses x descriptors, the browser also counts the src as the 1x candidate, so one extra entry is enough.

<img
  src="avatar-96.jpg"
  srcset="avatar-192.jpg 2x"
  width="96" height="96"
  alt="Portrait of the author">

A DPR-1 screen can load the 96-pixel file and a high-density screen the 192-pixel one. Images whose srcset uses density descriptors are skipped by the check, so after this change the image no longer appears in the report.

2. Give fluid images a large enough candidate

An image whose width follows the layout needs width descriptors and a sizes attribute. The browser divides each candidate's width by the slot size from sizes to get its effective density, and the HTML Standard leaves the final choice to the browser, which can weigh "the user's screen's pixel density, zoom level, and possibly other factors such as the user's network conditions" (HTML Standard, Images). What you control is the set: make sure the largest file is at least twice the widest slot the image fills.

<img
  src="hero-800.jpg"
  srcset="hero-400.jpg 400w, hero-800.jpg 800w, hero-1200.jpg 1200w"
  sizes="(max-width: 640px) 100vw, 600px"
  width="1200" height="675"
  alt="Team at the product launch">

Here the widest fixed slot is 600 CSS pixels, so the 1,200-pixel file covers a 2× screen. Without sizes, the browser assumes the image is the full viewport width (100vw) when it picks a candidate. The Properly size images guide walks through choosing the widths and writing sizes.

3. Export and upload at 2× the display size

Most low-resolution reports start in a design tool or a CMS. Export assets at twice the CSS size they are shown at, and check which size your CMS inserts: a theme that places a 300-pixel thumbnail into a 600-pixel column produces this failure on every post.

4. Go back to the original file, not an enlarged copy

Enlarging a small file in an image editor adds pixels but no detail, so the image passes the check and still looks soft. Re-export from the original photo or design file instead.

5. Use SVG for logos and icons

A vector logo is drawn sharply at any size and pixel ratio, and SVG images are not part of this check. For icons and simple marks it is the one fix that works on every screen, including ones denser than 2×.

6. Mark pixel art as pixelated

Some images are meant to look blocky: pixel art, retro game sprites, deliberately low-resolution graphics. image-rendering: pixelated scales them with a nearest-neighbour method so they keep that look (MDN, image-rendering), and the check leaves images drawn that way alone.

How to Find Low-Resolution Images on Your Site#

  • Greadme Page Audit — reports the check as "Images Too Low-Resolution for the Screen", listing each flagged image's URL, element and selector, with a copy-ready prompt for your AI assistant.
  • Chrome DevTools — select the image in the Elements panel and type $0.naturalWidth, $0.currentSrc and devicePixelRatio in the Console to see the file's width, which candidate the browser picked and the screen's ratio. Compare the width with the image's rendered width in the Computed tab.
  • Device emulation — the DevTools device toolbar lets you set the device pixel ratio (add its DPR menu from More options), so you can reload the page at 2 or 3 and watch which file each srcset loads.

Common Causes and Their Fixes#

Problem: The theme inserts a thumbnail size

What's happening: the CMS places its medium or thumbnail image into a column wider than that size, so every post image is stretched.

Fix: output the large size with a srcset of the generated sizes, or raise the registered size to twice the column width.

Problem: The largest srcset candidate is too small

What's happening: a srcset stops at 800w while the image fills a 600-pixel slot, so a 2× screen has nothing large enough to choose.

Fix: add a candidate at least twice the widest slot (1200w in this case).

Problem: The logo was exported at 1×

What's happening: a 160 × 40 PNG logo is displayed at 160 × 40 CSS pixels, which is sharp on a DPR-1 screen and soft on denser ones.

Fix: switch to the SVG version of the logo, or export a 320 × 80 file and offer it as 2x.

Problem: A blurry image is not reported

What's happening: it is a CSS background, it is cropped with object-fit: cover, or it is below the first screen — all of which the check skips.

Fix: check it by hand in DevTools with the steps above; the same 2× rule makes it sharp.

FAQ#

Does this check affect my performance score or Core Web Vitals?

No. It belongs to the Best Practices category, in its User Experience group, with a weight of 1. It has no part in the performance score, and it is not one of the Core Web Vitals, which measure loading, responsiveness and layout stability from real visits.

My phone has a pixel ratio of 3. Why does the check only ask for 2×?

The check rounds every ratio of 2 or more down to 2, so it never asks for a file more than twice the displayed size. Serving a 3× file is allowed and may look sharper on those phones, but it costs more bytes and the check does not require it.

Why does the expected size in the report differ from the size that passes?

The "Expected size" column is the rounded pixel ratio × the displayed size. The pass line lets an image larger than 64 × 64 CSS pixels fall 25% short of that, so a file between the two passes. Aim for the expected size; the tolerance absorbs small differences, it is not a target.

Is this the same as "Properly size images"?

No, it is the opposite problem. An oversized image — a 2,000-pixel file shown 400 pixels wide — wastes download bytes and slows the page. A low-resolution image is too small for its space and looks blurry. Both are fixed with the same toolkit: srcset, sizes and a sensible set of file widths. The Properly size images guide covers the oversized side.

Why was a blurry background image not flagged?

CSS background images are outside this check, as are SVGs, images cropped with object-fit and images below the first screen. They can still be blurry. In CSS, image-set() offers a background in several resolutions, the stylesheet counterpart of srcset.

Will a higher-resolution image make my page slower?

Not on screens that do not need it, if you use srcset: a DPR-1 screen can keep loading the small file. Compress the large file in a modern format such as WebP or AVIF so the 2× version costs as little as possible — see the modern image formats guide.

Conclusion#

"Serves images with low resolution" means a file has fewer pixels than its space on a high-density screen. The rule is simple once it is written down: rounded pixel ratio (at most 2) × displayed size, with a quarter of tolerance for anything bigger than 64 pixels square. Offer a 2x file for fixed-size images, a large enough candidate for fluid ones, and SVG for logos. Run Greadme Page Audit to see which images on your page fall short.