<div dir="ltr">We're definitely open to changing the speed test. It's being actively worked on. Issues through GitHub probably the best way to engage, but I'm happy to get direct email also.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 4 Jun 2020 at 10:51, Toke Høiland-Jørgensen <<a href="mailto:toke@toke.dk">toke@toke.dk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Jonathan Morton <<a href="mailto:chromatix99@gmail.com" target="_blank">chromatix99@gmail.com</a>> writes:<br>
<br>
>> On 3 Jun, 2020, at 7:48 pm, Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>> wrote:<br>
>> <br>
>> I am of course, always interested in how they are measuring latency, and where.<br>
><br>
> They don't seem to be adding more latency measurements once the<br>
> download tests begin. So in effect they are only measuring idle<br>
> latency.<br>
<br>
Yup, but they do seem to be amenable to fixing that:<br>
<a href="https://github.com/cloudflare/worker-speedtest-template/issues/13" rel="noreferrer" target="_blank">https://github.com/cloudflare/worker-speedtest-template/issues/13</a><br>
<br>
As for where the latency is measured to, it seems to be HTTP 'pings' to<br>
the nearest Cloudflare CDN endpoint.<br>
<br>
-Toke<br>
</blockquote></div>