ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Identify specific long tasks within the main thread for a specific third party
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
Is your feature request related to a problem? Please describe.
I usually use the Chrome Dev Tools to analyze third party scripts, specifically the longest tasks in the main thread. I analyze the JS of the third-parties and try to identify the performance bottlenecks.
Describe the solution you'd like
I'd like to quickly identify such long tasks, the specific points in the JS script which caused them, and see recommendations how to fix them.
Describe alternatives you've considered
My alternative for the moment is to do it manually, but if I can do it with the help of an LLM, it could save me some time.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by reviewing the repository's existing Chrome DevTools MCP capabilities for performance analysis, then determine how long main-thread tasks and third-party script locations would be identified. Done would require a defined way to surface the responsible JavaScript points and actionable recommendations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- devtools, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100