Two people can look at the exact same five cities and walk away with opposite favorites, and both can be right. A ranking built around affordability crowns a different winner than one built around safety or a short commute. The underlying numbers don't change — what changes is which number you decided to care about first.
Here's a framework for making that decision on purpose, instead of by accident.
Start with deal-breakers, not preferences
Before you weight anything, filter. A deal-breaker is a yes/no gate: a city either clears it or it's off the list, no matter how well it scores everywhere else.
Common deal-breakers:
- Budget ceiling. A hard number for home price or rent, not "affordable." If a $600,000 home value is out of reach, it doesn't matter that the city scores well on everything else.
- Climate tolerance. No amount of walkability fixes a place you'd resent every February or every July. Pull actual 30-year climate normals instead of trusting a tagline about sunshine.
- Proximity to family. A flight-hours or drive-hours limit, if aging parents, co-parenting, or caregiving is part of the calculation.
- Job market for your field. A city's overall economy can look strong while your specific occupation has almost no local demand — check BLS occupational employment data for your field in that metro before you assume.
Run every candidate through your deal-breakers before you look at a single score. A city that fails a deal-breaker doesn't get partial credit for scoring well elsewhere — that's the point of a gate instead of a weight.
Meet five cities, and one score each
Once a shortlist survives your deal-breakers, the real comparison starts. Here are five real cities from WhereAtHome's data, each with a different profile:
| City | WhereAtHome Score | Median home value | Median income | Cost-of-living index |
|---|---|---|---|---|
| El Paso, TX | 65.0 | $238K | $50K | 85 |
| Naperville, IL | 59.5 | $629K | $151K | 112 |
| Pittsburgh, PA | 58.4 | $241K | $54K | 91 |
| Denver, CO | 48.5 | $533K | $86K | 128 |
| Austin, TX | 47.1 | $504K | $91K | 129 |
Sorted by the default score, El Paso comes out on top and Austin comes in last.
But the default score blends six components at fixed weights — Housing Affordability and Income vs Housing at 20% each, Crime at 20%, Commute at 15%, Walkability at 15%, and Purchasing Power at 10%, all spelled out on the methodology page. Change what you're optimizing for, and this order stops being the only honest answer.
When safety is what you actually care about
WhereAtHome's crime component uses seven tiers, from Very Low down to Very High, each mapped to a fixed safety score: Very Low scores 95, Low scores 80, Moderate-Low 65, Moderate 50, Moderate-High 35, High 20, Very High 10.
Naperville's crime tier is Very Low — a safety score of 95. Austin's is Moderate — a safety score of 50. In the blended default score, Naperville's expensive housing drags its total down to 59.5, only just ahead of Austin's 47.1.
But if safety is the criterion that actually keeps you up at night, the real gap between these two cities is 95 versus 50 — nearly double — and no blended number captures that as clearly as looking at the component directly.
When walkability is what you actually care about
Run the same test on walkability, and the order flips somewhere you might not expect. Pittsburgh's Walk Score is 62. Naperville — the city with the better default score — has a Walk Score of just 46.
If your priority is running errands without a car, Pittsburgh wins outright, despite trailing Naperville on the composite.
Neither result is wrong. They're answers to different questions, using the same source data.
Use the sort tool instead of doing this by hand
You don't need to recompute weighted averages yourself. On the rankings page, you can sort by any individual component — try sorting by crime instead of relying on the blended default.
The compare page puts two cities side by side with every component visible, which is the fastest way to check whether a lead survives a change in what you're weighting.
Build your own weighted worksheet
For your own shortlist, assign every criterion a weight that sums to 100, rate each city 1–5 on that criterion, and multiply.
| Criterion | Weight | City A rating (1–5) | City B rating (1–5) | City C rating (1–5) |
|---|---|---|---|---|
| Housing affordability | ___ | ___ | ___ | ___ |
| Safety | ___ | ___ | ___ | ___ |
| Commute | ___ | ___ | ___ | ___ |
| Walkability | ___ | ___ | ___ | ___ |
| Job market fit | ___ | ___ | ___ | ___ |
| Weighted total | 100 | ___ | ___ | ___ |
Weighted total per city equals the sum of (weight × rating) divided by 100. Run it once with your honest weights, then run it again after bumping your top priority up by 20 points.
If the winner doesn't change, you have a robust answer. If it does, that's exactly the information you needed — the decision hinges on that one priority, so spend your remaining research time verifying it in person rather than adding more spreadsheet rows.
Here's the math with real numbers. Say a household weights housing affordability at 40, safety at 30, commute at 20, and walkability at 10 — summing to 100 — then rates El Paso and Pittsburgh 1–5 on each using the data above plus a little local research. El Paso might earn a 5 on housing (its $238K median is the cheapest of the five cities here) and a 4 on safety (a Low crime tier), for a subtotal of 40×5 + 30×4 = 320 on those two criteria alone.
Pittsburgh might earn a 4 on housing and a 3 on safety — 40×4 + 30×3 = 250 — but pulls most of that back on walkability, where its Walk Score of 62 beats El Paso's 40 by a wide margin. Add commute the same way, divide the running total by 100, and the two cities can land close enough that the household's actual walkability need decides it — not the 18-point gap in the headline WhereAtHome Score that made El Paso look like the clear winner before any personal weighting happened.
The takeaway
A single ranking answers "what does a fixed formula think, on average." Your move isn't average. Filter hard on deal-breakers first, then decide deliberately what you're weighting before you look at who wins — and use the component breakdown, not just the headline score, to check whether the answer actually matches what you said you cared about.
