Add PageSpeed.ONE to Browser & Frontend Performance - #13
Open
zuzanafatrdla wants to merge 1 commit into
Open
Conversation
Adds PageSpeed.ONE alongside the existing commercial entries in the same section (SpeedCurve, DebugBear), marked as commercial per CONTRIBUTING. Also fixes a missing line break where the Puppeteer and SpeedCurve entries were joined on a single line. Disclosure: submitted by a member of the PageSpeed.ONE team.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! Thanks for maintaining this list.
I'd like to propose adding PageSpeed.ONE to the Browser & Frontend Performance section. It's a page speed monitoring tool that runs daily synthetic tests and shows current and historical CrUX field data for Core Web Vitals. I added it the same space as SpeedCurve and DebugBear already listed in that section.
Disclosure: I'm part of the PageSpeed.ONE team, so please treat this as a suggestion and I am happy to adjust the wording or drop it if you don't think it meets the bar.
I marked my contribution as commercial (🟠)
Drive-by fix
This PR also fixes a missing line break in the same section, where the Puppeteer and SpeedCurve entries were joined on a single line. Happy to split that into a separate PR if you'd prefer to keep this one tool-only.