browser

janneke dust2 schreef:Als er een browser zou zijn die veel sneller,beter en veiliger zou zijn dan zou iedereen die gebruiken.
Meestal zijn het kleine details die de voorkeur van iemand bepalen of gewoon van iets horen zeggen.

iceman1718 schreef:Allemaal statistieken. Larie en apekoek.
Hou je computer schoon.
Meer moet je niet doen.

brisamar schreef:Welke zou de snelste browser zijn ?

Accuracy
Measuring browser usage in the number of requests (page hits) made by each user agent can be misleading.

Overestimation
Not all requests are generated by a user, as a user agent can make requests at regular time intervals without user input. In this case, the user's activity might be overestimated. Some examples:

- Certain anti-virus products fake their user-agent to appear to be popular browsers. This is done to trick attack sites that might display clean content to the scanner, but not to the browser. The Register reported in June 2008 that traffic from AVG Linkscanner, using an IE6 user-agent, outstripped human link clicks by nearly 10 to 1.

- A user who revisits a site shortly after changing or upgrading browsers may be double-counted under some methods; overall numbers at the time of a new version's release may be skewed.

- Occasionally websites are written in such a way that they effectively block certain browsers. One common reason for this is that the website has been tested to work with only a limited number of browsers, and so the site owners enforce that only tested browsers are allowed to view the content, while all other browsers are sent a 'failure' message, and instruction to use another browser. Many of the untested browsers may still be otherwise capable of serving the content. Sophisticated users who are aware of this may then 'spoof' the user-agent in order to gain access to the site.

- The browsers Chrome, Safari and Opera will under some circumstances fetch resources before they need to render them, so that the resources can be used faster if they are needed. This technique, prerendering or pre-loading, may inflate the statistics for the browsers using it because of pre-loading of resources which are not used in the end.


Underestimation
It is also possible to underestimate the usage share by using the number of requests, for example:

- Opera and Gecko-based browsers since Firefox 1.5 use fast Document Object Model (DOM) caching. JavaScript is only executed on pageload from net or disk cache, but not if it is loaded from DOM cache. This can have an impact on JavaScript-based tracking of browser statistics.

- While most browsers generate additional page hits by refreshing web pages when the user navigates back through page history, some browsers (such as Opera) reuse cached content without resending requests to the server.

- Generally, the more faithfully a browser implements HTTP's cache specifications, the more it will be under-reported relative to browsers that implement those specifications poorly.

- Some ISPs, mainly mobile network operators, have begun stripping the user agent strings.

- Browser users may run site, cookie and JavaScript blockers which cause those users to be under-counted. For example, common AdBlock blocklists such as EasyBlock include sites such as StatCounter in their privacy lists, and NoScript blocks all JavaScript by default. addons.mozilla.org reports 15.0 million users of AdBlock variants and 2.2 million users of NoScript.



Differences in measurement
Net Applications and W3Counter[citation needed] use unique visitors to measure web usage.[9] This has the effect that users visiting a site ten times will only be counted once by these sources, while they are counted ten times by statistics companies that measure page hits.

Net Applications also uses country-level weighting to correct for bias caused by variation in sampling rates across countries.[10] All statistics suffer from sampling bias and can not be considered representative.