WebPerf and front-end quality testing tool
Find a file
2017-05-27 23:25:59 +01:00
bin Add domain blocking option to the CLI 2016-12-29 19:45:11 +08:00
doc/img Improve doc 2015-05-13 19:23:12 +02:00
front/src Add file names to duplicated css selectors offenders (#233) 2017-05-27 23:25:59 +01:00
lib Ignore unused fonts (#234) 2017-05-27 23:25:59 +01:00
server_config Add a way to block some urls to avoid spam (#219) 2017-01-08 22:38:34 +08:00
test Add a way to block some urls to avoid spam (#219) 2017-01-08 22:38:34 +08:00
.gitignore Replace bower by npm (browserify) 2015-08-16 13:22:12 +02:00
.travis.yml Update dependencies 2016-07-08 13:06:51 +08:00
Gruntfile.js Merge branch 'master' into develop 2016-12-29 22:23:16 +08:00
LICENSE Initial commit 2014-08-01 16:24:43 +02:00
package.json Add file names to duplicated css selectors offenders (#233) 2017-05-27 23:25:59 +01:00
README.md Authorship 2016-07-28 20:18:01 +08:00
Vagrantfile Use a synced folder in Vagrant 2016-12-30 22:17:29 +08:00

Yellow Lab Tools

Analyzes a webpage and detects performance or front-end code quality issues. Free, easy to launch, easy to understand, in-depth details.

No website should go live without being tested with Yellow Lab Tools

The online tool (recommended): http://yellowlab.tools
The CLI (Command Line Interface) - Doc here
The Grunt task: gmetais/grunt-yellowlabtools
For developers or Continuous Integration
The NodeJS package - Doc here
The public API - Doc here
Allows you to launch runs from any language

How it works

The tool loads the given URL via PhantomJS (a headless browser) and collects various metrics and statistics with the help of Phantomas. These metrics are then categorized and transformed into scores. It also gives in-depth details so developpers can fix the detected issues.

By the way, it's free because we are geeks, not businessmen. All we want is a ★ on GitHub, it will boost our motivation to add more awesome features!!!

example dashboard screenshot

Test your localhost

You can use ngrok, a tool that creates a secure tunnel between your localhost and the online tool (or the public API). You can also use the CLI or the Grunt tasks as they run on your machine.

Install your own private instance

If your project is not accessible from outside, or if you want to fork and improve the tool, you can build your own instance. The documentation is here.

Author

Gaël Métais. I'm a webperf freelance. Follow me on Twitter @gaelmetais, I tweet about Web Performances, Front-end and new versions of YellowLabTools!

I can also help your company about Web Performances, visit my website.

Contributors