Any discussion on load average is meaningless without looking at the system it is running on. Without that information, it's just a 'number'
You must also see if there's a particular event that may be unavoidable or whether it's a sustained load level. For example nightly backups. During this period, our single CPU machines can hit a load of 5 easily. But it's for a short period, and you can schedule it for off-peak times (example after 4AM)
For a Celeron 2.4, basically you should keep the sustained load below 1 for it to run without noticable delays. The calculation of load figures already take in consideration (somewhat) the type of processor you have. It measure how many processes are in the CPU queue to be processed. So if you have a slower processor, the queue will be backed up more compared to a faster one. i.e. if you are running the same operation, since a faster dual machine can process it faster, their queue will be a lot shorter. So the load number will already be lower even if both machines are processing the same operation. Obviously many factors can affect it example memory or how fast your disk can read. More memory means data can be read faster (and thus sent through the queue faster), or if a process is reliant on a read from the disk drive, even if the CPU can run faster, the queue can still start accumulating. (That's why during I/O intensive task, your load will increase too)
When we used to run single CPU machines as our primary machines a year or so ago, we try to make sure we are always below 1 most times, and we started to scout for a machine once it sustain at 0.5.
It should also be noted that noticable difference is also different from dependent on the speed of the cpu. This is natural because a single slower processor for example isn't going to take the same time as a faster dual processor machine in processing 1 process assuming it's the same operation.
Hope this explains.