Oliver Vogel

I suggest to create a XDebug profile, to discover what is causing this delay.

I'm again suggesting to create a XDebug profile, to discover what exactly is causing this delay.

Please be more specific.

You can do this by storing your actual code into a [Filter class](http://image.intervention.io/use/filters) and run something like: ``` php $img = Image::cache(function($image) { $image->make('foo.jpg')->filter(new FooFilter); }); ```

What are the errors?

What is the actual output on the requested image route? (Broken image or square on a black screen could be anything.)

No, I mean what do you get if you request only the image? `http://domain.ext/img/original/image.jpg`

Why do you get base64 encoded data from the route? If you setup [URL based image manipulation](http://image.intervention.io/use/url) you should just get regular image data. PS: You can delete.

I think you setup imagecache like it is described in the docs. I would just like to know what image data you get from the route, when you got a...

The whitespace is the problem. But neither Intervention Image or Intervention Imagecache produces this whitespace. I think this may be a issue with Laravel's or Symfony's Cache/HTTP modules or the...