Video for 23 tire pages
A rough hosting budget using the current N’Fera Sport clips. It assumes the other tire pages have similar videos.
A rough Cloudflare Stream budget for 100,000 tire-page visits a month across the whole site, with 30 seconds to two minutes of video delivered per visit. It is a planning estimate, not a quote.
The assumptions behind the number
The 23-page count is approximate. The traffic and viewing time below are examples, not measured use.
Visits are counted across all pages combined. One page visit can start several clips.
See the file sizes and the delivery math
What we actually have on hand: the real N’Fera Sport set is 13 clips across 26 files. In WebM the total is 13.13 MB; in the alternative MP4 the total is 37.72 MB. A browser normally uses just one of these formats, not both.
If all 23 pages are similar, storing both formats for every page comes to about 1.17 GB of storage.
If 100,000 visits each load every clip once, the amount delivered is roughly 1.3–3.8 TB. Services that charge by data use this file-size estimate. Cloudflare Stream charges by delivered minutes instead.
Three services, compared plainly
The prices cover different amounts of work.
Includes preparing video quality options and a player. The example includes one $5 storage block, which holds up to 1,000 minutes of video.
The exact figure depends on how much is stored and delivered.
Official pricingIncludes a player, video preparation, and 1 TB of viewing data each month. Higher use needs a quote.
$948 for a year before extras.
Official pricingMay cover delivery for this example. Preparing the video versions and maintaining the player are separate work. Check the request limit before choosing it.
Official pricingTry the video difference
Play the same clip two ways. Streaming can choose a smaller picture on a slow connection. These two homepage samples test playback formats; the tire cost estimate above uses the tire files.
Choose “Play original” or “Play stream.”
Your playback numbers
Start time: — Waiting events: — Picture: —
A waiting event means the browser needed more video data. Several events can happen during one visible pause.
What we actually saw in the tests
In every pair, the original file started sooner. The stream started later.
For the longer clip, the original recorded 22–23 waiting events. The stream had zero at its smaller 360p picture size, but started later. These are browser events, not a count of separate long pauses.
Both were smooth.
The useful result was smoother playback on the slow connection, with a smaller picture. These were 16 Chrome lab runs. Replaying here may use saved browser data, so it may feel faster.
Three things to settle next
- Confirm the page count and the traffic. The 23-page figure and the 100,000 visits are working assumptions. Actual use will narrow the estimate.
- Choose autoplay and mobile behavior. Decide whether video should start on its own, and how it should behave on phones. This affects both cost and experience.
- Choose preview images and captions. Decide who supplies the still image shown before playback and captions for any speech.