imbahub
Menu +
US
Talk to us
IMBAHUB / Websites

Deliver an image that fits its space and still explains the right thing.

ImbaHub can implement responsive image delivery for selected components. We connect actual image use with size candidates, formats and loading choices, so a small image frame need not request the original while important details remain usable.

Three image roles with different needs
  1. Overview

    A card needs a recognisable subject at its actual size.

  2. Detail

    Drawings and product views may need readable enlargement.

  3. Introduction

    Main-image delivery is assessed against the initial viewport.

One file rule does not automatically suit every image role.

The mobile file is small but drawing labels cannot be read. Acceptable?

No. Preserve meaning and correct enlargement, then retest resource selection.

Define the image’s job before its files

Choose components such as a hero, product card and enlarged documentation image. Record subject, permission to use it and whether embedded text needs a language-specific version.

A fictional manufacturer shows product photographs and dimension drawings. A photograph can tolerate different scaling from a drawing with critical labels. Do not impose one crop and compression rule on both for convenience.

Build candidates around the real layout

Connect originals to named variants and HTML that supports browser selection. srcset and sizes must reflect actual file widths and layout. A different crop is an editorial decision rather than simply a smaller file.

For an Astro site, review existing image components and whether files come from the project, a CMS or another provider. Scope follows actual technology; no unverified Imba CMS capability is assumed.

UseDelivery decisionAcceptance case
HeroVisible subject and loading priorityIntended image in the initial view
Product cardCandidates based on card widthRequested resource suits rendered size
DrawingReadability and enlargementImportant labels remain understandable
Localized imageCorrect variant and text alternativeMobile and desktop use intended language
ReplacementTraceable usesNo stale variant remains

Verify the requested resource and its meaning

Test narrow mobile, desktop, relevant pixel density and cold loading. Inspect the file actually requested, reserved layout space and any enlargement destination. File existence alone does not establish correct content.

Set loading priority around the image’s role. An early main image should not routinely be treated like content far below. Fewer bytes are not acceptable if the subject or text becomes unusable.

Hand over an editorially usable pipeline

An initial project can cover one image component, selected originals and affected languages. Delivery includes code, variant rules, asset register and cases. Photography, new illustrations and licenses are scoped separately.

Pricing follows technical and asset review. Approved product subjects change only under an explicit image decision. A local comparison is not a guaranteed LCP result for every real visitor.

Sources and further reading

Questions, answered

Is this just compressing every image?

No. The work connects subject, layout, resource selection and updating. Compression must be balanced against readability.

Can existing originals remain?

Yes, where rights and quality are suitable. Originals and published variants need distinct roles and traceable uses.

IMBAHUB

Let’s plan your website

Bring a product card and a large image whose delivery should improve without losing information.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.