H2 heading over 70 characters
What it is
One or more <h2> headings on the page are longer than 70 characters. H2s label the sections of a page, and a short label is quicker to scan than a full sentence. Long H2s often pack in a keyword list, a sub-point or the first line of the section itself.
Why it matters
Readers skim section headings to decide where to stop, and screen reader users hear them as a list when they navigate by heading , so a long one slows both. Neither HTML nor Google sets a limit on heading length, and a question used as a heading on a FAQ page can reasonably run longer, so the cost is mostly readability.
How Asky checks it
Asky reads every <h2> in the page’s raw HTML (headings added by JavaScript are not seen), takes each one’s text including nested elements, trims whitespace at both ends and counts the characters. Any H2 over 70 characters is a hit, but the page is reported once, and the finding shows the last long H2 in source order; the others are not listed, so check them all. Seventy is a rule of thumb for a heading that scans at a glance, not a limit set by search engines or HTML. H2s in headers, footers and hidden elements count too.
Reported as an opportunity with low severity.
How to fix it
- Search the page source for every
<h2>, since the finding names only one of the long headings. - Shorten each to its core label and move the detail into the first sentence of the section.
- Aim for 70 characters or fewer.
- To leave it as it is: if the long H2s are questions on a FAQ page, phrased the way people ask them, mark the issue resolved.
Example
On https://example.com/help/domains a 94-character question becomes a 42-character one, with the detail in the text:
<!-- Before: 94 characters -->
<h2>How long does it take to move an existing Webflow site to a new domain without losing traffic?</h2>
<!-- After: 42 characters -->
<h2>How long does a move to a new domain take?</h2>
<p>For an existing Webflow site, plan for ...</p>