Lighthouse viewport is still in mobile view after running test using desktop configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, javascript
- Domain
- performance
Research direction
Start by reproducing the reported Docker command with sitespeed.io 17.1.1-plus1 and the Lighthouse desktop settings. Compare the generated screenshot and Lighthouse report with the requested viewport configuration; done means the screenshot and diagnostics use desktop rather than mobile settings.
Written by the indexing model from the issue text.
Description
I am having trouble running sitespeed 17.1.1-plus1 using lighthouse plugin. My configuration settings seems working fine but based on lighthouse report, the screenshot is in mobile view. Here's my command running tests:
docker run --name sitespeed --volumes-from=jenkins --network=host --privileged=true --shm-size=1g --rm -v \"/tmp/sitespeed.io/\":/sitespeed.io \sitespeedio/sitespeed.io:17.1.1-plus1 --plugins.remove browsertime \--lighthouse.settings.screenEmulation.mobile false --lighthouse.settings.formFactor desktop --lighthouse.settings.throttling.rttMs 40 --lighthouse.settings.throttling.throughputKbps 10240 --lighthouse.settings.throttling.cpuSlowdownMultiplier 1 \--graphite.host localhost --graphite.port 2003 --graphite.httpPort 8080 --graphite.namespace TestFolderD.default
See screenshot attached:
Viewport is in mobile
But the summary setting is in desktop
I also tried using the --lighthouse.setting.preset desktop but its not working as well.
Please help me guys, it gives discrepancy on lighthouse opportunities and diagnostics as well. Thanks a lot.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sitespeedio/plugin-lighthouse
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
sitespeedio/plugin-lighthouse#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#134 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#133 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#126 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#120 · 7 comments ·
All issues in sitespeedio/plugin-lighthouse
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100