Cursor timing (~4 blinks each side); rewrite perf post to the real fix

- Monitor terminal: ~4 blinks, type 'such', backspace, ~4 blinks, fade.
- Rewrite the blog post so it tells the accurate story end to end (not an update):
  the LCP breakdown showed render delay with TTFB 0 and a free main thread, so it
  was neither the network nor JavaScript. It was render-blocking CSS, fixed by
  inlining the stylesheet. Server components / dropping framer are kept as honest
  supporting steps, not the gate. Swap the architecture figure for a CSS
  critical-path figure; mobile now a steady 100.
This commit is contained in:
jwinterm
2026-06-07 17:32:21 -04:00
parent 89c086398d
commit d2d4ff997f
4 changed files with 88 additions and 101 deletions
+7 -8
View File
@@ -252,18 +252,17 @@
border-right: 1.5px solid currentColor;
/* type "such", hold, backspace (nebula-type, once); blink a finite number of times
(nebula-caret); then fade the whole thing out so it stops being distracting. */
/* blink ~7 times first (so you catch it even when the splash is skipped on refresh),
then type "such", hold, backspace, blink a few more, and fade away. */
/* blink ~4 times, type "such", backspace, blink ~4 more, then fade away. */
animation:
nebula-type 3s steps(4, end) 5.6s forwards,
nebula-caret 0.8s steps(1, end) 17,
nebula-term-out 0.6s ease-in 13s forwards;
nebula-type 2.2s steps(4, end) 3.2s forwards,
nebula-caret 0.8s steps(1, end) 11,
nebula-term-out 0.6s ease-in 8.4s forwards;
}
@keyframes nebula-type {
0% { width: 0; }
27% { width: 4ch; }
67% { width: 4ch; }
87% { width: 0; }
36% { width: 4ch; }
64% { width: 4ch; }
90% { width: 0; }
100% { width: 0; }
}
@keyframes nebula-caret { 0%, 50% { border-color: currentColor; } 50.01%, 100% { border-color: transparent; } }