Varchar(255) looks like a dummy size, is the data from Access or Oracle? I've seen load file from Oracle with definition like this, load performance was horrible and the target table was much larger than in Oracle, because most columns were NULL.
Changing to an appropriate size and datatype (there might be some columns defined as VARCHAR(255), which are actually CHAR(.) and applying COMPRESS will probably resuklt in better performance.
If the "Number of recs/msg:" in your FastLoad output is close to 1, this will be a BTEQ like speed.