DraftKings Proxies: 647 Words, Never Render

DraftKings is the sportsbook where the headless browser is pure waste. On 28 September 2026 we fetched sportsbook.draftkings.com through residential exits in the United States and Canada. The home page hands a plain HTTP client 647 words; rendering the same URL costs 2,877,467 bytes and 35 seconds and returns 642. The NFL odds page answers plain HTTP with 2,365,082 bytes and 5,418 words of lines, spreads and totals. A Canadian exit gets a different book, 697 words on the home page and 5,611 on NFL. And before any of that: DraftKings' terms allow one account per person, and no proxy changes it.

Never render DraftKings: the browser returns fewer words

Every other target in this series has a render that adds something, even when it does not pay. DraftKings is the case where it subtracts. Our audit earlier this month counted 647 words without JavaScript and 642 rendered; the re-check on 28 September counted 640 without JavaScript. The rendered response is the application shell hydrating in front of the same server-rendered SEO block, and it arrives at 1.8 times the bytes.

Fetch	Exit	Status	Bytes	Words	Time
Home, no JavaScript	United States	200	1,581,100	647 (640 on re-check)	52 s under load
Home, rendered	United States	200	2,877,467	642	34.8 s
Home, no JavaScript	Canada	200	n/a	697	8 s
NFL odds page, no JavaScript	United States	200	2,365,082	5,418	6.6 s
NFL odds page, no JavaScript	Canada	200	2,382,690	5,611	8.1 s

Three details in the head matter for a monitor. There is no canonical on the home page, from either country and in either mode, so deduplicate on the final URL yourself. The JSON-LD is a single WebSite object with no odds in it. And the Open Graph title is "Featured Betting Odds & Lines", which is the page's own description of what it is: a landing page, not the book. The home page is worth one fetch to confirm the site is up. The data is elsewhere.

The odds are in the HTML of the league pages

The page a line-movement monitor wants is a league page, and it answers plain HTTP. /leagues/football/nfl returned 2,365,082 bytes, a self-referencing canonical, 48 headings, two tables and 5,418 words from a US residential exit in 6.6 seconds: every game on the board with spread, moneyline and total. No browser, no login, no cookie. The bytes are heavy because DraftKings ships the whole application with the page, but the odds are server-rendered inside it, and the raw HTML is what the fetch returns.

The size decides the product. At 2.37 MB a page, one fetch per minute for a day is 3.4 GB, and the same page through the web scraping API without rendering is a flat $0.0002 regardless of weight. That is the cost table below in one sentence: on DraftKings the per-page product is nine times cheaper than the bytes.

Canada is a different sportsbook

DraftKings runs a separate book for Ontario, and the exit IP selects it. The home page audited through a Canadian residential exit returned 697 words against 640 from the US; the NFL page returned 5,611 words and 2,382,690 bytes against 5,418 and 2,365,082. Those are different markets and, in places, different prices. The rule follows: pin the exit to the market whose lines you are recording, and never compare a Canadian snapshot against an American one. We measured at country level only; DraftKings also licenses state by state inside the US, and a state-targeted residential exit is the precise instrument for that, as our bet365 measurement showed for the UK against Germany, where the same URL returned 987 words from one and 149 from the other.

One account per person: the line from DraftKings' own terms

The Terms of Use for DraftKings Sportsbook, last updated 08/05/2024 and organised by section heading rather than by clause number, say under Eligibility:

You may establish only one (1) Account per person to participate in the Services offered on the Website. In the event DraftKings discovers that you have opened more than one Account per person, in addition to any other rights that DraftKings may have, DraftKings reserves the right to suspend or terminate any or all of your Accounts and terminate, withhold or revoke the awarding of any winnings and prizes.

The same section, at item (f), bars "placing a wager as an agent of or proxy for any person or entity" who is not allowed to bet. That is the sense in which the search results use the word: in March 2022, New Jersey regulators fined DraftKings $150,000 for allowing a Florida man to bet from home through a friend in New Jersey, and the settlement voided 21 pending bets. And under Conditions of Participation the terms list, as improper conduct, "using automated means (including without limitation harvesting bots, robots, parser, spiders or screen scrapers) to obtain, collect or access any information on the Website or of any other user for any purpose".

The terms allow one account per person, forbid betting for someone else, forbid location spoofing by implication of the physical-location requirement, and forbid automated collection from the site; nothing in this post helps with any of it. What is left is narrow and honest: knowing what the site serves a logged-out client, so that anyone with a legitimate reason to look at public odds pages, from a compliance team to a researcher, does not pay for a browser that returns less.

robots.txt is 73 bytes

The whole file is three rules: Disallow: *wpsrc=*, Disallow: /update-app$ and Disallow: *referrer*. It disallows tracking parameters and an app-update route, and says nothing about league pages. That is common on sites whose real policy is in the contract, and it is why the previous section, not this one, is the constraint.

Cost math with real numbers

Prices from our pricing page: residential proxies from $0.80/GB on the Basic line, and the web scraping API from $0.0002 per page, $0.001 with rendering, billed only on success. A gigabyte is counted as 10^9 bytes.

Job	Bytes per request	Requests per GB	Cost per request	What you get
Home, no JavaScript, residential	1,581,100	632	$0.00126	647 words, no odds
Home, rendered, residential	2,877,467	347	$0.00230	642 words: less, for more
NFL page, no JavaScript, residential, US	2,365,082	423	$0.00189	5,418 words of lines
NFL page, no JavaScript, residential, Canada	2,382,690	420	$0.00191	5,611 words of Ontario lines
NFL page, web scraping API, no render	n/a	n/a	$0.0002	The same page, parsed, billed only on success

One snapshot of the NFL board per minute costs $2.72 a day in residential bandwidth and $0.29 a day through the API. The rendered home page is the row to remember: $0.0023 for 642 words when $0.00126 buys 647. Telling you to skip the browser saves a third of the bytes on every home fetch and all of the render time, and it is the reason to believe the rest of this table.

The setting that works on DraftKings

• Network: residential, Basic line at $0.80/GB. Sportsbooks score the network; every number here came through residential exits, and nothing challenged them in eight fetches.
• Fetch mode: engine: tls, plain HTTP, always. The home page returns 647 words without JavaScript and 642 with it for 2,877,467 bytes; the NFL page returns 5,418 words of odds without JavaScript. Never render this site.
• Country to pin: country=us for the US book. A Canadian exit returns a different sportsbook: 697 words on the home page and 5,611 on NFL instead of 640 and 5,418.
• When the proxy is not enough: the pages are 2.4 MB each, so send them through the web scraping API without rendering at $0.0002 per page, nine times cheaper than the bytes. There is no DraftKings collector in our catalogue and, given the terms, we are not building one.
• Free tier: every account gets $2 of free API usage per month, which is 10,000 league-page fetches through the API.