FAQs
Report-specific answers
Key takeaways for Binance.com pulled from this audit.
How often should I refresh the YourWebsiteScore report for Binance.com?
The latest audit was captured on September 19, 2025.
Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.
Which Lighthouse performance improvements should Binance.com tackle first?
Total Blocking Time (desktop) at 775ms: reclaim ≈27 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.
Total Blocking Time (mobile) at 1.5s: reclaim ≈26 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.
Cumulative Layout Shift (mobile) at 0.40: reclaim ≈19 points. Reserve space for media, stabilise fonts, and avoid late-loading ads to prevent jarring layout shifts.
Which Lighthouse SEO audits should Binance.com fix first?
Links are not crawlable (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Binance.com appears in search.
Image elements do not have `[alt]` attributes (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Binance.com appears in search.
Links are not crawlable (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Binance.com appears in search.
Image elements do not have `[alt]` attributes (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Binance.com appears in search.
Which Lighthouse Best Practices should Binance.com fix first?
Uses deprecated APIs (mobile) is missing roughly 18 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Serves images with low resolution (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Browser errors were logged to the console (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Uses deprecated APIs (desktop) is missing roughly 19 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Serves images with low resolution (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Browser errors were logged to the console (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Binance.com aligned with modern browser expectations.
Which Lighthouse Accessibility audits should Binance.com fix first?
Image elements do not have `[alt]` attributes (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
Background and foreground colors do not have a sufficient contrast ratio. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
Image elements do not have `[alt]` attributes (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 3 points. Fixing it will raise the Accessibility score and make Binance.com easier to use.
Which Website Quality issues should Binance.com fix first?
Title: missing ≈20 points. Missing (add <title> tag with 30-60 chars). Focus on it to lift Binance.com's Website Quality score.
Meta Description: missing ≈15 points. Missing (add <meta name='description'> with 120-160 chars). Focus on it to lift Binance.com's Website Quality score.
Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift Binance.com's Website Quality score.
Which Trust & Security fixes should Binance.com tackle first?
HTTP Strict Transport Security: missing ≈15 points. Missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains). Close this gap to raise Binance.com's Trust & Security score.
Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise Binance.com's Trust & Security score.
Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise Binance.com's Trust & Security score.