Question 1

How accurate is read-art compared to other readability libraries?

Accepted Answer

read-art achieves about 90% accuracy out-of-the-box, similar to Arc90's algorithm, but may require tuning for optimal results. Alternatives like Mercury Parser might offer better default accuracy for English, but read-art excels in performance and Chinese support.

Question 2

How to improve extraction accuracy for a specific website?

Accepted Answer

You can define custom score rules or CSS selectors in the configuration to target the main content more precisely. Check the wiki for examples on setting these up based on site structure.

Question 3

Does read-art work with JavaScript-rendered pages?

Accepted Answer

No, read-art extracts content from raw HTML, so it may not handle JavaScript-heavy pages unless they are pre-rendered. For dynamic sites, consider using a headless browser before passing HTML to read-art.

Question 4

What's the memory usage for large-scale crawling with read-art?

Accepted Answer

In benchmarks, memory usage is around 200 MB per spider kernel when processing 1500k documents daily, making it efficient but requiring careful resource planning for very high volumes.

Question 5

read-art or Mozilla's Readability: which is better for Node.js?

Accepted Answer

read-art is optimized for performance in high-throughput crawling with built-in Chinese support, while Mozilla's Readability is more focused on browser compatibility. Choose read-art for server-side scraping at scale, especially with multi-language needs.

Question 6

How to handle images in extracted articles with read-art?

Accepted Answer

read-art includes an image fallback mechanism that tries to preserve images, but you may need to configure selectors or thresholds to ensure reliable extraction, as noted in the wiki.

read-art

What is read-art?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions