This skill enables automated Chrome browser testing and performance analysis using the Chrome DevTools Protocol (CDP) via the chrome-devtools-mcp server. It provides access to 27 professional-grade tools for web application testing, performance measurement, accessibility validation, and browser automation.
git clone https://github.com/justfinethanku/cc_chrome_devtools_mcp_skill.gitThe cc_chrome_devtools_mcp_skill is an advanced automation tool designed for developers and product managers who need to conduct thorough testing and performance analysis of web applications. By leveraging the Chrome DevTools Protocol (CDP) through the chrome-devtools-mcp server, this skill provides access to 27 professional-grade tools that facilitate web application testing, performance measurement, accessibility validation, and browser automation. This powerful capability allows users to automate repetitive tasks, ensuring higher efficiency in their development workflows. One of the key benefits of this skill is its ability to significantly reduce the time spent on manual testing processes. While exact time savings are not quantified, the automation of browser testing and performance analysis can lead to faster deployment cycles and improved product quality. Developers can focus on writing code and enhancing features rather than getting bogged down by time-consuming testing procedures. This skill is particularly beneficial for teams looking to implement continuous integration and continuous deployment (CI/CD) practices, as it fits seamlessly into an AI-first workflow. This skill is ideal for intermediate-level developers and product managers who are responsible for ensuring the quality and performance of web applications. It empowers teams to validate their applications against industry standards and accessibility guidelines, making it an essential tool for any organization that prioritizes user experience. For example, a developer could use this skill to automate the testing of a new feature in a web application, ensuring that it performs well across different browsers and devices without the need for extensive manual testing. Implementation of the cc_chrome_devtools_mcp_skill is straightforward, requiring approximately 30 minutes to set up. Users should have a basic understanding of the Chrome DevTools and how to interact with the CDP. This skill not only enhances testing capabilities but also integrates well into existing workflows, making it a valuable addition to any development toolkit. By adopting this skill, teams can elevate their testing processes, paving the way for more robust and reliable web applications.
1. **Set Up Environment** - Install the chrome-devtools-mcp server and ensure it's running - Install required dependencies: `npm install @modelcontextprotocol/chrome-devtools-mcp` - Configure your AI assistant to use the MCP server endpoint 2. **Prepare Test Case** - Identify the specific workflow to test (e.g., 'candidate application submission') - Gather required credentials if testing authenticated areas - Note any specific performance thresholds or accessibility standards 3. **Execute Test** - Use the prompt template to generate your test command - Run the test during off-peak hours to avoid performance interference - Monitor the process for any errors or timeouts 4. **Analyze Results** - Review the performance metrics against your benchmarks - Check accessibility violations against WCAG 2.1 standards - Examine console logs for errors and warnings - Compare screenshots with expected behavior 5. **Generate Report** - Use the output to create a prioritized action list - Share findings with development/QA teams - Schedule follow-up tests after implementing fixes **Tips for Better Results:** - Test on multiple devices/browsers if cross-platform compatibility is important - Run tests at different times of day to identify performance variations - Compare results before/after code changes to measure impact - Use the `Network` tab in DevTools to simulate slow network conditions (3G, 4G)
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/justfinethanku/cc_chrome_devtools_mcp_skillCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Use the Chrome DevTools Protocol via the chrome-devtools-mcp server to automate testing of [WEBSITE_URL] for [SPECIFIC_TEST_CASE]. Focus on [PERFORMANCE_METRICS] and [ACCESSIBILITY_CHECKS]. Generate a detailed report including screenshots, console logs, and performance timings. If any issues are found, suggest fixes for [DEVELOPMENT_TEAM].
### Automated Chrome DevTools Analysis Report **Website:** https://recruit.jazzhr.com/candidates **Test Case:** Candidate application submission flow **Date:** 2024-05-15 **Performed by:** Chrome DevTools MCP Server #### Performance Metrics - **Page Load Time:** 2.4s (Target: <2s) ⚠️ - DOMContentLoaded: 1.8s - Load Event: 2.4s - First Contentful Paint: 1.1s - Largest Contentful Paint: 1.9s - **JavaScript Execution:** 850ms (High) - Main thread blocked for 420ms during script execution - 3 unused JavaScript files detected (total 450KB) - **Network Requests:** 47 total (12 blocked by ad blockers) - Largest resource: 1.2MB CSS file - 5 render-blocking resources #### Accessibility Checks - **Color Contrast:** 3 violations found - Login button: 2.8:1 (needs 4.5:1) - Error messages: 3.1:1 (needs 4.5:1) - **Keyboard Navigation:** 2 issues - Dropdown menus not fully keyboard accessible - Focus order incorrect in application form - **ARIA Attributes:** 4 missing labels detected - Form fields lack proper ARIA labels - Screen reader compatibility issues in candidate profile section #### Screenshots 1. **Page Load Performance** (attached as performance_timeline.png) - Visualizes the critical rendering path - Highlights 1.2s gap between DOM load and visual completion 2. **Accessibility Violations** (attached as a11y_violations.png) - Shows color contrast issues in candidate portal - Highlights keyboard navigation problems in application form #### Console Logs ``` [WARNING] 404 GET /assets/js/unused-lib.js (404) [ERROR] Uncaught TypeError: Cannot read property 'addEventListener' of null (candidate-form.js:42) [WARNING] 5 render-blocking CSS resources detected ``` #### Recommendations 1. **Performance Optimization** - Defer non-critical JavaScript (estimated 300ms savings) - Compress CSS files (potential 200KB reduction) - Implement lazy loading for images below fold - Use `preload` for critical resources 2. **Accessibility Fixes** - Increase color contrast for buttons and error messages - Add proper ARIA labels to all form fields - Fix keyboard navigation order in application form - Implement focus management for modal dialogs 3. **Code Quality** - Remove unused JavaScript files (450KB savings) - Fix TypeError in candidate-form.js line 42 - Replace blocking CSS with inline critical CSS **Next Steps:** Share this report with the development team for implementation. Prioritize fixes based on impact: performance issues first (highest user impact), then accessibility (compliance requirements).
Find high-paying freight loads instantly
Automate your browser workflows effortlessly
Streamline tech recruiting with automated coding assessments and customizable tests.
IronCalc is a spreadsheet engine and ecosystem
Foster employee recognition with customizable rewards and real-time peer acknowledgments.
Get more done every day with Microsoft Teams – powered by AI
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan