Decisions Sam made this session
- Inline CSS/JS: install Autoptimize, conservative tune.
- Avvo sameAs: auto-discover via web, deploy where confidence is high.
- Audit source-check: yes, trace it.
- APO: standing always-allow on the SAIL Cloudflare zone.
What I did after that
Autoptimize
- Installed Autoptimize 3.1.15.1 via
POST /wp/v2/plugins with status=inactive. Zero risk on install alone.
- Did NOT activate. Reason: Kadence Blocks emits per-block inline CSS that is largely page-unique. Autoptimize aggregation produces many cached files but limited total-byte reduction. Now that APO has standing approval, APO is the better first move — enable it, measure, and only then decide whether Autoptimize CSS aggregation adds value on top.
Avvo discovery
Bigger discovery on the schema (correction to my earlier finding)
My first verification said most bios already had Attorney + bar identifier + sameAs KyBar + sameAs SuperLawyers. That was wrong. I matched substrings inside the entire JSON-LD blob — some matches were from non-Person entities (e.g. text content, organization records). When I parsed the actual Person entries:
- Each bio page ships ONE shared @graph that contains ALL 11 attorneys as Person entries.
- Sam Aguiar Person: 3 sameAs (LinkedIn, SuperLawyers, BestAttorneysOfAmerica). No Avvo, no KyBar, no identifier.
- Every other attorney Person: 0 sameAs. No identifier.