npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

auto-perf-budget

v1.0.0

Published

Profile your web application automatically using headless chrome to ensure performance budgets are met.

Downloads

20

Readme

npm npm npm

auto-perf-budget

Run tests against specified URL's to keep control of your browser based experience .

Set a performance budget and run, whenever you want..

Measuring website performance is hard work, and Auto perf budget helps you profile your web site using a headless chrome browser to help you keep track of the answers to questions like this:

As a developer I want to know if my webpage is takes more than X ms to be interactive

Auto perf budget can be run locally, generating HTML reports or as command line interface for adding to build pipelines or as pre/post release step.

Auto perf budget opens specified URL's and checks against your defined performance budget values. It will report an error if your website is performing incorrectly.

How to use:

Run the app using this command:

  auto-perf-budget --config test.config.js

CLI Args:

--config <config-location>

Config:

See example (test.config.js):

module.exports = {
  urls: [
    {
      id: 'crc',
      url: "https://chainreactioncycles.com",
      screenshots: screenshots(),
      viewport: viewport()
    },
    {
      id: 'ebay',
      url: "https://ebay.com",
      screenshots: screenshots(),
      viewport: viewport()
    }
  ],
  report: 'html',
  budget: {
    level: 'error',
    timeline: {
      pageComplete: 350,//ms
      responseTime: 100,//ms
      domComplete: 500,//ms
      dns: 100,
      ttfb: 1000,//ms
      tti: 1000//ms
    }
  }
}

Options

url.screenshots : {object}

const screenshots = filename => ({
  enabled: true,
  fullPage: false,
  type: 'jpeg',
  quality: 80
}); 

Specify screenshot settings for each URL in config. Extends the default values found in Chrome puppeteer see screenshot here

url.viewport : {object}

const viewport = () => ({
  width: 1600,
  height: 2500,
  deviceScaleFactor: 1,
  isMobile: false,
  hasTouch: false,
  isLandscape: true
}); 

Specify the viewport settings for each URL in config. Extends the default values found in Chrome puppeteer see viewport here

Report {string}

report: 'html' || 'cli' 

Html: will open a html file with a report of each page and it's results.

Cli: will show the results in the command line, an error will throw an exit code.

Timeline : {object}

Uses the window.performance information, configure this object to set the values you want to benchmark against:

  timeline: {
    pageComplete: 350, //ms
    responseTime: 100, //ms
    domComplete: 500, //ms
    dns: 100, //ms
    ttfb: 1000, //ms
    tti: 1000 //ms
  }

Potential use-cases:

  • Automating screenshots of website;
  • Automate checking speed of website;
  • Cache warming of multiple pages;
  • Run after release and check recent changes aren't working against you.
  • Add to build pipeline on CI and check test envs.

Loads more.......

Output

Below is an example of output from cli:

alt Output

alt Output

@TODO Future Features:

  • Measuring resources on page and setting limits per asset.
  • Checking for more common performance bottlenecks, redirects, blocking scripts etc.

Uses Chrome puppeteer under the hood.

MIT License

Copyright (c) [2017] [Daniel Jenkins]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.