A few dozen findings, most of them small: a page with barely any text on it, a link whose text is just "here", a page whose title tag is a copy of its H1, a hero image heavy enough to hurt the largest contentful paint. Then a few months pass, a dozen new pages ship, and the next audit reports the same findings again.
A few dozen findings, most of them small: a page with barely any text on it, a link whose text is just "here", a page whose title tag is a copy of its H1, a hero image heavy enough to hurt the largest...
Then a few months pass, a dozen new pages ship, and the next audit reports the same findings again.
Not because anyone ignored the first round, but because the first round fixed pages instead of fixing the process that produces pages.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
A few dozen findings, most of them small: a page with barely any text on it, a link whose text is just "here", a page whose title tag is a copy of its H1, a hero image heavy enough to hurt the largest contentful paint. Then a few months pass, a dozen new pages ship, and the next audit reports the same findings again. Not because anyone ignored the first round, but because the first round fixed pages instead of fixing the process that produces pages.
Originally appeared on The Rails Tech Debt Blog. You get a site audit report and it looks manageable. You spend an afternoon on it, close the tickets, and move on.
Open the app view to save this story, compare related coverage, and continue from the same source.