feat: add blog post about achieving perfect Lighthouse scores

[baezor]

Summary

Adds a new blog post documenting how we achieved 100/100/100/100 on all Lighthouse categories (Performance, Accessibility, Best Practices, SEO), with a PageSpeed Insights screenshot as the hero image.

Test plan

• npm run build passes
• 40/40 visual regression tests pass
• CI checks pass

[cloudflare-workers-and-pages]

Deploying baezor with    Cloudflare Pages

Latest commit:	6af14ea
Status:	✅  Deploy successful!
Preview URL:	https://7b1eccd0.baezor.pages.dev
Branch Preview URL:	https://feature-blog-lighthouse-scor.baezor.pages.dev

View logs

[claude]

Code Review - Verdict: Approve with suggestions. Well-written blog post with correct structure. Frontmatter is schema-compliant, image is correctly placed in src/assets/, visual regression snapshots are updated for 8 affected variants. FAQs are well-structured. Suggestions: (1) Title vs content mismatch - Performance shows 99 not 100 in the table, consider clarifying. (2) Description says 3 scores but title implies 4. (3) pubDate ISO format works but simpler date format is conventional. No security or test coverage concerns.

[claude]

Verdict: Approve with suggestions

Well-written blog post with correct structure. Here are my observations.

Frontmatter is schema-compliant with src/content/config.ts. All fields (title, description, pubDate, heroImage, categories, keywords, contentType, faqs) are valid.

Image is correctly placed in src/assets/ per CLAUDE.md, enabling Astro optimization.

Visual regression snapshots are updated for the 8 affected variants (header mobile-open and homepage). Changes match the accessibility fixes described in the post (aria-label updates and CTA text change).

FAQs are well-structured for AEO and structured data purposes.

Suggestions:

1. Title vs content mismatch - The title says "100 Across the Board" and the hero image shows 100/100/100/100, but the results table shows Performance at 99 both before and after. The title is misleading. Consider renaming to: "How I Achieved 100/100/100 on Lighthouse Accessibility, Best Practices, and SEO", or add a note that Performance was already strong and not a target of this effort.

2. Frontmatter description vs title inconsistency - The description correctly says "from 95/81/92 to 100/100/100 on Accessibility, Best Practices, and SEO" (3 scores matching the table). The title implies all 4 categories hit 100. Aligning these is better for accuracy.

3. Minor: pubDate style - pubDate: 2026-03-19T00:00:00.000Z works fine (Zod parses it), but pubDate: 2026-03-19 is simpler and more conventional. Not a bug.

No security, performance, or test coverage concerns. This PR is purely a content change with no code logic modifications.