Search Results for "performance"

...In scope for this project is any well-known and widely-used test for HTML document quality. A major use for this project is continuous integration -- so we must have reliable results. We usually balance correctness over performance. And, if necessary, we should be able to trace this program's detection of HTML errors back to documented best practices or standards, such as W3 specifications. Third-party modules. We want this product to be useful for continuous integration so we prefer to avoid subjective tests which are prone to false positive results, such as spell checkers, indentation checkers, etc. ...

Amplify for Jekyll is a static site theme or template built with the static-site generator Jekyll, designed in the vague style of Medium, and leveraging the Google AMP (Accelerated Mobile Pages) framework for ultra-fast performance on mobile. The idea is to give authors a blogging theme that loads extremely quickly on mobile devices, with AMP-compatible markup and Jekyll integration. The README highlights performance numbers: on slow connections, pages built with this theme render in a fraction of the time compared to standard pages. It supports the usual Jekyll workflow (clone the repo, configure _config.yml, build/serve) but enforces AMP constraints (inline CSS, specific tags like <amp-img>, etc). ...

...It provides an easy-to-use API for parsing, modifying and querying documents (using XPath expressions). Oga does not require system libraries such as libxml, making it easier and faster to install on various platforms. To achieve better performance Oga uses a small, native extension (C for MRI/Rubinius, Java for JRuby). Oga provides an API that allows you to safely parse and query documents in a multi-threaded environment, without having to worry about your applications blowing up. Oga uses the version format MAJOR.MINOR (e.g. 2.1). An increase of the MAJOR version indicates backwards incompatible changes were introduced. ...