Browser Engine Benchmark

A toolkit for testing browser automation engines against modern web protection systems. It checks how well each engine can bypass bot detection and measures their speed, resource usage, and resistance to fingerprinting.

(Need some help with Automation? You can hire me for custom development or consulting!)

🎯 Overview

Modern web applications use advanced bot detection like Cloudflare, DataDome, and Imperva to block automated access. This benchmark suite shows how different browser automation engines handle these defenses:

• Bypass Success Rate: Effectiveness against major protection systems
• Performance Metrics: Memory usage, CPU consumption, and page load times
• Fingerprinting Resistance: reCAPTCHA scores and CreepJS trust ratings
• Network Analysis: IP detection (proxy validation) and WebRTC leak testing

🚀 Key Features

Protection System Testing

• Cloudflare
• DataDome
• Amazon
• Google Search
• Ticketmaster (Imperva)
• Akamai
• PerimeterX / HUMAN Security
• Kasada
• Reddit
• More systems coming soon

Browser Engine Support

• AdsPower - (Proprietary) Anti-detect browser with per-profile fingerprinting. Requires AdsPower desktop app running locally and an API key.
• Playwright - (Open-Source) Microsoft's automation framework (Chrome, Firefox, Safari)
• Camoufox - (Open-Source) Playwright-based
• Patchright - (Open-Source) Playwright-based
• Playwright Stealth - (Open-Source) Playwright-based
• CloakBrowser - (Open-Source) Playwright-based
• Selenium - (Open-Source) Browser automation framework (apparently deprecated, so it is tested without proxies)
• Seleniumbase - (Open-Source) Professional toolkit for web automation activities
• NoDriver - (Open-Source) Browser automation framework (supports only SOCKS5 proxies)
• ZenDriver - (Open-Source) NoDriver-based
• More engines coming soon. What engine should I add next?

Analytics

• Automated report generation with visualizations
• Performance profiling and resource usage tracking
• Exportable results in JSON and Markdown formats

🔒 Important: Proxy Requirements

Using a clean proxy is essential for accurate benchmark results.

Why Proxies Are Required

• IP Reputation: Your home/datacenter IP may already be flagged by protection systems from previous automation attempts, browser extensions, or security software
• Clean Testing Environment: A fresh proxy IP ensures you're testing the browser engine's capabilities, not your IP's reputation
• Rate Limiting: Repeated tests from the same IP can trigger rate limiting, affecting bypass success rates

---

Swiftproxy — Premium residential proxies with 80M+ IPs across 190+ countries, non-expiring traffic, and high-anonymity connections. Built for web scraping, protocol analysis, AI agents, browser automation, and large-scale data collection.

🔗 https://www.swiftproxy.net

---

📊 Sample Results

This benchmark provides detailed comparative analysis. Here's an excerpt from a recent test run (more in results/example):
Real IP in this example - 146.70.188.179
Proxy IP in this example is different for each engine

Overall Bypass Rate

Engine	Bypass Rate (%)
patchright	100.0
cloakbrowser	90.0
camoufox_headless	90.0
nodriver-chrome	80.0
adspower	80.0
seleniumbase-cdp-chrome	80.0
adspower_headless	70.0
tf-playwright-stealth-firefox	70.0
tf-playwright-stealth-firefox_headless	70.0
zendriver-chrome	70.0
cloakbrowser_headless	60.0
tf-playwright-stealth-chromium	60.0
playwright-chrome	60.0
playwright-firefox_headless	60.0
playwright-firefox	60.0
zendriver-chrome_headless	60.0
tf-playwright-stealth-chromium_headless	50.0
selenium-chrome__no_proxy	50.0
playwright-chrome_headless	40.0
nodriver-chrome_headless	40.0
patchright_headless	40.0
camoufox	30.0
selenium-chrome_headless__no_proxy	30.0

Resource Usage Comparison

Engine	Memory Usage (MB)	CPU Usage (%)
adspower_headless	123.0	4.9
adspower	130.0	7.0
playwright-chrome_headless	517.0	7.4
tf-playwright-stealth-chromium_headless	522.0	8.2
zendriver-chrome_headless	818.0	21.5
tf-playwright-stealth-chromium	913.0	28.6
cloakbrowser_headless	936.0	27.2
selenium-chrome_headless__no_proxy	948.0	10.1
zendriver-chrome	1009.0	38.8
selenium-chrome__no_proxy	1034.0	29.8
tf-playwright-stealth-firefox_headless	1034.0	44.7
playwright-firefox_headless	1068.0	70.3
cloakbrowser	1082.0	54.4
playwright-chrome	1103.0	28.5
seleniumbase-cdp-chrome	1157.0	51.9
playwright-firefox	1161.0	75.5
camoufox	1181.0	53.3
tf-playwright-stealth-firefox	1261.0	67.7
nodriver-chrome_headless	1275.0	24.4
patchright_headless	1277.0	16.6
patchright	1314.0	53.3
camoufox_headless	1318.0	88.6
nodriver-chrome	1389.0	47.4

Recaptcha Scores - https://antcpt.com/score_detector

Engine	Recaptcha Score (0-1)
adspower	0.90
adspower_headless	0.90
camoufox_headless	0.90
cloakbrowser	0.90
cloakbrowser_headless	0.90
nodriver-chrome	0.90
nodriver-chrome_headless	0.90
patchright	0.90
patchright_headless	0.90
playwright-chrome	0.90
playwright-chrome_headless	0.90
playwright-firefox	0.90
playwright-firefox_headless	0.90
selenium-chrome__no_proxy	0.90
selenium-chrome_headless__no_proxy	0.90
seleniumbase-cdp-chrome	0.90
tf-playwright-stealth-chromium	0.90
tf-playwright-stealth-chromium_headless	0.90
tf-playwright-stealth-firefox	0.90
tf-playwright-stealth-firefox_headless	0.90
camoufox	nan
zendriver-chrome	nan
zendriver-chrome_headless	nan

Note 1: "nan" indicates no score was obtained - the website just stopped working when tests were run

Note 2: This Score is taken by solving the reCAPTCHA v3 on your browser. The Score shows if Google considers you as HUMAN or BOT. 1.0 is very likely a good interaction, 0.0 is very likely a bot With low score values (< 0.3) you'll get a slow reCAPTCHA 2, it would be hard to solve it. And vise versa, with score >= 0.7 it will be much easier.

CreepJS Scores - https://abrahamjuliot.github.io/creepjs

Engine	Trust Score (%)	Bot Score (%)	WebRTC IP
adspower	0.00	0.00	90.214.10.188
adspower_headless	0.00	0.00	177.93.10.239
camoufox_headless	0.00	0.00	186.86.110.232
cloakbrowser	0.00	0.00
cloakbrowser_headless	0.00	0.00
nodriver-chrome	0.00	0.00	146.70.188.179
nodriver-chrome_headless	0.00	0.00	146.70.188.179
patchright	0.00	0.00	146.70.188.179
patchright_headless	0.00	0.00	146.70.188.179
playwright-chrome	0.00	0.00	146.70.188.179
playwright-chrome_headless	0.00	0.00	146.70.188.179
playwright-firefox	0.00	0.00	146.70.188.179
playwright-firefox_headless	0.00	0.00	146.70.188.179
selenium-chrome__no_proxy	0.00	0.00	146.70.188.179
selenium-chrome_headless__no_proxy	0.00	0.00	146.70.188.179
seleniumbase-cdp-chrome	0.00	0.00
tf-playwright-stealth-chromium	0.00	0.00	146.70.188.179
tf-playwright-stealth-chromium_headless	0.00	0.00	146.70.188.179
tf-playwright-stealth-firefox	0.00	0.00	146.70.188.179
tf-playwright-stealth-firefox_headless	0.00	0.00	146.70.188.179
zendriver-chrome	0.00	0.00
zendriver-chrome_headless	0.00	0.00
camoufox	nan	nan	Not detected

Note:

1. CreepJS disabled trust and bot scores for now - abrahamjuliot/creepjs#292
2. If the WebRTC IP is different from your real IP - no leakage (applicable only with proxy).

IP (Ipify)

Engine	IP
adspower	90.214.10.188
adspower_headless	177.93.10.239
camoufox	Not detected
camoufox_headless	186.86.110.232
cloakbrowser	179.0.46.130
cloakbrowser_headless	193.5.237.36
nodriver-chrome	190.232.219.121
nodriver-chrome_headless	91.54.173.199
patchright	24.78.176.233
patchright_headless	181.46.71.26
playwright-chrome	89.247.171.61
playwright-chrome_headless	196.65.213.80
playwright-firefox	79.8.183.149
playwright-firefox_headless	130.0.11.123
selenium-chrome__no_proxy	146.70.188.179
selenium-chrome_headless__no_proxy	146.70.188.179
seleniumbase-cdp-chrome	142.173.54.135
tf-playwright-stealth-chromium	212.237.121.217
tf-playwright-stealth-chromium_headless	83.168.89.168
tf-playwright-stealth-firefox	196.98.139.187
tf-playwright-stealth-firefox_headless	45.227.249.248
zendriver-chrome	47.234.192.130
zendriver-chrome_headless	142.173.61.185

Note: If the IP is your proxy's IP - good, your real IP - bad (applicapable only with proxy).

Visual Dashboard

Recaptcha Score Visualization

CreepJS Visualization

🛠️ Installation

Quick Start

1. Clone the repository

   git clone https://github.com/techinz/browsers-benchmark.git
   cd browsers-benchmark

2. Set up Python environment

   python -m venv venv
   source venv/bin/activate  # On Windows: venv\Scripts\activate
   pip install -r requirements.txt

3. Install browser engines

   Playwright

   playwright install
   # On Linux also run:
   playwright install-deps

   Camoufox

   # Windows
   camoufox fetch
   
   # Linux  
   python -m camoufox fetch
   sudo apt install -y libgtk-3-0 libx11-xcb1 libasound2

   Patchright

   patchright install chromium

   AdsPower (optional)

   1. Download and install AdsPower desktop app
   2. Open AdsPower, go to Settings → API and enable the local API
   3. Copy your API key and set ADSPOWER_API_KEY in .env
   4. Keep AdsPower running while the benchmark is active - it manages the browser process

4. Configure settings

   cp .env.example .env
   # Edit .env with your proxy settings if needed

5. Configure proxies

   1. Create a file named proxies.txt in the documents directory.
   2. Add your proxy URLs in format http://username:password@proxy_host:port or http://proxy_host:port.
      ❗️ IMPORTANT (1): Number of proxies has to be not less than number of engines you want to test.
      ❗️ IMPORTANT (2): Some engines support different proxy protocols - for example, Playwright supports only HTTP and HTTPS, but NoDriver supports only SOCKS5.
      This implies that you have to add multiple proxy protocols to the proxies.txt file or exclude some engines from the test.
      At the moment you need all HTTP/HTTPS proxies and at least 1 SOCKS5 for NoDriver. Also, the benchmark will show you what proxy protocols are missing.
      ❗️ IMPORTANT (3): Selenium won't use any proxies.

   Example proxies.txt content (each line is a separate proxy):

   http://proxy1.example.com:8080
   http://proxy2.example.com:8080
   http://username:password@proxy3.example.com:8080
   http://username:password@proxy4.example.com:8080
   socks5://username:password@proxy5.example.com:8080
   

6. Run benchmark

   python main.py

⚙️ Configuration

Environment Variables (.env)

# Proxy Configuration (highly recommended to enable)
PROXY_ENABLED=true
PROXY_FILE_PATH=documents/proxies.txt
PROXY_MAX_RETRIES=3

# Performance Settings
PAGE_LOAD_TIMEOUT_S=90
PAGE_STABILIZATION_DELAY_S=5
MAX_RETRIES=3

# AdsPower (optional — only needed if running the adspower engine)
# Get your API key from AdsPower desktop app: Settings → API
ADSPOWER_API_KEY=your_api_key_here
ADSPOWER_BASE_URL=http://local.adspower.net:50325
ADSPOWER_GROUP_ID=

📈 Output & Reports

The benchmark generates reports in the results/ directory:

• summary.md - Human-readable markdown report
• benchmark_results.json - Raw data for further analysis
• media/ - Generated visualizations and screenshots
  • bypass_dashboard.png - Multi-metric dashboard
  • recaptcha_scores.png - reCAPTCHA performance chart
  • creepjs_scores.png - Fingerprinting resistance analysis
  • screenshots - Screenshots of all tested targets

🏗️ Architecture

The codebase follows a modular architecture for extensibility:

├── config/           # Configuration management
├── engines/          # Browser engine implementations  
├── utils/
│   ├── targets/      # Test target definitions
│   ├── report/       # Report generation system
│   ├── logging/      # Structured logging
│   └── ...
└── results/          # Output directory

Adding New Targets

1. Modify config/benchmark_targets.py to add custom test targets:

   Target(
       name="custom_site",
       url="https://example.com",
       check_function="check_custom_bypass",
       description="Custom site protection test"
   )

2. Create a check function for the target in utils/targets/check_bypass, for example in a file named custom_bypass.py:

   from engines.base import BrowserEngine
   
   async def check_custom_bypass(engine: BrowserEngine) -> bool:
       element_found, element_html = await engine.locator('//div[@class="captcha"]')
   
       return not element_found # no captcha found - success!

3. Add it to the checkers mapping in config/benchmark_targets.py's BypassTargetsSettings:

   checkers: Dict[str, Callable] = Field(
       default_factory=lambda: {
           "check_cloudflare_bypass": check_cloudflare_bypass,
           "check_datadome_bypass": check_datadome_bypass,
           ...
           "check_custom_bypass": check_custom_bypass,
       }
   )

Adding New Engines

1. Extend the BrowserEngine base class:

   class CustomEngine(BrowserEngine):
       async def start(self) -> None:
           # Initialize browser
           
       async def navigate(self, url: str) -> Dict[str, Any]:
           # Navigation logic

   Or, if Playwright-based, extend PlaywrightBase base class:

   class CustomPlaywrightBasedEngine(PlaywrightBase):
       ...

   Or, if Selenium-based, extend SeleniumBase base class:

   class CustomSeleniumBasedEngine(SeleniumBase):
       ...

2. Add it to the engines mapping in config/engines.py's EnginesSettings:

   base_engines = [
           {
               "class": PlaywrightEngine,
               "params": {"headless": True, "name": "playwright-chrome_headless", "browser_type": "chromium"}
           },
           ...
           {
               "class": CustomEngine,
               "params": {"headless": True, "name": "custom_engine", "browser_type": "chromium"}
           }
   ]

🔧 Platform-Specific Notes

Troubleshooting

Common Issues:

• Detection failures: Verify proxy configuration and target accessibility

🤝 Contributing

Contributions are welcome! Areas where help is needed:

• New Protection Systems: Add support for additional bot detection services
• Browser Engines: Implement support for new automation frameworks (e.g. Selenium-based)
• Analysis Tools: Enhance reporting and visualization

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

⚠️ Disclaimer

This tool is designed for educational and research purposes. Users are responsible for ensuring compliance with website terms of service and applicable laws. The authors and contributors do not encourage or endorse any malicious use of this software.