misc: check doc page by Lighthouse CI

[lex111]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Since the doc page represents the main functionality of Docusaurus, Lighthouse should check it instead of the landing page. For example, the a11y error with the home page in the breadcrumbs could have been detected earlier.

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	2a2396f
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62726dd764e02200087ef57a
😎 Deploy Preview	https://deploy-preview-7300--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	59
🟢 Accessibility	100
🟢 Best practices	92
🟢 SEO	100
🟢 PWA	90

Lighthouse ran on https://deploy-preview-7300--docusaurus-2.netlify.app/

[Josh-Cena]

Can we check both?

The landing page's performance is still important, like FCP

[Josh-Cena]

Why does it always only check one URL😢 When you check the actions log for 3a5d4d4 and ea22edd, they seem to still stick with the old config

[lex111]

Perhaps need to merge this change so that the config for CI is updated?

[Josh-Cena]

Theoretically, the action should be using the config on this branch, especially since this is not in a fork. At least that's how I tested my config changes. My main worry is how audits on multiple URLs will be formatted, so I'd need to see at least what the output looks like.

[Josh-Cena]

@lex111 From our actions/github-script, we only take the first check's manifest and post it as comment. Can you add the second one's as well? We can simply add another column to the table.

[lex111]

I don't quite understand you, it will be for each of the checked pages by a separate table?

[Josh-Cena]

I'm suggesting it to be

| Category | Landing page score | Doc page score |
| --- | --- | --- |
| Performance | 🟠 57 | 🟠 57 |
| Accessibility | 🟢 100 | 🟢 100 |
| Best practices | 🟢 92 | 🟢 92 |
| SEO | 🟢 100 | 🟢 100 |
| PWA | 🟢 90 | 🟢 90 |

So instead of using [0] index, we just use a map instead.

[lex111]

I have another idea how visualize data that should work, but it is problematic to test these changes.

[Josh-Cena]

Yeah, I can understand. Do you want to merge this so we can test it?

[lex111]

Yes, let's check it out in action.