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.

Programmatic performance scores are consistently worse than from DevTools

See original GitHub issue

For some URLs, but not others, I’m getting consistently lower performance scores when running Lighthouse programmatically than from Chrome DevTools.

For example:

https://marksandspencer.com
Programmatic: 64, 64, 63, 64, 55
DevTools: 86, 73, 84, 77, 80

https://www.littlewoods.com
Programmatic: 46, 48, 50, 50, 49
DevTools: 60, 59, 57, 57, 60

https://asos.com/emporio-armani/emporio-armani-logo-slippers-in-navy/prd/10336705
Programmatic: 10, 8, 10, 9, 8
DevTools: 22, 25, 18, 17, 23

By comparison, for many other sites I get quite consistent results:

https://www.houseoffraser.co.uk
Programmatic: 20, 22, 22, 21, 18
DevTools: 20, 24, 23, 21, 21

https://www.johnlewis.com
Programmatic: 55, 58, 54, 58, 57
DevTools: 56, 53, 52, 52, 52

For the programmatic audit I’m running the Lighthouse sample code with Node 10.6.0.

For the DevTools audit I’m using Canary 73.0.3659.0. AFAIK I don’t have any extensions installed that could affect Lighthouse.

I’m using a Mac, and I’ve tried on home wifi (around 30 Mbps) and work wifi (>100 Mbps).

FWIW I’ve tried headless and non-headless — as expected, that doesn’t seem to make any difference.

Issue Analytics

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

github_iconTop GitHub Comments

1reaction
patrickhulcecommented, Jan 7, 2019

Thanks for the reminder @Hoten! I think he was using Canary to start with 👍

Since this is WAI in Lighthouse, I’m going to go ahead and close, but feel free to chime in with more examples if they don’t seem to fall into one of these categories!

1reaction
connorjclarkcommented, Jan 7, 2019

Please note that there is currently a bug in the latest stable Chrome DevTools that results in Clear Storage never happening - https://github.com/GoogleChrome/lighthouse/issues/6772

This is fixed in Canary and will be in Chrome 72.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Using the Chrome DevTools Audit Feature to Measure and ...
Part 1 defined the problem WebDevs face with app performance and demonstrated how to use the Audit feature of Chrome Developer Tools.
Read more >
Google Lighthouse: What Is It & How Do You Use It?
Take a deep dive into Lighthouse performance metrics with technical SEO pros Jamie Indigo and Rachel Anderson.
Read more >
Reminder to test for performance! This is the website ... - Reddit
If you want an automated scoresheet anyways (as it's a decent baseline), then using something like OP did is fine. I think this...
Read more >
A primer on performance of web applications - O'Reilly
The render engine then takes the tokens and converts them to Document Object Model (DOM) elements (the DOM is the in-memory representation of ......
Read more >
Performance features reference - Chrome Developers
Open the Performance panel of DevTools. Click Reload page Reload Page . DevTools records performance metrics while the page reloads and then ......
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