Web & development
Interactive tools with transparent methods. Change the inputs, check the example and use the result with its assumptions.
Page View Revenue Calculator
Page views equal visits multiplied by pages per visit. Estimated revenue equals those page views divided by 1,000, multiplied by page RPM.
Cache Origin Savings Calculator
Expected origin requests equal total requests multiplied by one minus the cache-hit fraction. At 80% hits, 100,000 requests leave 20,000 expected origin fetches.
Uptime Downtime Budget Calculator
Allowed downtime equals the monitoring window multiplied by one minus the uptime target. A 99.9% target over 30 days allows 43.2 minutes in this time-based model.
Observed Uptime Calculator
Observed uptime equals monitored time minus downtime, divided by monitored time, multiplied by 100. Use downtime measured within the same monitoring window.
Requests Per Second Calculator
Average RPS equals request count divided by elapsed seconds. A total of 180,000 requests in one hour averages 50 requests per second.
Average Request Concurrency Calculator
Average concurrency equals requests per second multiplied by mean duration in seconds. At 80 RPS and 250 milliseconds per request, the average is 20 in-flight requests.
Request Transfer Volume Calculator
Estimated transfer bytes equal request count multiplied by average response size. Two million responses averaging 20 decimal KB contain 40 GB of payload.
Compression Savings Calculator
Space saving is original bytes minus compressed bytes. Saving percentage divides that difference by the original size; compression ratio divides original size by compressed size.
Request cache-hit rate vs byte cache-hit rate
Request hit rate weights each request equally; byte hit rate weights the response-body bytes. If 99 small 1 KB responses hit cache and one 1,000 KB response misses, request hit rate is 99% but byte hit rate is only 9.01%.
Compression ratio vs percentage saved
Using the original-to-compressed convention, compression ratio is original bytes divided by compressed bytes. Reducing 100 KB to 25 KB gives 4:1 compression and 75% byte savings, not 400% savings.
HTTP status codes for website checks and integrations
The status code describes the result of an HTTP request. A friendly error page that returns 200 is different from a real 404. Read the code, method and response headers together when testing a website or API.
Cache-Control directives: storage and reuse are different
no-cache permits storage but requires successful validation before reuse. no-store instructs caches not to store the response. max-age sets a freshness lifetime; it is not a guarantee that a cache will retain the object for that long.
Base64 encoded-size table with padding
Standard padded Base64 needs 4 × ceiling(original bytes ÷ 3) characters, excluding line breaks. Three input bytes become four encoded characters; very small inputs can have a larger percentage overhead because of padding.
Uptime percentages and monthly downtime budgets
Translate an uptime target into allowed downtime over exactly 30 days. A 99.9% target permits 43.2 minutes in this fixed period.
Requests per second, minute and day: conversion table
Multiply a steady requests-per-second rate by 60 for a minute or 86,400 for a day. This table compares equivalent sustained rates.
Image resolution and uncompressed RGBA memory table
An 8-bit RGBA pixel uses four bytes before row padding and other overhead. Multiply width by height by four to estimate a single uncompressed pixel buffer.