Hi,

That would depends on your machine and it is common that it loads slower on the first run, but it should load faster if you are not debugging it. In any case, it should not have anything to do with the trial version. The trial version does not have any feature restrictions or performance throttling.

Thanks!

Hi,

That doesn't make much sense to us. Both EO.WebBrowser nad Awesomium are based on Chrome so once the Url is handed off to the Chrome side, it should pretty much the same. The main difference between our product and other product is our product is much easier to use. For example, we pack everything inside the same DLL so you don't have to deal with multiple files, but that shouldn't have such a great impact on performance.

There are a few more things that are different in our product:

1. We deliberately route a lot of notification through the UI thread so that you can handle those events easily without worry about synchronization issues. So if your UI thread is too busy, then that can have a negative impact on the performance;
2. For security reasons, the browser engine creates "security walls" around pages between different domains. So if you use the same WebView to load Urls from different domains, then you will be tearing down and rebuilding that security wall every time. To verify if this is the problem, try to load several Urls from the same domain and see if you see a big difference on the speed;
3. Our waiting mechanism is much more reliable so when functions like LoadUrlAndWait returns, it really means the page has completly loaded. For example, if you have a JavaScript that is triggered during load (for example, an alert call directly in the page), that code will be run before LoadUrlAnWait returns. If user waits for 10 seconds before closing that alert box, then LoadUrlAndWait will be delayed for 10 seconds. I am not sure if that's what you use to measure the load time;
4. Our engine is based on the latest Chrome code base, which I believe is much newer than what Awesomium uses;

In fact because the engine is based on Chrome, during our test the load time is pretty much the same as Chrome browser. You can try to start our TabbedBrowser sample and try to load some popular sites with the sample app and with Chrome browser, you will see both are almost always instant. Taking 8 seconds to load a page is very rare. So you may want to use the sample app to load your page and see if you see any significant difference "visually", if not much difference visually, then maybe the difference is only when we consider a load has completed.

Thanks

I agree with Scott here.

The EO.WebBrowser does seem slower. I'm already running on high-speced Macbook and good internet connection. Comparing to running the Google Chrome vs WinForm using WebView class (a very simple project at that), i can see the performance difference. Not sure if this is a fair comparison.

Regards,
Philip

Following your advise, there is indeed an improvement but definitely not on par with Google Chrome during start up. But loading from page to page, it's comparable to Chrome.

Is there a way to change the background color while loading the initial page?