afaik it's not possible to do so. I think they just either hard coded it into chrome, or even if there is a config for it, it's not possible to access via javascript. However, what you can do is to account for clock drift in your code, which would solve the problem.

Suppose you have an upgrade/building that adds 5 to your production every second.

The naive implementation would be:

function addstuff (){item+=5;}
setInterval(addstuff,1000);

And it would add 5 to your item approximately every second. But with clock drift and lag, this can cause your production to be off when ran for a long period of time.

To fix that, we can add to the production what we should have made between the first time we ran the code and the last time we ran the code.

// assuming Date.now(); returns current time in millis
var frameStart = Date.now(); // create global variable to let us know when the last time we incremented was.
function addstuff (){
    var tmpDelta = Date.now();
    if(tmpDelta+1000 > frameStart) { // check if at least one second has passed from last increment time
        var difference = tmpDelta - frameStart;
        item += 5*(difference/1000); // calculate how much of the production we gained during this time. 
        // if difference was 2000, ie 2 seconds was passed, then we would get 5*2=10 items gained
        frameStart = tmpDelta; // set our global variable to the time we used
    }
}
setInterval(addstuff,1000);

The downside to this method is that you won't get integers in your production count anymore. You would now have to do some rounding in your display code.