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

@bkwld/lightkeeper

v1.3.0

Published

Averages multiple successive Lighthouse tests to arrive at a more accurate PageSpeed score

Downloads

4

Readme

lightkeeper

Averages multiple successive Lighthouse tests to arrive at a more accurate PageSpeed score.

Usage

$ npm install --global @bkwld/lightkeeper
$ lightkeeper https://yourdomain.com

The results will be something like this:

Mobile Results
┌─────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┐
│     │ Score │ FCP   │ SI    │ LCP   │ TTI   │ TBT   │ CLS   │
├─────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ #1  │ 57    │ 3.8s  │ 5s    │ 6.2s  │ 5.6s  │ 328ms │ 0     │
├─────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ #2  │ 66    │ 2.5s  │ 3.5s  │ 5.5s  │ 5.2s  │ 406ms │ 0.005 │
├─────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ #3  │ 70    │ 2.5s  │ 3.5s  │ 5.4s  │ 5s    │ 307ms │ 0     │
├─────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ AVG │ 64.3  │ 2.9s  │ 4s    │ 5.7s  │ 5.3s  │ 347ms │ 0.002 │
├─────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ SD  │ 5.4   │ 646ms │ 719ms │ 354ms │ 263ms │ 42ms  │ 0.002 │
└─────┴───────┴───────┴───────┴───────┴───────┴───────┴───────┘

The summary rows (which can be exclusive returned with the -s option) contain the following rows:

Options

From lightkeeper --help:

ARGUMENTS

  <url>                   The URL to test

OPTIONS

  -b, --block <urls>    Comma seperated URLs to block, wildcards allowed
  -d, --desktop         Test only desktop
  -m, --mobile          Test only mobile
  -s, --summary         Only show summary rows
  -t, --times <count>   The number of tests to run
                        default: 10

For example:

  • lightkeeper https://www.bukwild.com - Runs 10 desktop and 10 mobile tests
  • lightkeeper https://www.bukwild.com -m -t=30 -b=googletagmanager - Runs 30 mobile tests while blocking Google Tag Manager
  • lightkeeper https://www.bukwild.com -ms -t=100 && say "All done" - Runs 100 mobile tests and only show the summary at the end. And says "All done" aloud on a Mac.