Clean Clipper Add to Chrome (free)

Measurement

What was measured, on what, and what came out

Claims about clean output are worth nothing without a corpus and a script. Both are published.

Run one: 109 pages, four engines

The corpus is the hundred most-visited sites in the world and the hundred most-visited in Russia. Non-content domains (messengers, banking, streaming, government portals) were excluded in advance. Pages were captured with a real browser, resolving a content link from each home page where one existed.

Four engines ran over the same captured DOM: Defuddle (the core of the official Obsidian clipper), Mozilla Readability, the real shipped code of a third Markdown clipper unpacked from its store build, and Clean Clipper.

MetricEngine AEngine BEngine CClean Clipper
Pages109107107109
Failures0220
Leftover HTML53271820
Duplicated menu lines491282478102
Short-line ratio0.2780.2620.2630.220

Where Clean Clipper is behind: it found 20 authors against 28 for the best engine, and extracted 4 tables against 11, though 41 of the 56 source tables sit on a single page and are layout, not content, which no engine should extract. Its share of “useful text” is lower because it refuses feed pages that other engines happily return.

Run two: 403 pages in twelve European languages

The top fifty sites in each of twelve countries, captured with the browser set to that country’s language, because otherwise half of them serve an English page and the measurement is of something else.

LanguagePagesFailuresLeftover HTMLLink share
German40000.058
French39000.050
Spanish40000.060
Italian40000.036
Polish30000.064
Portuguese36000.060
Dutch37000.049
Turkish31000.042
Ukrainian13000.054
Czech28000.039
Swedish28000.036
Romanian41000.039

What the numbers mean

Honest limits of this measurement

Questions

Can I reproduce this?
Yes. The corpus lists, the capture script and the scoring script are in the repository. The capture depends on live sites, so exact numbers will drift as those sites change.
Why are the competing engines not named here?
Naming competitors in store listings is against Chrome Web Store policy, and the same restraint is applied on this site. The repository names them, because there the claim can be checked.
Is more extracted text better?
Not on its own. An engine that returns a feed page full of links scores well on volume and badly on usefulness. That is why the tables above measure noise rather than size.