Browser Best Practices
Lighthouse Best Practices checks browser-side reliability, security hygiene, and deprecated patterns that can quietly break user experience or customer trust.
Ludwig Makhyan · Founder, WebsiteCoach ·
Jump to section
Executive Overview
The Best Practices score is Lighthouse's catch-all quality signal for browser-side risks. It looks for runtime JavaScript errors, insecure requests, vulnerable libraries, deprecated APIs, image presentation problems, and other issues that do not always fit neatly into performance, SEO, or accessibility.
Business Impact
A low Best Practices score is often an early warning that the site is carrying fragile frontend code or outdated dependencies. Console errors can break forms and checkout flows, vulnerable libraries increase security exposure, and mixed or insecure resources reduce trust even when the page appears to load.
Source: Google Lighthouse Best Practices category returned by the PageSpeed Insights API.
Browser Best-Practice Signals Explained
- Lighthouse Best Practices score (0-100)
- A summary of Lighthouse's selected checks. Read failed audits rather than treating the number as a complete quality assessment.
- Browser console errors and JavaScript runtime failures
- Reproduce console failures in the relevant user journey. Fix application errors and distinguish third-party noise.
- HTTPS usage and secure resource loading
- Confirm that the document and its required resources use HTTPS without mixed-content failures.
- Known vulnerable JavaScript libraries
- Check the affected package and version against the reported advisory. Update and test the flows that use it.
- Deprecated browser APIs and unsafe coding patterns
- Replace deprecated APIs with supported alternatives and test the browsers your users depend on.
- Image aspect ratio, resolution, and presentation quality
- Inspect displayed images for stretching or inadequate resolution. Serve appropriately sized assets with stable dimensions.
Role-Specific Action Plan
- →Treat low Best Practices scores as technical debt that can affect conversion, trust, and security posture
- →Prioritise issues on checkout, lead forms, account flows, and paid landing pages
- →Fix browser console errors before release and include console-clean checks in QA
- →Remove deprecated APIs and replace fragile third-party snippets
- →Validate image dimensions and aspect ratios so visual defects do not create layout or trust issues
- →Audit client-side libraries for known vulnerabilities and update stale packages
- →Ensure every resource loads over HTTPS and avoid mixed-content exceptions
- →Pair Lighthouse findings with dependency scanning such as npm audit, Snyk, or GitHub Dependabot
- →Run Lighthouse or WebsiteCoach before major deploys and after CMS/plugin updates
- →Set a minimum Best Practices threshold for high-value templates and user journeys
Frequently asked questions
What is Browser Best Practices?
Lighthouse Best Practices checks browser-side reliability, security hygiene, and deprecated patterns that can quietly break user experience or customer trust.
Why does Browser Best Practices matter?
A low Best Practices score is often an early warning that the site is carrying fragile frontend code or outdated dependencies. Console errors can break forms and checkout flows, vulnerable libraries increase security exposure, and mixed or insecure resources reduce trust even when the page appears to load.
Official references
Related topics
Check your browser best practices score now
Free audit in 60 seconds — no account required.
Run Free Audit