FAQs
Report-specific answers
Key takeaways for paulgraham.com pulled from this audit.
How often should I refresh the YourWebsiteScore report for paulgraham.com?
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 paulgraham.com tackle first?
Cumulative Layout Shift (mobile) at 0.10: reclaim ≈2 points. Reserve space for media, stabilise fonts, and avoid late-loading ads to prevent jarring layout shifts.
Largest Contentful Paint (mobile) at 2.0s: reclaim ≈1 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.
First Contentful Paint (mobile) at 1.8s: reclaim ≈1 points. Reduce render-blocking CSS/JS and stream initial HTML so meaningful content appears earlier.
Which Lighthouse SEO audits should paulgraham.com fix first?
Document does not have a meta description (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how paulgraham.com appears in search.
robots.txt is not valid (mobile) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how paulgraham.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 paulgraham.com appears in search.
Document does not have a meta description (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how paulgraham.com appears in search.
robots.txt is not valid (desktop) is missing roughly 8 points. Fixing it will raise the SEO score and strengthen how paulgraham.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 paulgraham.com appears in search.
Which Lighthouse Best Practices should paulgraham.com fix first?
Does not use HTTPS (mobile) is missing roughly 18 points. Fixing it will raise the Best Practices score and keep paulgraham.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 paulgraham.com aligned with modern browser expectations.
Page lacks the HTML doctype, thus triggering quirks-mode (mobile) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep paulgraham.com aligned with modern browser expectations.
Does not use HTTPS (desktop) is missing roughly 19 points. Fixing it will raise the Best Practices score and keep paulgraham.com aligned with modern browser expectations.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale` (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep paulgraham.com aligned with modern browser expectations.
Page lacks the HTML doctype, thus triggering quirks-mode (desktop) is missing roughly 4 points. Fixing it will raise the Best Practices score and keep paulgraham.com aligned with modern browser expectations.
Which Lighthouse Accessibility audits should paulgraham.com fix first?
Image elements do not have `[alt]` attributes (mobile) is missing roughly 10 points. Fixing it will raise the Accessibility score and make paulgraham.com easier to use.
`<html>` element does not have a `[lang]` attribute (mobile) is missing roughly 7 points. Fixing it will raise the Accessibility score and make paulgraham.com easier to use.
Links do not have a discernible name (mobile) is missing roughly 7 points. Fixing it will raise the Accessibility score and make paulgraham.com easier to use.
Image elements do not have `[alt]` attributes (desktop) is missing roughly 16 points. Fixing it will raise the Accessibility score and make paulgraham.com easier to use.
`<html>` element does not have a `[lang]` attribute (desktop) is missing roughly 11 points. Fixing it will raise the Accessibility score and make paulgraham.com easier to use.
Which Website Quality issues should paulgraham.com fix first?
Meta Description: missing ≈15 points. Missing (add <meta name='description'> with 120-160 chars). Focus on it to lift paulgraham.com's Website Quality score.
Title: missing ≈8 points. 11 chars (ideal 30–60). Focus on it to lift paulgraham.com's Website Quality score.
Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift paulgraham.com's Website Quality score.
Which Trust & Security fixes should paulgraham.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 paulgraham.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 paulgraham.com's Trust & Security score.
Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise paulgraham.com's Trust & Security score.