Major difference in time metrics between different versions of sitespeed

Hi @soulgalore,

We are currently on version 11.0.0 of sitespeed and looking to upgrade to a newer version. We have attempted this before, but have constantly come up against many issues with the newer versions. I.e. major differences in how sitespeed is measuring the rendering and major differences in the metrics produced.

Example when testing with version 24.0.0 vs 11.0.0. First visual and Last Visual change metrics are way off, i.e. 1.6 seconds vs 9.6 seconds. Am running the exact same script against both versions locally using the following docker command:
docker run --shm-size=2g -vpwd:/sitespeed.io sitespeedio/[sitespeed.io](http://sitespeed.io/)[:24](http://sitespeed.io:24/).0.0 --outputFolder assignment_output8 --speedIndex true --video true --multi ./tests/lp-multi-v3_cp.js --browsertime.url [https://perf-aws.front.develop.squads-dev.com](https://shawneentest-org-dev.com) --browsertime.login testTe --block js-agent.newrelic.com --block www.google-analytics.com --block www.googletagmanager.com --block bam.nr-data.net --browsertime.viewPort 1366X768 --spa --browsertime.iterations 1. The same issue exists when I try running with versions from 18.0.0 upwards :

11.0.0:

24.0.0:

Within the waterfalls for both runs, I can see that when running with version 24.0.0 - firstVisualChange and lastVisualChange measurements have been moved from where they were caught in version 11.0.0. Also 26 requests were hit in version 11.0.0 and only 23 hit in version 24.0.0. See diagrams below:

11.0.0:

24.0.0:

Please advise

Reproduce the comparison using ./tests/lp-multi-v3_cp.js and the Docker commands for sitespeed 11.0.0 and 24.0.0. Compare the First Visual, Last Visual, waterfall placements, and request counts, then review the long discussion for an agreed cause. Done means the version difference is explained and a focused fix or documented compatibility change is identified.