Practical guide · Search topic: compare website traffic over time
How to compare website traffic over time fairly
A useful traffic comparison holds the measurement method steady. Compare equal-length periods with similar weekdays, and check holidays, promotions, outages, launches and tracker changes before interpreting a difference.
What the query can—and cannot—measure
Choose the metric that fits the decision: pageviews for consumption, sessions for visits or a defined conversion for outcomes. Use the same timezone, source rules and visitor definition. If imported historical data uses different rules, mark its start and do not treat it as perfectly continuous.
A practical way to do it
Record the date range, comparison range, filters and any known changes with each review. Show absolute counts as well as percentage changes, especially when the baseline is small.
A useful checklist
- Match period length and weekdays.
- Keep metric definitions and filters consistent.
- Annotate campaigns, outages and tracking changes.
Limits to keep in mind
A comparison describes observed difference, not its cause. Small baselines create large percentage swings.
Questions
Should I compare month over month or year over year?
Choose the range that controls for the seasonality relevant to your business.
Why do historical imports differ?
Import mappings and source-tool definitions may not match current tracking.
Sources and further reading
Related pages
Compare any two date ranges · quietstats cookie-free analytics Trend charts, headline cards and any date range · quietstats cookie-free analytics Import from Plausible or GA4 · quietstats cookie-free analytics
Put your traffic in context
Explore the product, its measurement method and pricing before choosing a tool.