From e2b17c2d9cd182eaa3f69fa9bf3f2cbbb9d3e38e Mon Sep 17 00:00:00 2001 From: Zuzana Fatrdla Date: Mon, 3 Aug 2026 16:33:53 +0200 Subject: [PATCH] Add PageSpeed.ONE to Testing & Quality Adds PageSpeed.ONE at the bottom of the section, next to the other quality monitoring tools. There is no dedicated performance section, and this fits alongside the browser testing and continuous inspection entries. I'm a developer of PageSpeed.ONE, so treat this as a suggestion. Happy to adjust the wording or placement, or drop it, if it doesn't meet the bar. --- readme.md | 1 + 1 file changed, 1 insertion(+) diff --git a/readme.md b/readme.md index 88e1a50..8009459 100644 --- a/readme.md +++ b/readme.md @@ -116,6 +116,7 @@ Inspired by [awesome](https://github.com/sindresorhus/awesome). * [ESLint](https://eslint.org/) - Linting utility for JavaScript and TypeScript. * [Prettier](https://prettier.io/) - Opinionated code formatter. * [SonarQube](https://www.sonarsource.com/products/sonarqube/) - Continuous inspection of code quality. +* [PageSpeed.ONE](https://pagespeed.one/en) - Page speed monitoring with daily synthetic tests and current and historical CrUX field data for Core Web Vitals. ## Docs & Knowledge