You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time npx hint https://stage.firefoxmonitor.nonprod.cloudops.mozgcp.net/
✖ Finishing...
You can view the HTML report in"/Volumes/Dev/github/mozilla/blurts-server/hint-report/https-stage-firefoxmonitor-nonprod-cloudops-mozgcp-net.html"
compat-api/css 1 warning
meta-viewport 1 error
sri 1 error
ssllabs 1 error
x-content-type-options 2 errors
axe/color 3 warnings
content-type 4 warnings
compat-api/html 5 warnings
disown-opener 6 errors
no-html-only-headers 16 warnings
http-compression 4 warnings 13 hints
strict-transport-security 17 errors
no-disallowed-headers 35 warnings
http-cache 1 error 18 warnings 30 hints
detect-css-reflows/layout 170 hints
× Found a total of 29 errors, 86 warnings, 213 hints and 0 informations
npx hint https://stage.firefoxmonitor.nonprod.cloudops.mozgcp.net/ 3.25s user 0.89s system 36% cpu 11.214 total
REPORT:https-stage-firefoxmonitor-nonprod-cloudops-mozgcp-net.html.txt
GitHub wouldn't let me upload an .html file, so I added a .txt suffix. You should be able to rename it locally and open in your favorite browser of choice.
I did a quick scan and nothing looked suspicious, but I'll leave it to y'all to determine if anything looks concerning on the stage env and might affect production in any way.
Semi related, but I also did a Google Lighthouse audit of staging and it got 3× 💯 scores, and a 90 for SEO (mainly because I think we prevent crawlers from indexing non-production sites). So I ignorantly assume it'll be four-hundred on production.
The text was updated successfully, but these errors were encountered:
Ref: https://webhint.io/
Used some default .hintrc config:
REPORT: https-stage-firefoxmonitor-nonprod-cloudops-mozgcp-net.html.txt
GitHub wouldn't let me upload an .html file, so I added a .txt suffix. You should be able to rename it locally and open in your favorite browser of choice.
I did a quick scan and nothing looked suspicious, but I'll leave it to y'all to determine if anything looks concerning on the stage env and might affect production in any way.
Semi related, but I also did a Google Lighthouse audit of staging and it got 3× 💯 scores, and a 90 for SEO (mainly because I think we prevent crawlers from indexing non-production sites). So I ignorantly assume it'll be four-hundred on production.
The text was updated successfully, but these errors were encountered: