LFW

Blog · all articles

For embassies and missions.

The articles that apply to the websites these organizations run, in one place, with a feed of their own. The market page is here.

The Four Files Nobody Links To

Every website has four plain-text files no visitor ever sees: robots.txt, sitemap.xml, security.txt, and llms.txt. Search engines, security scanners, and AI agents read them on every visit.

What each one is, who actually reads it, what to put in it, and the one rule that keeps all of them safe. We went through this list on our own site this week and found gaps, so the free audit now checks for them.

Our Hero Image Was Disappearing on iPhones. An Ad Blocker Was Hiding It.

For weeks the hero on three of our own pages vanished for a second and a half on iPhones, on a cold load only. Nothing reproduced it in a lab.

A fifty-line field trace found it in three page loads: an ad blocker was hiding any element whose class started with ad-.

Accessibility Tips

Color contrast, image headers, link behavior, and the small interface choices that determine whether a page works for everyone.

Error Messages That Actually Help

A form's error messages are the only conversation it ever has. What a useful error says, where it belongs on the page, when it should speak up, and who has to be able to perceive it.

Labels Versus Placeholders

Placeholder-only forms look clean in a mockup and fall apart in use. Why the label has to stay visible, what placeholders are actually good at, and what a screen reader hears when the label is missing.

Email Deliverability

Password resets, spam folders, domain trust, and why important website emails should never look suspicious to inbox providers.

The letter

The mission letter

Once a month: one number from our census of sites like yours, one fix, and what we published. No sequence, no sales calls.

One confirmation email first. Nothing sends until you click it. Or follow by RSS.

Prefer to write?

Tell us what needs to work better.

Slow, fragile, hard to edit, missing a workflow. Say it plainly, and you'll get a straight answer, not a ticket number.

You'll get a straight answer, usually the same day.