Forum Moderators: not2easy
Also, they have a link from each slice, so that's a few more bytes - which may negate the benefit.
As an aside, would a service like Akamai be able to cache only the logo (if someone wanted to go to that extent)?
I like the packet size angle.
- Ash
I was talking about the slices in the Advanced Search view, where I haven't seen the country name, so out goes that theory.
Anyway, to facilitate that in the Simple Search page, only the bottom of the g needs to be lopped off and the country name can still fit in nicely to its right.
If we see a decent explanation, it should be quite interesting.
Now it is one logo:
8558 bytes
Old logo
4277
2953
2702
1410
=11342 bytes
They always do stuff to their home page - I remember when they just used:
<style><!--
body {font-family: arial,sans-serif;}
//--></style>
I like that cause I like something simmple to put in my header to make all the type the same font
Actually, the logo that I noticed originally (in the Advanced Search) is still all cut up and feeling miserable:
Image, Alt tag, width, height, size in bytes:
res0.gif "Go to Google Home" 110 58 3,648 B
res1.gif (not set) 38 58 1,704 B
res2.gif (not set) 52 58 1,538 B
res3.gif (not set) 38 20 0,716 B
Total size = 7606 bytes.
Depending on how one crops the composite image off a search form, you can reduce it to 4669 B as a .gif or 2989 B as a .jpg with 60% quality.
The link from the image to the Simple Search is still a puzzle.
One other possible explanation would be a deterrence to image theft, though three slices would not be much of one... a few quick copy n' pastes and you have a fully functional 'Google'
Here is a slice n' dice for all of you to chew on:
Check out the image links on Adobe's site for Acrobat and the PDF online creator. At first glance, I had thought that they might be using a pixel for any solid color slices and just increasing the height/width of the image through code (for that MAXIMUM optimization). But upon snagging a few of the jpgs, I realized that it was not the case. Some of the colors even overlap where it could have been easily avoided... Not to mention ANY bytes saved were most definitely lost in the code gained (+4kb!). I reconstructed the image, switched it to a gif and found it was only 1.6kb in size (jpg was 2.2)... quite a ridiculous amount of trouble for such a small image to begin with, wouldn't you say?
Which leads to me suggest the theft deterrence possibility in both cases
maybe they are just promoting ImageReady...
maybe someone was just really bored...