jsPerf.app is an online JavaScript performance benchmark test runner & jsperf.com mirror. It is a complete rewrite in homage to the once excellent jsperf.com now with hopefully a more modern & maintainable codebase.

jsperf.com URLs are mirrored at the same path, e.g:

https://jsperf.com/negative-modulo/2

Can be accessed at:

https://jsperf.app/negative-modulo/2

Google Analytics protocol check versus hardcoded string (v2)

Revision 2 of this benchmark created by John-David Dalton on December 24, 2011

Description

The snippets I’m comparing here aren’t quite the same, but for HTTP-only websites it doesn’t make a difference. See the “Use the protocol check only when it’s needed” section in my article on optimizing the asynchronous Google Analytics snippet for more information.

Setup

var location = window.location;

Test runner

Ready to run.

Test Ops/sec

Ternary protocol check

Testing in
Test	Ops/sec
Ternary protocol check	`('https:' == location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';`	ready
ternary best	`('https:' == location.protocol ? 'https://ssl.google-analytics.com/ga.js' : 'http://www.google-analytics.com/ga.js');`	ready
hardcoded string	`'//www.google-analytics.com/ga.js';`	ready

('https:' == location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';

ready

ternary best

('https:' == location.protocol ? 'https://ssl.google-analytics.com/ga.js' : 'http://www.google-analytics.com/ga.js');

ready

hardcoded string

'//www.google-analytics.com/ga.js';

ready

Revisions

You can edit these tests or add more tests to this page by appending /edit to the URL.

Revision 1: published by Mathias Bynens on April 11, 2010
Revision 2: published by John-David Dalton on December 24, 2011
Revision 3: published on January 6, 2012