mozilla / mozilla/blurts-server
webhint report for staging (2023-03-23)
Nobody has claimed this yet.
- Dominant language
- Fluent
- Stars
- 942
- Forks
- 315
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 19
Description
Ref: https://webhint.io/
Used some default .hintrc config:
{
"extends": ["web-recommended"]
}
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached webhint report and the staging URL, then review the listed errors and warnings to determine which findings affect the application or production configuration. Done means the relevant findings are resolved or explicitly triaged for production, with the remaining items explained.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, testing-qa, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100