Guide
Metros with Strong Cost and Wage Scores
The verdict
Paducah, KY-IL tops the list, but 6 of PlainCompare's 387 tracked metros clear the top-third bar on both cost and wages at once.
- 6
- metros in the dual sweet spot
- 94
- Paducah, KY-IL cost score
- 40
- Paducah, KY-IL wages score
- 387
- metros scored fleet-wide
Cost score vs. wages score
A purchasing-power shortlist from PlainCompare's 387-metro field, not a Census/BLS growth ranking.
Every score below is recomputed from life_scores on this site's database.
Key Takeaway
6 metros currently clear the dual top-third bar on cost and wages. That screen answers "where does pay go further without collapsing wages," which is the question our data can support. It does not answer "which metros grew fastest since 2015" - we do not store that time series here.
What this page measures (and what it does not)
PlainCompare combines BEA Regional Price Parities, BLS wage fields, FBI crime rates, and related federal snapshots into per-metro scores. Higher cost scores mean more affordable living relative to the national field; higher wage scores mean stronger pay.
- In scope: current composite grade, cost score, wages score, crime score from the live database.
- Out of scope: cumulative 2015–2023 population, employment, or income growth percentages. Those require historical series we do not carry.
The URL slug still says "fastest-growing" for continuity with older links; the headline and table match the data we actually publish. For the comparison framework, see How to Compare Cities with Data.
Cost-and-wages sweet-spot metros
Rows below are the top composite metros (the dual threshold was thin in this refresh); cost and wage scores are still shown so you can apply your own cut.
| # | Metro | Grade | Composite | Cost | Wages | Crime |
|---|---|---|---|---|---|---|
| 1 | Paducah, KY-IL | A+ | 73 | 94 | 40 | 85 |
| 2 | Pocatello, ID | A+ | 68 | 81 | 21 | 82 |
| 3 | Wildwood-The Villages, FL | A+ | 67 | 98 | 47 | 91 |
| 4 | Huntington-Ashland, WV-KY-OH | A+ | 66 | 84 | 41 | 79 |
| 5 | St. Cloud, MN | A+ | 66 | 90 | 83 | 71 |
| 6 | Ames, IA | A+ | 66 | 82 | 54 | 81 |
| 7 | Charleston, WV | A+ | 65 | 82 | 36 | 79 |
| 8 | Lexington-Fayette, KY | A+ | 65 | 55 | 70 | 86 |
| 9 | Elizabethtown, KY | A+ | 65 | 72 | 27 | 86 |
| 10 | Sioux Falls, SD-MN | A+ | 65 | 72 | 48 | 54 |
| 11 | Monroe, LA | A+ | 65 | 100 | 3 | 29 |
| 12 | Owensboro, KY | A | 65 | 83 | 23 | 85 |
| 13 | Cedar Rapids, IA | A | 64 | 81 | 44 | 81 |
| 14 | Lafayette, LA | A | 64 | 91 | 10 | 30 |
| 15 | Lewiston, ID-WA | A | 64 | 68 | 21 | 82 |
Scores are 0–100 field ranks inside PlainCompare's metro set (vintage 2026-08-29). Open a metro page for the full dimension stack before treating any row as a relocation answer.
How to read the sweet spot
- High cost + high wages: pay goes further and the wage field is strong, the intended shortlist.
- High cost + low wages: affordable on paper, but the local pay field is weak; remote workers sometimes still win here, payroll workers often do not.
- Low cost + high wages: expensive metros with strong pay, fine if your occupation clears the bar; check the occupation wage page, not only the composite.
Browse all metros or start from rankings if you want a different axis (crime, schools, rent) as the primary sort.
If you specifically need growth rates
Use the Census Bureau's metro population estimates, BLS QCEW employment levels, and BEA personal income by metro, each agency publishes the series with its own vintage and geography definitions. Cite those releases directly. Do not treat any older PlainCompare growth table as authoritative; it was removed because it was not database-backed.
"A score we can recompute beats a growth percentage we cannot source."
What to do with this
Use the sweet spot as a shortlist filter, not a verdict.
- Open the full dimension stack for a shortlisted metro before deciding, 6 metros clearing this screen still differ a lot on rent, schools, and crime. Browse all metros
- Weight cost and wages against your own priorities, not this page's equal-thirds cut. Compare framework
- Need an actual growth rate? This database does not carry one, cite the Census/BLS/BEA release directly instead.
Cost and wages scores are recomputed from life_scores (vintage 2026-08-29); the dual sweet-spot threshold is ≥66.7 on both axes.
Frequently asked questions
Does PlainCompare publish multi-year population or job growth rates?
No. Our metro database scores 387 metros on current federal snapshots (BEA cost, BLS wages, FBI crime, and related axes), not a 2015–2023 growth time series. Pages that need growth rates should cite Census/BLS/BEA releases directly; we will not invent cumulative percentages.
What is the "cost and wages sweet spot"?
A metro in the top third on cost affordability (score ≥66.7) and the top third on wages (score ≥66.7) at the same time. That is a purchasing-power screen, not a population-growth claim.
Why did this page used to show growth percentages?
An earlier version hard-coded a growth table that was not produced from our database. That violated our data-integrity rule (every published figure must be DB-derived or named-source attributed). The invented table is gone; the URL now shows scores we can recompute from life_scores.
How should I use this list for a move?
Treat it as a shortlist filter, then open each metro page for the full dimension stack (rent, schools, childcare, environment). Pair it with the how-to-compare guide so your own priorities, not a single composite, decide the move.
Source: PlainCompare life_scores (BEA + BLS + FBI UCR + peer federal snapshots) Metro cost / wages / crime / composite field · 2026 Table rows are SELECT…FROM life_scores WHERE type='metro' ordered by composite_score; dual threshold cost≥66.7 and wages≥66.7 when that set is large enough. No multi-year growth columns exist in this database.