The issue is that the .NET assemblies that run Crystal don't load into memory until your application uses them. How much RAM is on the machine where your application is running? How much free space is available on the hard drive? The more of both that you have, the faster the report will load and process. (Crystal can be a memory hog.)
-Dell