FAQs
Report-specific answers
Key takeaways for Tierly.app pulled from this audit.
How often should I refresh the YourWebsiteScore report for Tierly.app?
The latest audit was captured on September 21, 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 Tierly.app tackle first?
Cumulative Layout Shift (desktop) at 0.14: reclaim ≈5 points. Reserve space for media, stabilise fonts, and avoid late-loading ads to prevent jarring layout shifts.
Largest Contentful Paint (mobile) at 2.7s: reclaim ≈4 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.
Total Blocking Time (desktop) at 138ms: reclaim ≈2 points. Split large JavaScript bundles, defer non-critical scripts, and keep heavy work off the main thread to improve responsiveness.
Which Lighthouse SEO audits should Tierly.app 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 Tierly.app 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 Tierly.app fix first?
Buttons do not have an accessible name (mobile) is missing roughly 6 points. Fixing it will raise the Accessibility score and make Tierly.app 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 Tierly.app easier to use.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Tierly.app 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 Tierly.app easier to use.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). (desktop) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Tierly.app 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 Tierly.app easier to use.
Which Website Quality issues should Tierly.app fix first?
Meta Description: missing ≈9 points. 217 chars (ideal 120–160). Focus on it to lift Tierly.app's Website Quality score.
Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift Tierly.app's Website Quality score.
Sitemap: missing ≈7 points. Missing (create sitemap.xml and submit to Google Search Console). Focus on it to lift Tierly.app's Website Quality score.
Which Trust & Security fixes should Tierly.app tackle first?
Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise Tierly.app's Trust & Security score.
Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise Tierly.app's Trust & Security score.
MIME Type Protection: missing ≈5 points. Missing (should be: X-Content-Type-Options: nosniff). Close this gap to raise Tierly.app's Trust & Security score.