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

perfbench

v1.8.1

Published

Benchmark metrics for your web application

Downloads

11

Readme

 

Build Status

 

minimal setup

npm install perfbench --save

 

usage

Add to your package.json

"scripts": {
  "test": "perfbench http://localhost:3000"
}

use with CI

Add this line in your .travis.yml

scripts:
  - perfbench http://localhost:3000

 

metrics measured

  • First meaningful paint (1600 ms threshold)
  • Speed index metric (1250)
  • Time to interactive (2500 ms)
  • Total byte weight (1600 Kb)

 

test conditions

  • Network: Regular 3G (750 Kbps)
  • Device emulation: Nexus 5X
  • CPU: 5x slowdown

 

configuration

You can also drop a YAML file .perf.yml in the root of your repository for easier customisation.

All fields are optional.

runs: 2         # average of how many runs (optional, default: 3)
fail: false     # fail: true only throws a warning (optional, default: true)
thresholds:     # build will fail if these thresholds are not met (optional, defaults:)
  - first-meaningful-paint: 1600
  - speed-index-metric: 1250
  - time-to-interactive: 2500
  - total-byte-weight: 1600

 

custom properties

You can also add custom properties.

Send a user timing performance event from your javascript.

performance.mark('Page ready')

And add the kebabcased key to .perf.yml

thresholds:
  - page-ready: 1500
event-type

For travis users, if you would like to run perfbench in pull_request instead of push, set event-type in .perf.yml

event-type: pull_request

 

like it?

:star: this repo

 

todo

  • support multiple urls

 

license

MIT © siddharthkp