FAQs
Report-specific answers
Key takeaways for secondary.ai pulled from this audit.
How often should I refresh the YourWebsiteScore report for secondary.ai?
The latest audit was captured on October 3, 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 secondary.ai tackle first?
Total Blocking Time (desktop) at 1.4s: reclaim ≈30 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.
Largest Contentful Paint (mobile) at 9.4s: reclaim ≈25 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.
Speed Index (desktop) at 5.0s: reclaim ≈10 points. Trim render-blocking resources, preconnect to critical domains, and focus on above-the-fold rendering to accelerate visual completion.
Which Lighthouse SEO audits should secondary.ai fix first?
Mobile Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.
Desktop Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.
Which Lighthouse Best Practices should secondary.ai fix first?
Mobile Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.
Desktop Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.
Which Lighthouse Accessibility audits should secondary.ai fix first?
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 secondary.ai easier to use.
Heading elements are not in a sequentially-descending order (mobile) is missing roughly 2 points. Fixing it will raise the Accessibility score and make secondary.ai easier to use.
Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make secondary.ai easier to use.
Heading elements are not in a sequentially-descending order (desktop) is missing roughly 2 points. Fixing it will raise the Accessibility score and make secondary.ai easier to use.
Which Website Quality issues should secondary.ai fix first?
Meta Description: missing ≈9 points. 283 chars (ideal 120–160). Focus on it to lift secondary.ai's Website Quality score.
Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift secondary.ai's Website Quality score.
Headings: missing ≈6 points. Missing (add H1, H2, H3, H4, H5, H6 tags to structure content). Focus on it to lift secondary.ai's Website Quality score.
Which Trust & Security fixes should secondary.ai tackle first?
Domain Rating: missing ≈25 points. No domain rating found. Close this gap to raise secondary.ai's Trust & Security score.
HTTP Strict Transport Security: missing ≈15 points. Missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains). Close this gap to raise secondary.ai's Trust & Security score.
Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise secondary.ai's Trust & Security score.