Skip to content

Change label to "inc. soft navs" - #1375

Open
tunetheweb wants to merge 1 commit into
mainfrom
soft-navs-label
Open

tunetheweb wants to merge 1 commit into
mainfrom
soft-navs-label

Conversation

@tunetheweb

Copy link
Copy Markdown
Member

Had complaints that "(with soft navs)" and "(soft navs)" are ambiguous.

@github-actions

Copy link
Copy Markdown
Contributor

Visit the preview URL for this PR (updated for commit 3d43729):

https://httparchive--pr1375-soft-navs-label-3ovpspoq.web.app

(expires Mon, 26 Oct 2026 08:53:39 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 1069cba7974889c25bacf4f0a19ddb6735592729

Comment thread config/techreport.json
},
{
"label": "Good Core Web Vitals (with soft navs)",
"label": "Good Core Web Vitals (inc. soft navs)",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking to expand into incl., but I understand the confusion is about defining its additive definition.

+ version seems most straightforward.

Suggested change
"label": "Good Core Web Vitals (inc. soft navs)",
"label": "Good Core Web Vitals (+ soft navs)",

WDYT?

@max-ostapenko

max-ostapenko commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Let's also add details here:

"description": "The percentage of origins passing all three Core Web Vitals (LCP, INP, CLS) with a good experience, accounting for soft navigations in single-page applications. Note that if an origin is missing INP data, it's assessed based on the performance of the remaining metrics."
},

Maybe just making 'soft havs' bold.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants