Browser Performance

BROWSER PERFORMANCE

Over the past 5 years the Chrome and Chromium-based browsers were top in HTML 5 recognition and Firefox was top in CSS 3 recognition. The latter might be considered best overall, since issues in parsing HTML may cause less issues in the display than those with CSS. Although, Firefox may be ahead in CSS 3 recognition, it seems to be falling further behind in HTML 5 and we are having more issues when using it, compared to Chrome, or Edge. From current testing, there are less differences in the performance of the browsers tested and how they behave on the various operating systems. The price often paid for the rapid progress in browser development was instability in some browsers, because the pre-release testing was sometimes inadequate, but in general this has improved too.

The first Microsoft Edge browser was different from IE and its emergence spelled the end of IE, when operating systems, in which it is supported, reached the end of their own support period; as was the case with IE 9 in Windows Vista and IE 10 in Windows 8. Firefox, which released Version 57 on 14 November, 2017, only started life in 2003; whereas IE had only reached version 11, with the first version in 1995. Google Chrome, which is based on the open source Chromium browser project, has moved even faster from its start in 2008 and on 13 February, 2018 released Version 62!  Microsoft Edge browser had incremental updates improving its performance as well as security updates on the second Tuesday each month together with other Microsoft software. In October 2017, Microsoft also introduced an Edge browser for Android and iOS phones.  These were Edge in name only and do not use the Edge engine. The Android version is based on the Blink engine used in Chromium and the iOS version is based on the WebKit engine as used by Safari. Their performances are similar to other Chromium and WebKit-based browsers. We do not run Apple platforms and Apple stopped support for the Safari Windows versions in 2012.  Testing of Safari ver. 5.1.7 found that it did not support the HTTPS protocol and we discontinued testing on our site.

Regarding other alternative browsers, it should be noted that Opera, at version 49 on 16 November, 2017, was the fifth most popular browser. It was first released in 1996 and it presently performs almost as well as Chrome in recognizing HTML5 and CSS3. When the Firefox version 57, named Quantum, was released it was s said to be faster and use less memory than Chrome. Firefox version 58 was released on 23 January, 2018.  Two other browsers, SRWare Iron version 62, released 6 November, 2017; and Vivaldi, now at version 1.14, released on 31 January, 2018, are also based on Chromium. Iron claims the advantage of not allowing the feedback as used by Google from Chrome and thus has better privacy. Vivaldi offers a theme colour that will follow the web site and a panel for working with open tabs.  Our experience with both browsers is that they perform very well, but support for automatic updating is lacking. The choice of a browser is no longer really a question of performance, but more of other specific feartures and security. In our latest page Browser Performance, we comment on some of the differences.

Even with the rapid development of browsers, when using HTML and CSS, there are still differing ways to write the code necessary to show the various styles, which evolve. While the latest versions of the more popular browsers may be able to recognise standardised coding, they sometimes still need their own specific extensions to recognise certain CSS coding such as the colour gradients used at the top and bottom of these pages. The older versions of browsers may also need different extensions added, if pages are to be backwards compatible. In the past, as many as 7 different strings of code were needed to accomplish this for one particular gradient style. This slowed down the loading of pages, but fortunately the need for these extensions has been greatly reduced. We now have another issue where the inclusion of unnecessary or deprecated extensions in pages and software coded 5 – 10 years ago, has become the problem that slows page loading. Styling for pages can be checked on a W3 CSS Validation page and, if the tests are passed, will be acknowledged with a logo and a message: Congratulations! No Error Found. This document validates as CSS level 3!

vcss-blue

To compare browsers in their capabilities to render HTML5 and CSS3, there are two web sites that will almost instantly give you a valuation at the following URLs:

HTML Iconhtml5test.co/ Results appear on opening screenCSS3 Iconcss3test.com/ Results appear on opening screen

In the case of the CSS 3 testing, the site now allows the selection of versions or time periods to be chosen for the testing, as well as testing for SVG recognition and other tests.


1. HTML5 is the fifth revision of the HTML standard. Its main aim has been to improve the language with support for the latest multimedia, while keeping it easily readable by humans and understood by computers and devices. HTML5 will subsume HTML 4.
2. CSS3 (Cascading Style Sheets Level 3) is one of a series of levels. Style sheet language is used for describing the look and formatting of a document written in a markup language such as HTML. CSS3 is divided into several separate modules, which have been in development since 1999. Not all implementations are considered stable and browsers vary in their capability to render them.


Back to top

Recent Posts