Today I came across an article by Wictor Wilen describing health scores in SharePoint 2013.
I’m using Office 365 so that article isn’t describing what I need. I’m finding that my tenant is very slow but is there a way to check my farm?
OfficeDev PnP PowerShell (https://github.com/OfficeDev/PnP-PowerShell) giving a very easy answer. The Get-SPOHealthScore CmdLet.
As always I’m first connecting to my tenant:
Connect-SPOnline https:/ /mytenant.sharepoint.com
Then when I’m connected:
Get-SPOHealthScore
This now returns my health score between 0-10. Where 0 is the best possible.

Ok, so my tenant is healthy.
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/
Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/
You can contact me using contact@sharepains.com