GoogleChrome / GoogleChrome/lighthouse
Proposal: add PulseCare to Web Perf services in README.md
- Dominant language
- JavaScript
- Stars
- 30.8k
- Forks
- 9.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 20
Description
**Summary**
Hi Lighthouse team,
First of all thank you very-very much for such an amazing tool! Really, thank you guys!
I’m writing to propose adding [PulseCare](https://pulsecare.cloud/) to the community tools section in your README.md.
PulseCare monitors Lighthouse scores, Uptime, Web Vitals and deploy regressions, then explains what changed and what to fix first.
**Key feature:**
We run a full Lighthouse audit against your page and turns the raw result into something you can act on. You get every Core Web Vital measured on real page loads - LCP, CLS, INP/TBT, FCP, TTFB and Speed Index - each scored against the official Google thresholds (good / needs improvement / poor), not just printed as a number.
Every metric comes with its own breakdown rather than a bare score.
LCP is split into its four phases — time to first byte, load delay, load time and render delay — so you see which part actually holds the paint back, with the dominant phase highlighted.
TTFB is broken down the same way across redirect, DNS, connection, TLS and server think-time.
**Visuals:**
I think this tool would be really useful for developers who need to test performance across different regions and troubleshoot various bottlenecks.
Best regards,
Alex Kovalev
Contributor guide
Research direction
Start by opening README.md and locating the community tools section. Add PulseCare with its provided link and a concise description of its Lighthouse and Web Vitals monitoring, then verify that the Markdown renders correctly and the tool appears in the intended section.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100