chore(cli): fix recording env

Author: j-mendez

.github/workflows/action.yml

@@ -18,4 +18,4 @@ jobs:
           TLD: true
           LIST: true
           UPGRADE: true
-          RECORD: ./recordings
+          RECORD: ~/recordings

README.md

@@ -58,61 +58,18 @@ All inputs are **optional** except $WEBSITE_URL.
 | -------- | -------------------------- | ------- |
 | `issues` | The amount of issues found |         |
 
-## Benches
 
-The hardware specs for results:
+## Performance
 
-```sh
-----------------------
-linux ubuntu-latest
-2-core CPU
-7 GB of RAM memory
-14 GB of SSD disk space
------------------------
-```
-
-### Benchmark Results
-
-The results for crawling a website that is small - large.
-
-#### crawl-speed
-
-Test url: `https://a11ywatch.com`
-
-25 pages
-
-runs with 10 samples:
-
-|                        | `libraries`            |
-| :--------------------- | :--------------------- |
-| **`A11yWatch: crawl`** | `0.4 s` (✅ **1.00x**) |
-| **`Pa11y-CI: crawl`**  | `45 s` (✅ **1.00x**)  |
-| **`Axe: crawl`**       | `N/A` (✅ **1.00x**)   |
-
-#### crawl-speed (Large Website)
-
-Test url: `https://www.hbo.com`
-
-7500 pages.
-
-runs with 10 samples:
-
-|                        | `libraries`               |
-| :--------------------- | :------------------------ |
-| **`A11yWatch: crawl`** | `2.5 mins` (✅ **1.00x**) |
-| **`Pa11y-CI: crawl`**  | `50+ hr` (✅ **1.00x**)   |
-| **`Axe: crawl`**       | `N/A` (✅ **1.00x**)      |
-
-### Benchmark Info
-
-On a larger website A11yWatch action runs over 60x-10,000x+ faster depending on CPUs/hardware.
+On a larger website A11yWatch action runs over 60x-10,000x+ faster depending on CPUs/hardware. After the first installation you should have faster setup time between runs.
+You can expect to handle at least 1k pages per minute on a 2-core CPU 7 GB of RAM memory shared github action. If you enable `RECORD` the output time may increase a bit.
 
 When `AI_DISABLED` is set to true the run for `A11yWatch` may increase.
 
 ## Common Issues
 
-If you experience issues on your CI you may have to toggle the `UPGRADE` input to true in order to get the latest docker images.
-We need docker in order to build the appliciation in quickly since we have some services that need to compile that may take awhile.
+If you experience issues on your CI you may have to toggle the `UPGRADE` input to true in order to get the latest installs. If you see 
+a playwright error try adding `PLAYWRIGHT_VERSION` env variable with the newest version to install chrome.
 
 ## CLI
 

action.yml

@@ -8,7 +8,7 @@ author: A11yWatch
 branding:
   icon: "shield"
   color: "gray-dark"
-description: Powerful web accessibility testing.
+description: Fast and feature-packged web accessibility testing.
 inputs:
   WEBSITE_URL:
     description: Website domain to scan
@@ -148,15 +148,15 @@ runs:
       uses: baptiste0928/cargo-install@v1
       with:
         crate: a11ywatch_cli
-        version: "0.10.7"
+        version: "0.10.8"
         features: "grpc"
 
     - name: A11yWatch CLI Install
       if: ${{ inputs.SLIM == 'false' }}
       uses: baptiste0928/cargo-install@v1
       with:
         crate: a11ywatch_cli
-        version: "0.10.7"
+        version: "0.10.8"
 
     - name: Configure CLI creds
       if: ${{ inputs.A11YWATCH_TOKEN }}
@@ -311,7 +311,7 @@ runs:
       if: ${{ inputs.RECORD && inputs.RECORD != 'false' && failure() || success() }}
       with:
         name: Recordings
-        path: ${{ inputs.RECORD && inputs.RECORD != 'false' && inputs.RECORD || './recordings'  }}
+        path: ${{ inputs.RECORD && inputs.RECORD != 'false' && inputs.RECORD || '~/recordings'  }}
 
     - name: Stop A11yWatch Service
       if: ${{ !inputs.EXTERNAL }}