FAQs
Report-specific answers
Key takeaways for Sendx.io pulled from this audit.
How often should I refresh the YourWebsiteScore report for Sendx.io?
The latest audit was captured on September 26, 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 Sendx.io tackle first?
Cumulative Layout Shift (mobile) at 0.27: reclaim ≈14 points. Reserve space for media, stabilise fonts, and avoid late-loading ads to prevent jarring layout shifts.
Largest Contentful Paint (mobile) at 3.2s: reclaim ≈7 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.
First Contentful Paint (mobile) at 2.5s: reclaim ≈3 points. Reduce render-blocking CSS/JS and stream initial HTML so meaningful content appears earlier.
Which Lighthouse SEO audits should Sendx.io fix first?
Links do not have descriptive text (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Sendx.io appears in search.
Links are not crawlable (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Sendx.io appears in search.
robots.txt is not valid (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how Sendx.io appears in search.
Which Lighthouse Best Practices should Sendx.io fix first?
Charset declaration is missing or occurs too late in the HTML (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep Sendx.io 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 Sendx.io aligned with modern browser expectations.
Which Lighthouse Accessibility audits should Sendx.io fix first?
Buttons do not have an accessible name (mobile) is missing roughly 5 points. Fixing it will raise the Accessibility score and make Sendx.io easier to use.
Touch targets do not have sufficient size or spacing. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make Sendx.io 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 Sendx.io easier to use.
Which Website Quality issues should Sendx.io fix first?
Headings: missing ≈6 points. H1 missing (add one <h1> tag for main title). Focus on it to lift Sendx.io's Website Quality score.
Image: missing ≈3 points. Missing (add <meta property='og:image'> with 1200x630px image). Focus on it to lift Sendx.io's Website Quality score.
Schema.org JSON-LD: missing ≈2 points. Missing (consider Organization, Article, Product, or FAQPage schemas). Focus on it to lift Sendx.io's Website Quality score.
Which Trust & Security fixes should Sendx.io tackle first?
HTTP Strict Transport Security: missing ≈15 points. Missing (should be: Strict-Transport-Security: max-age=31536000; includeSubDomains). Close this gap to raise Sendx.io's Trust & Security score.
Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise Sendx.io's Trust & Security score.
Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise Sendx.io's Trust & Security score.