Transfer Size is incorrect in resource-summary audit
See original GitHub issueProvide the steps to reproduce
- Run LH on https://test.lucacasonato.vercel.app/
- View
Keep request counts low and transfer sizes small
diagnostics
What is the current behavior?
The Transfer Size
is not correct. It is double, triple, quadruple, or 10 fold the actual value:
It says 0.5 kb for Script
in Lighthouse
vs 48 bytes in network panel:
Here is a JSON export from Lighthouse on this page: test.lucacasonato.vercel.app-20200911T201026.txt
What is the expected behavior?
I expect Lighthouse to show the correct values.
Environment Information
- Affected Channels: DevTools
- Lighthouse version: 6.3.0
- Chrome version: 87.0.4259.3 (Official Build) dev (64-bit)>
- Operating System: Linux
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:14
Top Results From Across the Web
Keep request counts low and transfer sizes small
Learn how high resource counts and large transfer sizes affect load performance. Get strategies for reducing request counts and transfer sizes.
Read more >AS 2810: Evaluating Audit Results - PCAOB
If the auditor concludes that the amount of an accounting estimate included in the financial statements is unreasonable or was not determined in...
Read more >Evaluation of Misstatements Identified During the Audit | AICPA
and the amount, classification, presentation, or disclosure that is ... auditor should request management to correct those misstatements. (Ref: par.
Read more >Common IRS Audit Triggers - Bloomberg Tax
Learn the characteristics of a tax return that triggers audits by the ... up-to-the-minute news, analysis, primary sources, tools, and more.
Read more >Professional Judgment Resource - The Center For Audit Quality
2 Professional Judgment Resource. Overview. Auditors can enhance their professional judgment capabilities by utilizing an effective decision-making process ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Bisect gave me: https://chromium.googlesource.com/chromium/src/+log/41ce21f10c765a426cc990c4714506ee4424347c..1079b28e253fa321c8d9379fed1e69b5b5c6fbbb
I wonder which one it is 😉
https://chromium.googlesource.com/chromium/src/+/1079b28e253fa321c8d9379fed1e69b5b5c6fbbb (I forgot about this).
For Paul’s example, I noticed in CLI I get two
dataReceived
events for that request. The first is 63390 bytes. the second is zero. The incorrect value that Lighthouse gets in devtools is 126780, which is 63390 * 2.I believe I summarized the behavior of
dataReceived
in a previous PR, I’ll have to comb through this file’s history to find it. But I can definitely confirm this is a bug in Lighthouse’ DevTools integration.