Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

sitespeedio/sitespeed.io:17.0.0-alpha.2-plus1 lighthouse core web vital on Grafana/graphite don't seem to match with lighthouse.pageSummary.json

Open
#82 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Reproduce the mismatch using sitespeedio/sitespeed.io:17.0.0-alpha.2-plus1 with both lighthouse and gpsi enabled, comparing the first and subsequent runs. Inspect the plugin’s Lighthouse metric collection and Graphite/dashboard output against lighthouse.pageSummary.json for FCP, LCP, TBT, and CLS. Done means repeated runs consistently report values matching the JSON file.

Written by the indexing model from the issue text.

Description

prio:low

Hi Peter, sorry to bother you.

I have been testing your alpha release you made to store lighthouse web vitals to graphite and display value on dashboard sitespeedio/sitespeed.io:17.0.0-alpha.2-plus1 . I noticed weirdness with values, I am not sure if i am correct but i also understand that its not a stable release yet. I am able to display data in dashboard but those values do not match with lighthouse.pageSummary.json report file. FCP LCP TBT . maybe i am looking at it from a wrong view but i am correct to say those values should match ?

CLS seems to always be correct but the rest do not match.

I have both lighthouse and gpsi enabled.

it seems like on the 1st run it match with report file but any subsequent runs just looks off.

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

  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.

More from sitespeedio/plugin-lighthouse

All issues in sitespeedio/plugin-lighthouse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.