Benefit of sprites for WebSocket applications?

Question

In normal web applications, it is good practice to package multiple images in sprites such as to diminish the number of HTTP requests, and therefore minimize loading time...

My question is: does this benefit still exist in WebSocket based applications?

Since a WebSocket application does not technically make HTTP requests, will there be a performance increase when using sprites in this case too?

Note: I know that sprites have other advantages such as a better user experience when switching a button from idle/hover, but I'm here talking only about load time.

score 0 · Answer 1 · edited May 23 '17 at 12:10

0

Alright, so my question was motivated by a surprisingly low overhead when using individual frames vs. sprites on a Meteor application. Turns out, this is due not to WebSocket but to HTTP/2. Some resources which answer it:

Under what circumstances would loading images individually with HTTP/2 be slower than loading all images at once with a sprite a la HTTP/1.1?
Loading 1 1MB large image (spritesheet) vs loading 100 10KB images -
Optimizing File Cacheing and HTTP2

edited May 23 '17 at 12:10

Community

1
1

answered Mar 22 '17 at 14:13

ProgressiveMonkey

315
1
4
11

how are you measuring overhead? – mutdmour Mar 26 '17 at 08:39
We're measuring the entire load time of the page. It has a massive number of graphical assets, around 5000, but we saw only a 20% increase in load time when using single images vs. sprites of 16 images. – ProgressiveMonkey Mar 27 '17 at 11:15

Benefit of sprites for WebSocket applications?

1 Answers1