sitespeedio / sitespeedio/sitespeed.io

sitespeedio reporting LCP element incorrectly in the docker version

Open
#4,517 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
5k
Forks
624
Avg merge
4h 8m
Merged PRs (30d)
2

Description

Have you read the documentation?
URL

https://uk.puma.com/uk/en

What are you trying to accomplish
  • Noticed that LCP element is tracked incorrectly while running tests against this page with a video element on viewport (https://uk.puma.com/uk/en) - but only while using the docker version.

  • While using the sitespeedio native app, can see the LCP element is identified correctly - which is the hero video on the view port. Attaching results from this test: sitespeedio-test-native-results.zip

  • Performance tab on Chrome browser also reports the same as LCP element, as expected.
    Image

  • Whereas the sitespeedio docker version apparently tracks LCP element incorrectly! It seems to be not loading the video element correctly and probably causing the LCP element to be tracked incorrectly.
    Attaching results from this test: sitespeedio-test-docker-results.zip.

  • Same config file was used to run the tests on both cases: config_mobile.json

What browser did you use?

Chrome

How to reproduce
- Please run test against URL `https://uk.puma.com/uk/en` using the config file attached above.

- Commands used:
-- native app: 
sitespeed.io --config config_mobile.json https://uk.puma.com/uk/en

-- docker: 
docker run --shm-size=2g --rm -v "$(pwd):/sitespeed.io" sitespeedio/sitespeed.io:37.4.1 --config config_mobile.json https://uk.puma.com/uk/en
Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the page with config_mobile.json using both the native command and the sitespeedio/sitespeed.io:37.4.1 Docker command, then compare the reported LCP element and attached results. Done means the Docker run identifies the hero video consistently with the native app and Chrome Performance results.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.