Web Browsers Report

Embed Size (px)

DESCRIPTION

Web

Citation preview

1Web BrowsersSubmitted byAmogh Kulkarni (05CO05)Jaison Salu John (05CO29)Yohan John Thampi (05CO67)Shravan Udaykumar (05CO59)Gaurav Prasad(08IS03F)Vrinda Halarnkar (08IS04F)DEPARTMENT OF COMPUTER ENGINEER INGNATIONAL INSTITUTE OF TECHNOLOGY KARNATAKA SURATHKAL 575 025March 20091 2ABSTRACTWeb browser is the most commonly used client application and speed and efficiency of our online work dependson browser to a great extent. As the market is flooding with new browsers there is a lot of confusion ineveryones mind as to which is the best browser.Our project aims to answer this question. We have done acomparative study of the four most popular web browsers namely Mozilla Firefox, Internet Explorer, GoogleChrome, Opera. In the first phase of our project v arious comparison parameters are selected which can bebroadly cat egorized into -General Features, Security features and browser extensibility features. Using theselected benchmarking tools each browser is tested. We have also use our own test scripts for some parameters.Depending on the performance of the browser points are assigned to each browser .Public opinion is consideredfor usability issue and finally we have come to a conclusion t hat opera and firefox are leading the browser war.firefox has finished first scoring 49.84 and opera has scored the next highest 48.90Our other contributions include a K-chromium browser ,addon for firefox and scripts showing the major browserattacks.The report gives details of work done by our team from Jan 62008 till March 292008.ththI. INTRODUCTIONThe World Wide Web has come a long way in its short existence. Without it, many people wouldnt know what todo with their day. And others literally couldnt survive without it. To browse the internet we use browser. Abrowser provides a user interface for displaying and selecting items from a list of data or from hierarchicallyorganized lists of data such as directory paths. We can tell that browser is the most commonly used client sideapplication. Earlier the choice of the browser was limited but this is no longer the situation now. Numbers ofoptions are available making the choice of web browser difficult and confusing. Mainstream browsers are gettingtough competition from the upcoming alternatives each one having its own unique features. Hence making aright choice is a daunting task.The main reason that motivates us to work on this project is that nowadays the users just use any browser theyget without knowing its positives and negatives. Our project aims clear the confusion in users mind bysystematically testing the browsers and deciding t he best choice for different categories of users.First we discuss about the importance of a browser and its general architecture. In section III we elaborate ourevaluation strategy. In section IV, V , VI VII we list and justify our selection of browsers, test environment,parameters and benchmarks . Section VIII gives the details of the tools/scripts developed by us and the testresults. Section IX gives discusses the security issues of the browser . Section X we list out the points of eachbrowser .II. WHY WEB BROWSERS ARE SO IMPORTANT?Today most of what we use the web for isnt just web pages, they are applications. Users upload downloadvideos, chat, play online games, and use many other web services. Web browser is becoming more and moreimportant as an application used to conduct billions of dollars of Internet -enabled commerce each year.It has evolved significantly over the past fifteen years. Web browsers run on diverse types of hardware, from cellphones and tablet PCs to desktop computers. Hence a proper design becomes very important. Referencearchitecture for web browsers can help implementers to understand trade-o s when designing new systems, andcan assist maintainers in understanding legacy code. A web browser is client side application program thatcontacts remote servers and retrieves documents from it and displays them on screen, either within t he browserwindow itself or by passing the document to an external helper application. It allows particular resources to be2 3requested explicitly by URI, or implicitly by following embedded hyperlinks. Many other features are provided bybrowser which increases the ease of use. For example, most browsers keep track of recently visited web pagesand provide a mechanism for book-marking pages of interest. They may also store commonly entered formvalues as well as usernames and passwords.Finally, browsers often provide accessibility features to accommodate users with disabilities such as blindnessand low vision, hearing loss, and motor impairmentsBrowser Jargon you will come across in this report :Plug-in or Add-on : It consists of a computer prog ram that interacts with a host application in our case a webbrowser to provide a certain specific function on demand .Extension :is a program desig ned to to be incorporated into web browser to extend the functionality of thelater . On its own an extension is non-functionalBHO : Browser Help Object, BHO is a help object added to your Internet browser. For example theGoogleToolbaris considered a Browser Help Object; t his add-on enables users to perform Google searches through thetoolbar and contains additional features that help improve a user's experience.III. Evaluation Method: Why are we different?We started by performing a literature survey of the latest research papers, articles and whitepapers onbrowsers. Our study included the browser architecture study which is very important to evaluate the browsersresponse to scripts, security of the browser, memory and CPU usage by the browsers etc. Then we used theoutput of the literature survey to choose the parameters. In broader sense the parameters were classified intogeneral features, security features and t he add support . To evaluate each parameter following methods wereadopted.1)Test scripts were designed and used wherever possible (For ex. Speed Test2)Public opinion was asked for assigning values to features like usability3)Scripts were designed for attacking the browser4)Standard Benchmarks were usedIV .BROWSER SELECTIONAs our task was to compare the browsers, we need to decide which browser is to be selected. For that, we wentthroug h the usage statistics and found the following results given by some of the websites.Market Share of browsers:YEAR IE Fire fox Chrome Safari Opera Others200939.9%45.5%3.9%3.0%2.3%5.4%3 4200840.2%6.7%44.4%3.6%2.7%2.4%A.Mozilla FirefoxFirefox is an open-source project that is managed by the Mozilla Foundation. Each component is divided into sub-modules. Each of these modules is owned by a specific individual that is in charge of managing the developmentof that that module. It descended from Mozilla Corporation suite and is manag ed by Mozilla Corporation.Firefox includes tabbed browsing, a spell checker, incremental find, live bookmarking, a download manager, andan integrated search system that uses the user's desired search engine .Functions can be added through add-onscreated by third-party developers, which include the NoScript JavaScript disabling utility, Tab Mix Pluscustomizer, FoxyTunes media player control toolbar, Adblock Plus ad blocking utility, StumbleUpon (websitediscovery), Foxmarks Bookmark Synchronizer (bookmark synchronizer), WOT: Web of Trust security site advisor,download enhancer, and Web Developer toolbar. With a market share of 45.5% in 2009 it is the most popularbrowser.A.Internet ExplorerWindows Internet Explorer (formerly Microsoft Internet Ex plorer; abbreviated MSIE), commonly abbreviated toIE, is a series of graphical web browser developed by Microsoft and included as part of the Microsoft Windowsline of operating system starting in 1995. It has been the most widely used web browser since 1999, attaining apeak of about 95%usage during 2002 and 2003 with IE 5 and IE6 and that percentage share has declined since inthe face of renewed competition from other web browser developers.Internet Explorer uses DOCTYPE sniffing to choose between "quirks mode" (renders similarly to older versions ofMSIE) and standard mode (renders closer to W3C's specifications) for HTML and CSS rendering on screen (InternetExplorer always uses standards mode for printing). It also provides its own dialect of ECMA Script calledJscript.Internet Explorer has been subjected to criticism over its limited support for open web standards.B.Google ChromeChrome the latest browser released in 2008 already had a market share of 3.9% in Jan 2009. Chromium is theopen source project behind Google chrome.Salient Features include:1. Task Manager for Websites2. Visual Browser History3. Super Clean Contextual Menus4. Search option from the Address Bar5. Check Memory Usage by Different Browsers6. Reopen Website tabs that you closed by mistake7. Launch Websites from the Start Menu / Quick Launch Bar8. Developers claim faster speed (Sunspider and v8 benchmarks), better stability and performance and highsecurity..Architecture of chrome provides insight into its security featuresChromium has two modules in separate protection domain: browser kernel and rendering engine. Thisarchitecture helps mitigate high severity attack without compromising the compatibility.4 5C.OperaOpera has market share of 2.3%. But the features of this browser get it a place in our comparison chart. Claimedto be a fast and secured browser it, has the following new features in its latest version:Content blockingBitTorrent supportWidgetsSearch engine editorSite preferencesNew installer. One package30 languag esIntegrated source vieweropera:config for advanced settings configurationTab use: Thumbnails when you hover the cursor over a tabWidgets in Opera are more like small standalone applications that can interact with the internet and liveoutside the browser, rather than interface elements that can change the basic behavior of the browser,as Firefox's extensions are.Innovative Features in OperaOpera was the first browser with tabs, RSS support, and built-in BitTorrent client and tab thumbnails. It allowsfor duplication of tabs, Goto URL feature for web address that is not hyperlinked, periodic reloading, fitting towindow size (ERA), rewinding, crash recovery, page zoom, instant back, tab closing.Along with this it does the best on the Acid2 web standards test.Thoug h the safari browser is been used more as per the statistics given above we have taken chrome and operabecause chrome is the latest browser by Google which is popular and wanted to know the details of the newbrowser.V. TEST ENVIRON MENTBrowser VersionMozilla Firefox 3.0.7Internet Explorer 7.0.6001Google Chrome 1.0.154Opera 9.63Operating System RAM HDD Processor SpeedWindows XP Home512 MB DDR2, L2 cache 60 GBIntel Centrino 1.77Ghz,edition100% CPU Usage is made available for each test. This is ensured by reboot after every test .5 6VI. PARAMETER SELECTION AND WEIGHTAGESL NO. ParameterWeightage1. Web technologies Support52. Cross-platform Support73. Browser Features54. Accessibility Features55. Mobile Web technology support76. Plug in and Web Feed Support57. Protocol Support58 Security89. Add-ons810. Speed1011. Benchmark Tool Testing10Justification for the weightage for parameters:Every parameter was given a base of 5 points each.Added points were given t o parameters depending on the relevance and importance at the present. Like mobiletechnologies support was given ex tra 2 points because mobile tech is the upcoming technologies. Security, ofcourse is really important parameters and hence the 8 points. Speed, is the ultimate decider for the bestbrowsers and therefore we allot 10 points to it .Market Share table given in III. Browser SelectionVII. BENCHMARKS SELECTEDA. SunSpider JavaScript BenchmarkA benchmark suite that aims to measure JavaScript performance only not the DOM or Other browser APIs. Ittests on tasks that are relevant to the current and near future use of JavaScript in the real world, such as screendrawing, encryption and text manipulation. The suite further attempts to be balanced and statistically sound. Itwas released by Apple's Web Kit team in December 2007. It is designed to compare different versions of the samebrowser, and different browsers to each ot her.SL NO. Firefox Opera Chrome IE3D 641.4 815.8 181.02124.8ACCESS 808.4 1071.6117.62800.0BITOPS 531.6 840.2 90.22359.2CONTROLFLOW 64.8 81.2 4.0774.8CRYPTO 330.8 375.2 89.81606.6DATE 438.0 496.8 460.21452.6MATH 591.0 678.8 192.21918.66 7REGEXP 296.0 565.8 508.8425.2STRING 1185.4 1850.2 813.830937.8TOTAL 4887.4 6775.6 2457.644399.6Points 9 8 100*All times are in msB. ACID3Acid3 is a test page from the Web Standards Project that checks how well a web browser follows certain webstandards, especially relating to the Document Object Model and JavaScript.When successful, the Acid3 testdisplays a gradually increasing percentage counter with colored rectangles in the backg round. The percentagedisplayed is based on the number of sub-tests passed. It is not representing an actual percentage of conformanceas the test does not keep track of how many of the tests were actually started (100 is assumed). In addition tothese the browser also has to render the page exactly like the reference page is rendered in the same browser.Like the text of the Acid2 test, the text of the reference rendering is not a bitmap, in order to allow for certaindifferences in font rendering.Passing ConditionA passing score is only considered valid if the browser's default settings were used.The following browser settings and user actions invalidate the test :Zooming in or outDisabling imagesApplying custom fonts, colors, styles, etc.Also User JavaScript or Greasemonkey scripts may invalidate the test.SL NO. Browsers ACID3 test Points1. FIREFOX 71 7.12. IE FAILS 03. OPERA 85 8.54. CHROME 79 (LINKTEST FAILS) 7.9VIII .ImplementationK ChromeChromium source code was downloaded, built and tweaked to make changes in the interface.These are the basic steps to modify,build and run the chromium source code. The detailed steps aregiven in the other report.1. Install Microsoft Visual Studio 2005 Pro (8.0) or later. Visual Studio Express won't work. VisualStudio 2005/2008 Pro Trial will work.7 82. Install the Windows SDK 6.1. Integrate the SDK with Visual Studio: Start > All Programs >Microsoft Windows SDK v6.1 > Visual Studio Registration > Windows SDK Configuration Tool.3. Download the Chromium Source Code. The source code will be in .rXXXXX.tgz.format4. Using 7-Zip, we have to extract(unzip) twice.5. We will finally get the actual source code and this requires around 8GB of your hard disk.6. To change the display of the web browser, the new_tab file which is html format wasmodified. This file was found in the resources folder. To identify this file took up much of timeas it was kept in multiple folders.7. After the new_tab.htm file was modified, we had to build the chromium source code.8. Open the chrome/chrome.sln solution file in Visual St udio and build the solution.9. Right-click chrome_exe and select Set as Startup Project. Right-click chrome_exe in thesolution explorer and select Build. It took 1hr and 10mins to build for the first time.10. This will make Chromium build and to run the code press F5.The details of the build are given in the appendix.Extension and Addon for Mozilla FirefoxFollowing are the Steps for building an Extension/Add-ona.Customize the InterfaceEdit the XUL file to change the appearance of your extension.b.Take StockUpdate the Contents.rdf files by replacing all the occurrences of orginal extension name with thename of your extension. Make sure that the Contents.rdf file in the content folder correctlypoints to the filename of your XUL file. When you're done, rename the ZIP archive (the onecontaining the skin and content folders) with a .jar extension.c.Update the Install scriptThere are six lines to update in the Install.rdf file: the name of your extension, the versionnumber, the creator, a brief description, the name of the .jar file, and a unique ID thatdifferentiates your extension from all others.d.Put it Back TogetherWith all the files updated, rename the main ZIP file with an .xpi extension again. Make sure thatthe directory structure exactly matches the example XPI. To install your extension, drag anddrop your XPI file onto an open Firefox window, and then restart Firefoxe.Check your workTest your extension on a real Web site. If you get an error, or if something doesn't work, retrace.your steps and see if you missed anythingFollowing is the directory Struct ure:Xpi file>/install.js/install.rdf>Chrome>jar file>content/name of extension>content/contents.rdf/nameofextension.xul>locale8 9>folders for different languages>skin>images used for the toolbar interfaceBrowser Helper ObjectA Browser Helper Object (BHO) is a DLL module desig ned as a plugin for Microsoft's Internet Explorerweb browser to provide added functionality. A HelloWorld BHO for internet explorer wasimplemented.Steps for building an IE Extension using Microsoft Visual Studi o 20051) Create a ATL project with server type is "Dynamic-link library (DLL)"The following files are created as part of this project.HelloWorldBHO.h this header file contains the class definition for the BHO.HelloWorldBHO.cpp this source file is the main file for the project and cont ains the COMobject.HelloWorld.cpp this source file implements the exports that ex pose the COM objectthroug h the DLL.HelloWorld.idl this source file can be used to define custom COM interfaces. For thisarticle, we will not change this file.HelloWorld.rgs this resource file contains the registry keys that are writt en and removedwhen the DLL is registered and unregistered.2) In HelloWorldBHO.h,First, include shlguid.h. This file defines interface identifiers for IWebBrowser2 and the eventsthat are used later in the project.Next, in a public section of the CHelloWorldBHO class, declare SetSite.Finally, in a private section of the class declaration, declare a member variable to store thebrowser site.3) In HelloWorldBHO.cpp,Add the code for SetSite. During initialization, the browser passes a reference to its top-level IWebBrowser2 interface, which we cache. During uninitialization, the browser passesNULL. To avoid memory leaks and circular reference counts, it's important to release all pointersand resources at that time. Finally, we call the base class implementation so that it can fulfill therest of the interface contract.4) In HelloWorld.cpp,Since this BHO does not require thread-level tracking, we can callDisableThreadLibraryCalls during the DLL_PROC ESS_ATTACH notification to avoid the overheadof new thread notifications.Therefore code the DllMain function in HelloWorld.cpp5) Register the BHOAll t hat remains is to add the CLSID of the BHO to the registry. This entry marks the DLLas a browser helper object and causes Internet Explorer to load the BHO at start-up. Visualhen it builds the project.Studio can register the CLSID w9 10NITK Online Music Toolbar originally Online Music Player / NITK Toolbaroriginally Wizz RSS News ReaderTools required to develop this is an XUL editor like RJ Keller's MozCreato.For the First tweak we downloaded Wizz RSS News Reader addon fromhttps://addons.mozilla.org/en-US/firefox/addon/4617. Figured out how to change details in theAdd-ons Sections of Firefox - by changing install.rdf and how to change the details on the toolbar- by changing content/omusic.jar contents.rdf and the tweaking was done.For the second one we reffered to https://addons.mozilla.org/firefox/addon/424 and figuredout how to change t he Details on the toolbar - by changing content/wizzrss.jar - contents.rdf.Then t he jar file needs to be directly changed.Speed Test of BrowsersWe carried out the speed test of the browsers based on three i) CSS rendering ii) GraphicsRendering iii) Cryptographic code execution time.CSS rendering results:SL NO. BROWSER 1 2 3 AVG Points1 Firefox 78 79 78 78.33 12 IE 31 31 31 31 73 Chrome 39 27 29 31.66 64 Opera 16 16 16 16 8Graphics rendering resultsBrowser 1 (in s) 2 (in s) 3 (in s) Average (in s) PointsFirefox 7.197 7.201 7.201 7.1996 6Opera 11.388 11.388 11.232 11.336 4Chrome 2.876 2.877 2.877 2.8766 9IE 11.215 11.219 11.212 11.2153 4RSA javascript for encryption and decryption was tried in all the four browsers. Following results wereobtained:Key: 10001 Text: web browsers teamBrowser Encryption Decryption Total Points1 2 3 Avg 1 2 3 AvgFirefox 0.051 0.048 0.044 0.047 0.066 0.056 0.059 0.060 0.107s 7IE 0.187 0.109 0.094 0.13 0.187 0.171 0.204 0.562 0.692s 110 11Chrome 0.013 0.005 0.006 0.008 0.013 0.012 0.011 0.036 0.044s 9Opera 0.032 0.016 0.015 0.021 0.062 0.047 0.062 0.057 0.078s 8Prime Factorization Test was carried out to check the time taken by each browser to find prime factors of anumber. Following were the results:Browser 9 99 999 9999 9999999999 999999Total Points99Firefox 0.011 0.012 0.016 0.056 0.883 3.381 39.014 43.373 5IE 0 0 0.015 0.125 0.797 9.281 67.266 77.484 2Chrome 0.001 0 0.004 0.043 0.387 3.355 32.057 35.847 6Opera 0 0 0.016 0.047 0.547 2.641 24.953 28.204 7Cold StartThis is the time it takes to do a cold load. Once logged out and once all background processes have beencompleted, browser is run as the first program. Default settings for the browser, are used The browsers are allset to show a single page on startup, and this page is a locally stored basic HTML page.Browser Time 1(s) Time 2(s) Time 3(s) Average(s) PointsGoogle Chrome 1.6 1.6 1.6 1.6 10Internet Explorer 3.9 3.7 3.2 3.8 7Mozilla Firefox 8.0 7.7 7.7 7.8 2Opera 3.8 3.6 3.7 3.7 7Warm StartAfter completing a cold start, browser is closed ,and time taken to start again is measured . This is done twomore times and average is taken .Browser Time 1(s) Time 2(s) Time 3(s) Average(s) PointsGoogle Chrome 0.4 0.5 0.6 0.5 7Internet Explorer 0.2 0.7 0.9 0.6 6Mozilla Firefox 0.6 0.7 0.8 0.7 5Opera 0.7 0.8 0.9 0.8 4IX. BROWSER SECURITY ISSUESWe dealt with the following issues:I. A manual for browser security settings (For IE and Firefox).Internet users are always worried about the overall security of their assets on the net .We have created amanual to adjust the browser security settings and so that users can browse in more secured environment .This is added in the Appendix D.II. Evaluating the browsers based on securit y settingsThe main objective of the manual was to evaluate the browsers based on the security settings. This mainlyincluded the ease with which the users could control the security settings of the browsers and also thesecurity features provided by the corresponding browsers. The major security issues identified by us werejavascript/vbscript vulnerabilities, Active-x control vulnerabilities, Plug-ins, Cookies management, pop-up11 12blockers, certificate management, encryption, password management. The browsers were evaluated on theall these issues. For ex ample: a secure browser should have the option to disable javascript/active-Xoptions. This is mainly for the convenience for the user. If the user feels insecure surfing a particularwebsite, he/she can disable javascript so that the v ulnerable scripts wont execute at all in the browser.Similarly the browser should have efficient pop-up blockers and clever management and certificatemanagement options. The browser should be able to differentiate between a secure pug-in and a spyware ora malicious plug-in that attaches itself to the browser by deceit or without the permission of the user. Thebrowser should use the latest encryption standards. The browsers were evaluated on mainly the abovesecurity issues.III .Demonstration of security attacks on browsersScripts for demonstration of Cookie stealing and CSRF attacks and click-jacking vulnerability were prepared.Security Analysis of BrowsersThe browsers were finally evaluated on Security settings, architecture of the browser and click-jackingvulnerability that we had tested on all the four browsers.The evaluation of the browser based on the sec urity settings is explained in the above section. Architectureplays a major role in the security of a browser. If t he architecture is weak, its easy for a malicious code topenetrate into the code base of the browser. A browser with a good architecture wont let the maliciouscode or plug-in to compromise the code base of the browser. With upcoming technologies being releasedevery day, its a challenge for the browsers architecture to deal with the technologies and thevulnerabilities associated with it.We included click-jacking in the evaluation of the browsers based on security mainly because click-jacking isa vulnerability that is dependent totally on the browser architecture unlike XSS or CSRF that depend on theserver. The detailed report is put up in the Appendix E section .12 13X. Evaluation TableSLParameterNO.IE Firefox Chrome Opera Weightage1 Web technologies Support51.1 CSS 2.1P Y Y Y1.2 FramesY Y Y Y1.3 Nav LINKSN N N Y1.4 XSLTY Y Y Y1.5 XHTMLN Y Y Y1.6 XFormsN Y N N1.7 Web FormsN N N Y12.5 25 20 301.79 3.57 2.86 4.292 Cross-platform Support72.1 WindowsY Y Y Y2.2 Mac OSN Y N Y2.3 LinuxN Y N Y2.4 UnixN Y N Y7 28 7 281.75 4 1.75 43 Browser Features53.1 Password managingY Y Y Y3.2 Download ManagerN Y Y Y3.3 Bookmarks ManagingY Y Y Y3.4 Form ManagingY Y Y Y3.5 Spell CheckingN Y Y Y3.6 Search toolbarY Y Y Y3.7 Image grabberN N N N3.8 Auto UpdaterY Y Y Y13 14SLParameterNO.IE Firefox Chrome Opera Weightage25 35 35 353.12 4.37 4.37 4.374 Accessibility Features54.1 Tabbed BrowsingY Y Y Y4.2 Pop-up blockingY Y Y Y4.3 Incremental FindingN Y Y Y4.4 Ad FilteringPartial N N Y4.5 Page ZoomingY Y N Y4.6 Full text History searchN N Y Y4.7 HTML access keyY Y Y Y4.8 Tabbing navigationY Y Y Y4.9 Spatial navigationN Y N Y4.10 Caret navigationN Y N N4.11 Voice controlP Y N Y4.12 Text-to-SpeechN Y N Y30 50 30 552.50 4.17 2.50 4.585 Mobile Web technologysupport 75.1 C-HTMLN P N N5.2 HDMLN N N N5.3 I-modeN N N N5.4 XHTML Mobile ProfileN P N N5.5 WMLN N N Y0 7 0 70 1.4 0 1.46 Plugin and Web FeedSupport 514 15SLParameterNO.IE Firefox Chrome Opera Weightage6.1 ActiveXY N N N6.2 NPAPIN Y N Y6.3 JavaN N N Y6.4 GearsY Y Y N6.5 RSSY Y N Y6.6 AtomY Y N Y20 20 5 203.33 3.33 0.83 3.337 Protocol Support57.1 HTTPP Y Y Y7.2 E-mailN N N Y7.3 FTPY Y Y Y7.4 SSLP Y Y Y7.5 EVY Y Y Y7.6 IRCN N N Y7.7 GopherN Y N N7.8 IDNY Y Y Y7.9 Data: URLN Y Y Y7.10 BitTorrentN N N N7.11 IPv6Y Y N Y25 40 30 452.27 3.64 2.73 4.098 Security88.1 Browser Security Settings6 7 4 78.2 Architecture4 6 8 48.3 Clickjacking3 7 3 315 16SLParameterNO.IE Firefox Chrome Opera Weightage13 20 15 144.33 6.67 5.00 4.679 Add-ons5 8 2 4 810 Speed1010.1 Graphics Rendering4 6 9 410.2 Cryptography1 7 9 810.3 Prime Factorization2 5 6 710.4 Cold Start7 2 10 710.5 Warm Start6 5 7 420 25 41 304 5 8.2 611 Benchmark tool testing1011.1 Sunspider JavascriptBenchmark 0 9 10 811.2 ACID 3 Test0 7.1 7.9 8.511.3 CSS Rendering Test7 1 6 87 17.1 23.9 24.52.33 5.7 7.97 8.17IE Firefox Chrome OperaTotal30.42 49.84 38.20 48.90 11416 17XI. Comparative Bar-ChartBenchmark TestSpeedAdd-onsSecurityProtocolPlugin - Web feedMobile w eb techAccessibilityBrow ser FeaturesCross-platformWeb Tech Support0 2 4 6 8 10IE Firefox Chrome Opera17 18XII. Conclusion:As you saw in the evaluation table, all the paramet ers have been given appropriate points and the total has beencalculated for each browser. The results are:CategoryResultBasic browser features (Web technologies Support, Cross-platform Support, Browser Features, Accessibility Features,Mobile Web technology support, Plugin and Web FeedOpera tops with 26.05/39Support, Protocol Support)Security featuresFirefox tops with 6.67/8Add-OnsFirefox tops with 8/8SpeedChrome tops wit h 8.2/10Benchmark Tool Testing Opera tops with 8.17/10OVERALL (all categories tog ether) MOZILLA FIREFOX TOPS with 49.84/75Mozilla Firefox has merged out to be the winner with 49.84 points but it is very closelyfollowed by Opera with 48.90 points .XIII. References[1] Alan Grosskurth and Michael Godfrey. A case study in architectural analysis: The evolution of themodern web browser. EMSE, 2007.[2] Allan Grosskurth and Michael Godfrey. A reference architecture for web browsers. In Journal ofSoftware Maintenence and Evolution: Research and Practice, pages 17, 2006.[3] Nigel McFarlane. Rapid Application Development with Mozilla, pages 1123. Prentice Hall, 2003.[4] mozilla.org. JavaScript Reference Implementation (JSRef) README.http://lxr.mozilla.org/mozilla/source/js/src/README.html.[5] mozilla.org. Module Owners.http://www.mozilla.org/owners.html. Referred 10th Jan 2009[6] mozilla.org. Mozilla Layout Engine. http://www.mozilla.org/newlayout/.[7] mozilla.org. Necko Interfaces Primer. http://www.mozilla.org/projects/netlib/necko interfaceoverview.html.[8] mozilla.org. Networking Library Documentation. http://www.mozilla.org/projects/netlib/.[9] mozilla.org. NGLayout architecture. http://www.mozilla.org/newlayout/overview.html.[10] mozilla.org. Overview of NSS. http://www.mozilla.org/projects/security/pki/nss/overview.html.[11] mozilla.org. Personal SecurityManager (PSM).http://www.mozilla.org/projects/security/pki/psm/.[12] mozilla.org. SpiderMonkey (JavaScript-C) Engine. http://www.mozilla.org/js/spidermonkey.[13] mozilla.org. Storage - MDC. http://developer.mozilla.org/en/docs/Storage.[14] mozilla.org. XPToolkit architecture. http://www.mozilla.org/xpfe/aom/AOM.html.[15] http://www.w3schools.com/JS/ - Javascript Tutorial[16] The Security Architecture of the Chromium Browser by Adam Barth ,Collin Jackson[17] http://www.labnol.org/software/browsers/best-google-chrome-features/4388/ - Google Chromefeatures we miss in other Web browsers[18] http://googleblog.blogspot.com/2008/12/google-chrome-beta.html - Official Google ChromeBlog18 19[19] http://www.extremetech.com/article2/0,2845,2326718,00.asp Browser Comparison[20] http://googlesystem.blogspot.com/2006/05/10-features-youll-find-only-in-opera.html - 10Features youll find only in Opera[21] http://www.opera.com/docs/era/#intro Opera Documentation[22] Adam Barth and Collins Jackson . The Security Architecture of Chromium, Technical report2008[23] Daschuan Yu , Ajay Chander ,Nayeem Islam ,Igor Serikov , Javascript Instrumentation for BrowserSecurity , DoCoMo Communications Laboratories USA.19