Right now the netlify app for instance sends back requests with Cache-Control: public,max-age=0,must-revalidate headers. This means when each line item fetches the blob URL the cache is now invalid and it gets requested from the server again. If you were running to actually measure a score this would make those numbers invalid as the OS might throttle the CPU during that request and into the start of the line item.
Right now the netlify app for instance sends back requests with
Cache-Control: public,max-age=0,must-revalidateheaders. This means when each line item fetches the blob URL the cache is now invalid and it gets requested from the server again. If you were running to actually measure a score this would make those numbers invalid as the OS might throttle the CPU during that request and into the start of the line item.