Sprite generation
We combine icons and small graphics into sprites (a CSS sprite or SVG sprite), so instead of dozens of requests for tiny files there is one. To offload loading, especially for icon sets. Honestly upfront: it is a neat technique, but with HTTP/2 the sprite win has decreased (small files load in parallel anyway), so we do it where it is genuinely useful (e.g. an SVG sprite for icons), not 'for show'.
Sprite generation — overview
Sprite generation is a small project: we combine small images/icons into a sprite (PNG/CSS sprite for raster or, often preferably, an SVG sprite for icons) and set up usage in the markup. Honestly about context, this is key: sprites were invented to reduce the number of HTTP requests; but with HTTP/2/3 many small files are served in parallel over one connection, so the classic sprite win has DECREASED — on a modern protocol it is not the 'silver bullet' it once was. So we apply sprites selectively: an SVG sprite for icon sets is genuinely convenient and useful (management, styling, cache), while gluing everything into a raster sprite on HTTP/2 often makes no sense; we honestly say whether you need it. Honestly about the effect: the win is modest and targeted, measurable by request count; we do NOT guarantee sales growth by itself. Honestly about sprite downsides: one big sprite is invalidated entirely on an edit (like a big bundle) and loads what is not used on the page — we account for that. Honestly about access: access to code/assets is needed. An important boundary: these are sprites, not image optimization in general (707 — separate), not asset bundling (725) and not a CDN. If you have a modern protocol and few icons, a sprite may not be needed. Picture this: instead of 30 requests for icons — one neat SVG sprite where appropriate. The base price starts from 9,000 ₽ per project; it depends on the number of images.
Problems we solve
- Dozens of requests for small icons/images.
- Icons are scattered, inconvenient to manage and cache.
- There is no SVG sprite for an icon set.
- Extra requests slow loading (on old protocols).
What's included in the Sprite generation service
- An audit of small graphics and icons
- Building an SVG sprite for icons (preferably)
- A CSS sprite for raster where appropriate
- Setting up usage in the markup
- An assessment: is a sprite needed with your protocol
- A 'before/after' request-count report
- Checking display correctness
- Handover and review with you
What you get
- Fewer requests for small graphics
- Convenient icon management and cache (SVG sprite)
- A targeted win where it is real
- An honest applicability assessment (sales growth — not guaranteed)
How the work goes: steps
- We audit icons and the protocol; decide whether a sprite is needed and which
- We build an SVG/CSS sprite and set up usage
- We check display, measure requests, review with you
Why PDV Expert
- Fixed price and timeline — no surprises on the invoice.
- Report and recommendations in plain language — clear without a technical background.
- In touch at every step and answering questions about the result.
FAQ
Will sprites greatly speed up the site?
Modestly and selectively. Sprites reduce the number of requests, but with HTTP/2/3 small files load in parallel anyway — the classic win has decreased. An SVG sprite for icons is useful; gluing everything on HTTP/2 is often unnecessary. We honestly assess your situation.
Will it raise sales?
Not directly guaranteed. It is a small technical win on requests, helps loading, but sales depend on many factors.
Do sprites have downsides?
Yes: a big sprite is invalidated entirely on an edit and may load the unused on a page (like a big bundle). So we apply them selectively and do not overuse them, especially on modern protocols.
About the provider
The «Sprite generation» service is provided by PDV Expert — a team specialising in «Site quality». We work under contract and deliver a written report with recommendations.