#Qupzilla google photos series#

When QtWebServer is ready (replacing QtWebkit), Qupzilla will migrate to Blink.On the cover of this blog, Qupzilla consumes 63 MBs, while Firefox it still consumes 160 MBs.On the default page the consumption of Qupzilla drops to 16 MBs, while Firefox is located at 160 MBs. The consumption data were made with the google.es page.

Autoscroll support (by pressing the central button you can scroll the page with the cursor).Support for Mozilla Greasemonkey (allows modifying JavaScript scripts).Native notification integration (also with kde).It also allows you to specify a user agent for certain pages (I for example log into Gmail with the Chrome user agent).Īnd, optionally, the following functions can be enabled (which are disabled by default): This technology is known as Click to Flash. It blocks Flash applications and replaces them with a button, which we must press to load (reducing consumption).Native integration on the desktop (see images at the beginning of this post).Hover over tab previews (as in rekonq).Combine bookmarks, history, and RSS in the same window.It also shows your IP in parentheses, which can be useful if you're a whois freak. It shows the domain name, which can be useful to prevent Phising (for example, someone making a page called dsdelinux and using it to steal passwords).By blocking advertising, you reduce consumption. Integrated (but deactivatable) AdBlock.

#Qupzilla google photos series#

In addition, Qupzilla has a series of characteristics very useful, many of them innovative: This guarantees a lower CPU consumption and in turn allows large web applications to run faster.

Regarding CPU usage, Qupzilla uses V8, the same Javascript engine as Chrome, what benchmark after benchmark keep crushing the firefox.

They may vary on other websites and environments.Īs for Chrome, it does not enter this comparison because, with a initial consumption similar to Firefox, consume much more for each open tab (around 40MB).