question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Screenshots don't match with first meaningful paint

See original GitHub issue

Provide the steps to reproduce

Vist https://jantimon.github.io/css-framework-performance/ or

git clone https://github.com/jantimon/css-framework-performance
cd css-framework-performance
npm i
npm run reports

Internally it executes the following command:

  lighthouse
    http://127.0.0.1/
    --throttling.cpuSlowdownMultiplier=4
    --chrome-flags="--headless"

What is the current behavior?

For the default throttling settings the screenshot and the first meaningful paint don’t match at all:

screenshots

The screenshots are all the same inside “screenshot-thumbnails”.

https://github.com/jantimon/css-framework-performance/blob/49e86ee318bb90070f3d80aa711836efa2f92f51/reports/4g/vanilla/index-0.report.json#L110

Full report as html:

https://github.com/jantimon/css-framework-performance/blob/49e86ee318bb90070f3d80aa711836efa2f92f51/reports/4g/vanilla/index-0.report.html

What is the expected behavior?

first meaningful paint should match screenshots like in this example (the first meaning full paint is 1.3s and the screenshot thubmnails show it around the same time):

screenshots

To generate the second image I added --throttling-method=devtools

Environment Information

  • Affected Channels: “@lhci/cli”: “0.3.12”,
  • Lighthouse version: 5.5.0
  • Chrome version: HeadlessChrome/80.0.3987.149
  • Operating System: ubuntu-18.04

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
jantimoncommented, Apr 14, 2020

OH sorry now I get it.

It looks like it works perfectly with --throttling-method=devtools
I just got confused because the numbers in the report didn’t match with the docs https://github.com/GoogleChrome/lighthouse/blob/master/docs/throttling.md

throttle

But that’s only because of https://github.com/GoogleChrome/lighthouse/blob/ac186d0ecbdce739961b7be086dc8f3dbf86f4fa/lighthouse-core/config/constants.js#L8-L15

0reactions
jantimoncommented, Apr 14, 2020

Thank you so much for taking so much time for this.
I will close this issue 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

First Meaningful Paint - Chrome Developers
Learn about Lighthouse's First Meaningful Paint metric and how to measure ... A screenshot of the Lighthouse First Meaningful Paint audit ...
Read more >
Optimize Largest Contentful Paint - web.dev
A step-by-step guide on how to break down LCP and identify key areas to improve.
Read more >
What is First Meaningful Paint (FMP) & Why it Matters for SEO
The First Meaningful Paint or FMP refers to the moment it takes for the page's main content to display on the screen. Google...
Read more >
Evaluating rendering metrics - SpeedCurve
In our experience with the Picker, First Meaningful Paint often doesn't match the point where critical content is rendered. Hero Rendering Times ...
Read more >
How to Improve First Contentful and Meaningful Paint
When the content the user is looking for appears on the page, this is referred to as the first meaningful paint. Screenshot of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found