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

web-speed-compare

v0.0.7

Published

NodeJS app that runs lighthouse against multiple websites and reports the comparison

Downloads

26

Readme

web-speed-compare

NodeJS app that runs lighthouse against multiple websites and reports the comparison. This was built with the purpose of assessing the impact of 3rd party scripts on a website, by measuring the website's performance blocking scripts one by one.

How to use

  • Install it as a global package: npm i -g web-speed-compare.
  • Create a json config file based on the example-config.json file.
  • Run the tool: web-speed-compare --config-file=config.json.

Arguments

  • --config-file (required): path to the configuration json file.
  • --output (optional): by default the tool will print the report in a nice table. You can specify ``--output=md` to print the result in a markdown table.

Configuration file

Example:

{
    "chromeFlags": ["--no-sandbox", "--headless", "--incognito"],
    "runs": 5,
    "pages": [
        {
            "url": "https://github.com/",
            "name": "Github",
            "blockedPatterns": []
        },
        {
            "url": "https://github.com/",
            "name": "Github w/o spotify image",
            "blockedPatterns": ["*spotify*"]
        }
    ]
}
  • chromeFlags: array of flags that will be passed to the Chrome launcher.
  • runs: number of times the tool will run Lighthouse on each page. The results will show the median of each metric. With a higher number the metrics will be more accurate, but the tool will take longer to run. Defaults to 3.
  • pages: array of objects with the information of pages to run the tool against.
    • url: url of the page
    • name: name to be used in the report
    • blockedPatterns: array of strings with patterns of the assets that will be blocked by Chrome. You can use this to block 3rd party scripts and measure the website's performance without them.

Example

web-speed-compare --config-file=config.json --output=md

| Metric                  | Google | Google w/o JS | Google w/o icons |
| :---------------------- | :----: | :-----------: | :--------------: |
| Performance Score       |   96   |      100      |        96        |
| First Contentful Paint  |  1245  |      1269     |       1268       |
| First Meaningful Paint  |  1260  |      1272     |       1294       |
| Speed Index             |  1602  |      1480     |       1656       |
| Estimated Input Latency |   42   |       12      |        45        |
| Total Blocking Time     |   312  |       0       |        340       |
| Max Potential FID       |   238  |       48      |        230       |
| Time To First Byte      |   97   |       98      |        92        |
| First CPU Idle          |  3426  |      1272     |       3411       |
| Time to Iteractive      |  3662  |      1272     |       3647       |
| NetworkRequests         |   29   |       10      |        30        |
| Total Byte Weight       | 308711 |     83967     |      305444      |
| DOM Size                |   411  |      388      |        411       |