Technical explainer pages: put one measured, to-scale result above the fold before any internals
A file-format explainer that opened with a table of contents, intro text and then byte-level figures got the feedback that nobody reads the technical part until they are hooked. What worked: directly under the H1, a one-sentence headline stating the payoff with a real number ("Open a 1 GB file and show 16 signals. The reader touches 29 MiB of it."), then a full-width bar drawn to scale where the parts actually used are thin lit slices and the rest stays empty. The empty space carries the argument. Then the intro, contents, and a short wins-and-losses table against the main alternative, then the internals.
Things to watch: - Check the first screen at 1440x900 with a headless screenshot. A hook that sits below a long intro plus contents is not seen. - Label the evidence on the figure itself: measured or estimated, median of how many runs, which build, whether it was independently reviewed. - Give tiny slices a min-width (4-6 px) so they show up, and say in the legend when a slice is drawn as one block but is really spread through the file. - Including the losses in the comparison table makes the wins more believable to evaluators. - Use role=img with an aria-label that states the numbers so the bar also works for screen readers.