Pertaining to website loading period, is it better to possess 1 big photo or break the larger image upwards into several lesser ones
When you are talking about a large photo, I would certainly leave that entire.
If you broken up a 4k photo into four 256 byte images thinking that you cut page load time by way of a quarter. However that is counter productive, and in just about all cases the 4k graphic would load more quickly do to ask for overhead. If your picture is reasonable in dimensions, I think any particular one large file will load with more speed than several little ones.
How big is big When you are talking about one thing over 1MB you might split that upwards. But if it’s just a 200k header, We’ve loaded that of hospitality attire image with lots fast results. Hope that helps.
1 large. Every additional image with a page means one more HTTP request.
Cheers Brandontran and Filbert1 – Let me change the method I do things. I had considered that – one example is, three 25k pictures would load a lot quicker than one 100k graphic – but have find things recently of which support your view:
Whether it has the three 25k graphics or one 75k graphic, you still ought to load the similar amount.
In case its a photograph, save in a progressive format. This permits the photograph that will load in layers rather then l ine through line. Low high quality layer 1 then medium quality layer 2, then premium layer 3.
This might not be true, not to be able to sure on just how webservers handle photo requests, but i believe this is A FEW seperate requests.
the overhead may well be minimal though
Case in point: im downloading from an ftp. 75k graphic = 1 interconnection, 1 download
Only do this inside 3 connections, 25k img, 25k img, 25k graphic, those extra A COUPLE OF connections have extra overhead.
why exactly are you concerned with loading time Optimize ones images, drop the quality on ones that may offered to are dropped. Drop the type on others (example: thumbnails… instead of scaling, make any seperate thumbnail image)
That bandwidth overhead is actually minimal (usually) using multiple requests, nonetheless most browsers will only allow 2 simultaneous HTTP cable connections. That means it would sit there waiting considerably for content in order to load.
http: //developer. aol. com/performance/rules. html#num_http.