<?xml version="1.0" encoding="UTF-8"?>
<response><data><post><id>18</id><slug>headless-vs-headed-browsers-18</slug><title>Headless vs headed browsers</title><excerpt>Running a browser without a window is faster and works on servers, but some problems are much easier to understand when you can watch the browser do its work.</excerpt><seriesName>Headless vs headed browsers</seriesName><seriesPart>1</seriesPart><sections><item><heading>Introduction</heading><paragraphs><item>Running a browser without a window is faster and works on servers, but some problems are much easier to understand when you can watch the browser do its work.</item></paragraphs></item><item><heading>Going further</heading><paragraphs><item>Time zones matter more than they seem. Store timestamps in UTC and convert only when displaying them.</item><item>Be careful with relative URLs. Resolve every link against the page it came from, not against the site root, or you will request pages that do not exist.</item></paragraphs></item><item><heading>Putting it into practice</heading><paragraphs><item>Dynamic pages render content after the initial HTML arrives. A browser automation tool can wait for a specific element to appear, which is far more reliable than sleeping for a fixed amount of time.</item><item>Always identify your client honestly with a descriptive User-Agent, and keep your request rate modest. A crawler that behaves like a considerate visitor is far less likely to cause problems for the site operator.</item></paragraphs></item><item><heading>Key takeaway</heading><paragraphs><item>Develop headed with slow motion turned on, run headless in CI, and capture screenshots or traces on failure so headless runs are still debuggable.</item></paragraphs></item></sections><authorId>4</authorId><authorName>Lucas Silva</authorName><authorSlug>lucas-silva</authorSlug><category>Browser Automation</category><tags><item>selenium</item><item>playwright</item><item>http</item></tags><publishedAt>2025-06-13T00:00:00.000Z</publishedAt><wordCount>166</wordCount><readingTimeMinutes>2</readingTimeMinutes></post></data></response>
