GT Metrix command automation

Installation

npm install -g @jackbrown9375/gtmetrix

Description:

The command gtmetrix helps the developer to process a batch of urls generating the gtmetrix report for each one in a single file. It allows a pool of API keys and a pool of urls.

Full Example

gtmetrix spot example --keys mykeyingtmetrix --urls https://google.com https://example.com
gtmetrix run example.json  report1 "Simple Comment for the report1(before the update)"
#Now you can update your website and then repeat the report to compare them
gtmetrix run example.json  report2 "Comment for the report2(after the update)"
gtmetrix compare report1 report2

Params:

help        Shows the full help. Used with another params show the 
            help of that specific param.
            e.g: 
            gtmetrix help run

spot        Create the batch seed file to process.
            You can provide the following parameters
            --keys: to provide the gtmetrix API keys
            --urls: to provide the list of urls to process
            --user: the htaccess_user (if the urls needs it)
            --pass: the htaccess_password (if the url needs it)
            Structure:
            ${commandName} spot <my_seed> --keys <key1> <key..>  --urls <url1> <url..>  --user <htaccess_user> --pass <htaccess_pass>
            e.g:
            ${commandName} spot example --keys mykeyingtmetrix --urls https://google.com https://example.com 
    
            The command will generate a file with the name 
            example.json with the structure, you can edit it with your custom params.

run         Execute the bash seed file generating the final report.
            e.g:
            gtmetrix run <my_seed> <my_report_1>  "A comment"
            The command process the file <my_seed>.json 
            and generate a file with name <my_report_1>

compare     Generate the CSV comparision between two reports of
            the same seed file. Also it prints the gtmetrix url comparison.
            e.g:
            gtmetrix compare <first_report> <second_report>