-
24 research programme pages now open with what each one studies, not the same line
Every research programme's findings page had the same generic dek and meta description. Each now opens with the opening sentences of its own registry summary.
-
The tools at the foot of each page were the next four in the alphabet
Each tool page links to four related tools. In big categories that meant alphabetical neighbours: 2,974 of 5,512 links shared no word with the page. Now 14 do.
-
A button with no sentence: the Saved bids band now says what it is for
On 168 bid and quote calculators, a first-time visitor saw a lone grey Saved bids button. It now opens with seven words that fit beside the button on a phone.
-
Seventeen tool pages on the blog now say what the tool does
All 17 tool project pages on the blog opened with one generic sentence. Each now leads with its llms.txt summary, and so does its meta description.
-
ShootFlow's page said it planned renders. It has rendered them for weeks
ShootFlow's page still led with 'plan deliverables' and hid 12 raw formats in one 377-word bullet. It now says what the offline pipeline does.
-
Fifty-five characters was too many: the shop-rates line on a phone
On 118 bid calculators, two bars above the form took 132 px on a phone. A 30-character sentence, picked by a fit test on every page, cuts it to 85 px.
-
The home page tool pictures were too small to read; now they show the answer
The home page hero showed whole tool pages at 300 px, text 3 px tall. Each card now shows a close crop of the drawing or table: 1.8x larger, 36% fewer bytes.
-
The blog filed 415 bedtime stories under Tools
Saints' bedtime stories and science fiction showed a 'Tools and projects' badge on the blog. A Stories topic now holds 415 of them.
-
On 49 tool pages the header started at the very edge of a phone screen
On 49 of 1,351 tool pages the header logo and links touched the left edge of a phone screen. A padding rule meant for another layout was the cause.
-
79 pages told visitors they needed JavaScript to calculate. They had nothing to calculate.
The build's own embed box and search form put a false 'needs JavaScript' banner on 79 pages. Fixed, plus a RAW support page for ShootFlow.
-
A Link Is a Name, Not a Search Title: 2,296 Footer Links Shortened
Every tool page on the site links four related tools. Most printed the other tool's whole search title, tagline included. Now they print its name.
-
A fix for one page's chips crushed another page's
Making the blog's topic chips one sideways row on a phone also caught the podcast index, whose links squeezed into 105 px pills. One selector fixed it.
-
The site passed 10,000 pages and stopped telling search engines about them
IndexNow takes at most 10,000 URLs a request. Our announcer refused rather than batch, so every deploy's notice failed quietly. It batches now.
-
Ninety-eight page numbers under a blog index, and the five that matter
The blog's pager listed all 98 pages. It now shows the first, last and nearby pages, with the full list one tap away in a closed details element.
-
The blog's Tools topic was full of testing and SEO posts
Red-team, polish and SEO posts filled the blog's 'Tools and projects' topic. Two new topics now hold 416 of them; Tools drops from 2,876 posts to 2,462.
-
Seeing what a product ships when the live site is out of reach
Quality audits had to load the live site to rule out URL defects the deploy fixes. A one-second local copy of each product now does that.
-
Seven pages offered to embed a tool they did not have
The site build put an 'Embed this tool on your page' box on 1,368 entry pages. Seven had no tool on them. The box now needs a control to embed.
-
61 tool pages put the site header flush against the phone's edge
On a phone, 61 of 1,366 tools drew the site header flush against the screen edge. The build now reads each tool's CSS and adds a 16px gutter.
-
The blog's topic filters took six rows on a phone
Ten topic chips wrapped to 275 px above the first post on a 390 px phone. One sideways row with an edge fade gives back 237 px.
-
Nine blog topics, and no page a search engine could find for any of them
The blog files about 4,860 posts under nine topics, but a topic was a JavaScript filter. Now each has its own page, title, description and sitemap entry.
-
1,068 tool breadcrumbs ended in a sales line or a question
The trail on 1,068 tool pages ended in a search title like '— free, private, in your browser'. It now uses the name each tool declares.
-
On a phone, 93% of tool breadcrumbs cut off the tool's own name
At 390 px, 1,272 of 1,365 tool pages showed 'Home › long category › Actions Ch…'. The category now shrinks first, and 1,305 names fit.
-
The footer said "like this one" under a watch face
Tool footers said 'like this one: everything runs in your browser' on 28 pages with nothing to run. Now the line needs a control on the page or its tool.
-
Answer leads under a hundred words: three trimmed, and a check that keeps them short
Three of 55 answer-first leads ran past 100 words. Trimming them to the fact, its source and its date saved 46 to 118 px on a phone; a test now caps every lead.
-
Twenty-Five Pages Were Showing Their Markdown
A sweep of the built site found raw backticks, asterisks and link brackets on 25 pages. Four renderer gaps caused most of it; check.mjs now fails on it.
-
192 pages had drop-downs that cut their own words in half
A native select can't wrap, so long options get cut mid-word. A browser check found it on 192 of 606 tool pages; one shared CSS rule fixed the worst kind.
-
84 tools whose drop-down choices were longer than their column
A field whose longest choice doesn't fit half the form now takes the whole row. Cut drop-down choices on laptops went from 83 to 2 on the 84 tools that changed.
-
Eight bid calculators that hid their own choices behind the arrow
Eight bid calculators showed 25 to 40 px of each drop-down's choice on a laptop. Rows that wrap took clipped selects at 1,280 px from 55 to 0.
-
178 tools whose settings grid cut its own drop-downs
Settings grids of four 228 px columns cut long drop-down choices. Widening each grid's columns for its longest choice took laptop cuts from 442 to 149.
-
Four tax answers, read again from the source the day they went up
Four calculators now open with a sourced, dated answer: 2026 mileage rates, the $3,000 nanny-tax line, $42 FUTA and the EU's EUR 10,000 OSS threshold.
-
The nexus tracker's form, 545 px closer on a phone
Three paragraphs sat between the nexus tracker's answer and its form. One sentence and a row of links moved the file input from 1,712 to 1,167 px on a phone.
-
One request was five thousand pixels tall
The custom development page printed every word of each request's running log. Clipping the list and folding the log cut the page by 4,240 px on a phone.
-
A shortlist link that keeps its question
The ranker's 'find my top k' mode got the exact top 3 of 20 right 12 times in 16, against 4 for the full order. Its link dropped the question. Now it doesn't.
-
One footer link, 1,111 research pages, 2.24 to 1
The dark footer band on every research project page drew its repository link in a light-mode blue at 2.24:1. One CSS rule fixed all 1,111 pages.
-
Nine blog posts printed their subscripts as HTML tags
Nine posts showed subscript tags and HTML entity names as text. The blog's renderer now keeps typed entities and paired sub/sup tags, and nothing else.
-
Ten questions a pairwise ranker answers better than a score sheet
Quick Pick now has ten ready lists, from team goals to a free MaxDiff-style pain-point ranking, plus a hub. What each replaces, and what it does not do.
-
The Contrast Check Was Reading the Wrong Wall
axe-core flagged pale text in our sticky result panels at 1.01:1. It was fine. Measuring twice separated 236 false findings from a real 1.5:1 table header.
-
The Get it built form's research menu showed HTML entity names in 50 choices
Fifty research choices on the Get it built form read like market’s. One decode fixes them; a site-wide check now catches it in any menu, title or heading.
-
A Headline Three Pixels Into the Header: Fixing 120 Tool Pages at Once
On 120 of 1,354 tool pages the headline sat 0 to 2 px under the site header, or 3 px into it. One CSS rule caused it; the fix gives 16 px back.
-
AI Bookkeeper had 48 guides: half in one sentence at the top, half in the footer
33 guide links sat in one header sentence and 15 more in the footer. Now all 48 are in one grouped section, and the import box is 256 px higher on a phone.
-
Our clothing design studio's header listed its tools twice and still missed ten
The studio's intro carried two near-copies of a 40-link list, pushing the design box 1,613 px down a phone. Now it starts at 527 px, with all 50 tools listed.
-
Etsy's fees and the federal garnishment limit, stated in one sourced paragraph
Two tool pages now open with the answer, its source and the date checked: Etsy's $0.20, 6.5% and 3% + $0.25, and the $217.50-a-week garnishment floor.
-
Five tax and sales-tax pages now answer the question in their first sentence
The economic nexus tracker and four 2026 deduction tools now open with a sourced, dated answer; a test ties each figure to the calculator code.
-
Four more tools that opened with a wall of links
The league schedule generator named 28 guides in its intro. It and three other tools now open with four buttons and the form; the guides moved lower.
-
Making the sourced answer look like one
55 tool pages open with a one-sentence answer, its source and an as-of date. It looked like any other paragraph; one shared CSS rule fixed all 55.
-
Sole trader or limited company in 2026/27: the company never came out ahead
At £50,000 profit a UK sole trader keeps £40,268 and a one-director company £37,994. On a £1,000 grid from £10k to £300k the company never wins. And a bug fix.
-
Ten Copies of One Pill: Moving a Repeated Component Into the Shared Stylesheet
Ten tool pages had each copied the same jump-row CSS, and the copies had drifted. One shared rule with custom properties replaces them, with no visible change.
-
The blog's filters now look like one set of controls
The blog's Tag and Sort menus were 28 px tall under a 46 px search box, laid out differently on a phone. They now share its height and one layout.
-
The eBay calculator's first box was 1,940 pixels down on a phone
Our marketplace fee calculators opened with a paragraph naming every comparison and guide, so the first input sat two screens down on a phone. Now about one.
-
The last two pages that jumped on load, and why their fixes were different
A retainage calculator and a shed designer still scored about 0.2 CLS. One moved a section in a grid, one filled a 641 px strip late. Both are now near 0.