WebEngine needs a new method such as setLoadImages(boolean) to enable/disable loading of images.

This way if the user needs to process many pages the total time spent is much improved because only the html/scripts were downloaded.

Notice that the full processing of javascript is still needed even if the loading of images were turned off. That is because full DOM event processing and general javascript processing needs to occur for DOM manipulations and their events to be processed correctly. That way I can have a headless browser behavior with full dom manipulation support (such as filling out of forms etc) and all the event processing / javascript processing that requires, without the unnecessary bandwidth / performance load for downloading images.

This feature is invaluable for headless browser behavior. And the best place for this decision to occur (whether or not to download the image resource) is inside the WebEngine itself, because the engine itself has full knowledge of whether what it's about to grab is an image or not, when putting together the web page.