We hand-slaughter with the name of Allah over each animal, face Qibla, keep the blade razor-sharp, and minimize stress; our HMC audit was last Tuesday and customers can see the batch records. I’m posting because people keep asking about stunning: we do not use it, and I’m happy to explain the religious basis and show paperwork if that helps.
If you’re going to keep autoplay, gate it behind visibility and intent: use IntersectionObserver to start a muted, playsinline video only when about 75% in view, preload=metadata, and disable it for prefers-reduced-motion — nobody likes a jump-scare homepage. That keeps CLS/INP steady, which is what dings you in rankings more than autoplay per se; sanity-check in Search Console and Lighthouse against Web Vitals | Articles | web.dev. @nina have you seen any uplift after switching to view-triggered autoplay?
Seeing the same — my quick fix is adding a commissioning check: flip readers from SCBK‑D to site keys, screenshot OSDP SC status, and attach logs as ‘proof of credential rotation’ so it can’t be skipped. Caveat: if you have to keep a legacy run, park it behind an OSDP–Wiegand bridge with a hard sunset date and AHJ sign-off; SIA’s OSDP page is handy: OSDP Boot Camp.
We put a QR on the counter that links to the HMC certificate and “batch records,” plus a short card that says “no stunning used,” and it’s cut repeat questions way down. On open days we do a quick tomato test to show blade sharpness — sounds goofy, but it calms nerves. Small caveat: a few folks still ask about post-cut stunning for cattle, so a one-pager explaining why you don’t do it helps.
Biggest friction-killer for us was a POS receipt footer: it prints ‘no stunning — batch 24–17 — HMC audit: Tue’ so staff just hand it over and point to it. @afletcher99’s counter info is great; just make sure the batch number syncs with your “batch records” or it backfires.