The two options
Measured loading, interactivity and layout stability — a real but modest ranking input, and a large conversion input.
- You already rank in the top ten for target terms
- Mobile scores are failing while competitors pass
- Conversion rate drops sharply on slower connections
Coverage of the sub-questions a query implies, with enough substance to be the last page a reader needs.
- You sit on page two or lower for target terms
- Competing pages answer questions yours never raises
- Your page is shorter than every result above it for a reason you cannot defend
How they differ
| Core Web Vitals | Content depth | |
|---|---|---|
| Ranking weight | Small — a tiebreaker | Large — a qualifier |
| Helps at position | Four to eight | Eleven and below |
| Also affects | Conversion rate, materially | Answer selection and AI citation |
| Who delivers it | Engineering | Content and subject experts |
| Time to signal | Two to six weeks | Two to five months |
What actually decides it
The most common misallocation in this pair is a team spending a quarter on performance engineering while ranking eleventh. Speed does not move a page from eleventh to fifth, because the gap at that distance is relevance rather than milliseconds. The engineering is not wasted — it helps conversion — but it does not fix the stated problem.
There is a version of this where speed genuinely is the constraint. Two comparable pages, similar depth, similar authority, and one loads in one second while the other takes four. That contest is real, and it is decided partly on experience signals and heavily on the readers who abandon before the slow page renders.
Depth has a second payoff that speed does not. Answer engines and generative engines both select at passage level, so a page covering the sub-questions of a query becomes eligible for surfaces a fast, thin page never reaches. Depth compounds across three disciplines; speed compounds within one.
Questions
Does Google still use Core Web Vitals?
Yes, as part of page experience, and its weight is modest and openly described as a tiebreaker. It matters where competing pages are otherwise comparable, and much less where a relevance gap exists.
Is longer content always deeper?
No, and padding is its own penalty. Depth means covering the sub-questions a query implies, not word count. A tight page that answers everything beats a long one that circles the topic without resolving it.
What if both are bad?
Fix depth first for ranking and speed first for conversion, and pick based on whether your problem is traffic or revenue. If pages fail Core Web Vitals badly enough to affect usability, that is a business issue regardless of rankings.
Related services
- Core Web Vitals — SEO
- Topical Authority — SEO
- Technical SEO Audit — SEO
- On-Page SEO — SEO
Still not sure?
Thirty minutes with a senior strategist. We pull your live visibility while we talk and tell you which of these two is actually binding for you — including when the answer is neither. Book a discovery call →