Performance metrics help us see how fast a web page loads and works. Using DevTools lets us check these numbers automatically in tests.
Performance metrics via DevTools in Selenium Java
DevTools devTools = ((HasDevTools) driver).getDevTools(); devTools.createSession(); // Enable performance monitoring devTools.send(Performance.enable(Optional.empty())); // Get performance metrics List<Metric> metrics = devTools.send(Performance.getMetrics());
You need Selenium 4+ and a browser that supports DevTools (like Chrome).
Performance metrics include things like page load time and CPU usage.
DevTools devTools = ((HasDevTools) driver).getDevTools(); devTools.createSession(); devTools.send(Performance.enable(Optional.empty())); List<Metric> metrics = devTools.send(Performance.getMetrics()); for (Metric metric : metrics) { System.out.println(metric.getName() + ": " + metric.getValue()); }
DevTools devTools = ((HasDevTools) driver).getDevTools(); devTools.createSession(); devTools.send(Performance.enable(Optional.empty())); List<Metric> metrics = devTools.send(Performance.getMetrics()); // Find and print only the "TaskDuration" metric metrics.stream() .filter(m -> m.getName().equals("TaskDuration")) .forEach(m -> System.out.println("TaskDuration: " + m.getValue()));
This test opens a Chrome browser, starts DevTools performance monitoring, loads example.com, then prints performance metrics like page load times.
import org.openqa.selenium.WebDriver; import org.openqa.selenium.chrome.ChromeDriver; import org.openqa.selenium.devtools.DevTools; import org.openqa.selenium.devtools.v114.performance.Performance; import org.openqa.selenium.devtools.v114.performance.model.Metric; import java.util.List; import java.util.Optional; public class PerformanceMetricsTest { public static void main(String[] args) { System.setProperty("webdriver.chrome.driver", "path/to/chromedriver"); WebDriver driver = new ChromeDriver(); DevTools devTools = ((ChromeDriver) driver).getDevTools(); devTools.createSession(); // Enable performance monitoring devTools.send(Performance.enable(Optional.empty())); driver.get("https://example.com"); // Get performance metrics List<Metric> metrics = devTools.send(Performance.getMetrics()); // Print all metrics for (Metric metric : metrics) { System.out.println(metric.getName() + ": " + metric.getValue()); } driver.quit(); } }
Make sure to use the correct ChromeDriver version matching your Chrome browser.
Performance metrics names and values may vary by browser version.
Always quit the driver to close the browser and free resources.
DevTools lets Selenium get performance data from the browser.
Enable performance monitoring before loading the page.
Use metrics to understand and improve page speed.
Practice
Solution
Step 1: Understand DevTools role in Selenium
DevTools integration allows Selenium to collect browser performance data like load times.Step 2: Identify the purpose of performance metrics
Performance metrics help measure page speed and resource usage to improve user experience.Final Answer:
To measure page load speed and browser performance -> Option DQuick Check:
Performance metrics = page speed measurement [OK]
- Confusing performance metrics with element locators
- Thinking DevTools handles alerts
- Assuming screenshots are related to performance
Solution
Step 1: Identify the correct DevTools command for performance
The Performance domain in DevTools is enabled by calling Performance.enable().Step 2: Check other options for correctness
devTools.send(Network.enable(Optional.empty(), Optional.empty(), Optional.empty())); enables Network, not Performance. driver.manage().timeouts().pageLoadTimeout(Duration.ofSeconds(10)); sets timeout, and B loads a page.Final Answer:
devTools.send(Performance.enable()); -> Option AQuick Check:
Enable performance with Performance.enable() [OK]
- Using Network.enable() instead of Performance.enable()
- Confusing timeout settings with performance enabling
- Calling driver.get() instead of enabling metrics
metrics.getMetrics()?
DevTools devTools = driver.getDevTools(); devTools.createSession(); devTools.send(Performance.enable()); PerformanceMetrics metrics = devTools.send(Performance.getMetrics()); System.out.println(metrics.getMetrics().get(0).getName());
Solution
Step 1: Understand Performance.getMetrics() return type
It returns a PerformanceMetrics object containing a list of Metric objects, each with a name and value.Step 2: Analyze metrics.getMetrics().get(0).getName()
This accesses the first Metric's name, which is a String describing the metric.Final Answer:
A String representing the name of the first performance metric -> Option CQuick Check:
getName() returns String metric name [OK]
- Assuming getName() returns a number
- Confusing metrics with WebElements
- Expecting a boolean from getMetrics()
DevTools devTools = driver.getDevTools(); devTools.send(Performance.enable()); devTools.createSession();
Solution
Step 1: Check the order of DevTools commands
Session must be created before sending any DevTools commands like Performance.enable().Step 2: Verify method usage
Calling Performance.enable() before createSession() causes an error because no session exists yet.Final Answer:
createSession() must be called before sending commands -> Option BQuick Check:
Call createSession() first, then enable performance [OK]
- Calling enable() before createSession()
- Thinking Performance.enable() needs parameters
- Assuming DevTools is unsupported in ChromeDriver
Solution
Step 1: Enable performance monitoring before page load
Performance must be enabled before loading the page to capture all metrics during load.Step 2: Load the page and then retrieve metrics filtering for 'DomContentLoaded'
After page load, get metrics and select the 'DomContentLoaded' metric to measure load time.Final Answer:
Enable performance, load page, then get metrics and filter for 'DomContentLoaded' -> Option AQuick Check:
Enable first, load page, then get metrics [OK]
- Enabling performance after page load misses metrics
- Getting metrics before loading page
- Relying only on timeout settings for load time
Ready to prove it?
Pass the test and this pattern moves unknown
