-
Why 67 of our tools jumped on load, and the one script that holds their place
Tools that build starting rows in a module script made the page jump on load. Measured heights, held until DOMContentLoaded, took CLS from 2.95 to 0.07.
-
Every post on this blog pointed at the same five posts
36 of 3,717 posts got every related-post link and 3,681 got none. Shared tags and title words now pick them, and 32 titles lost stray backslashes.
-
Five page checks were using one core out of four
Five page checks parsed 3,700 pages on one core. A process pool and two exact pre-filters cut them from 18.7 s to 4.5 s, same output.
-
204 posts that no other post linked to, and the one slot that fixes each
204 of 3,936 posts had no inbound related-post link. A balancing pass now gives each one by borrowing its best match's weakest slot.
-
One extra zero froze three of our planners. Here is what each loop was doing
Typing 100000 into one field froze three planner pages for over 30 s. An O(n²) loop, an O(H²) loop and a simulation; now each answers at once.
-
6,228 false alarms and three real ones: sweeping 8,939 pages at tablet widths
A sweep of 8,939 pages at tablet widths flagged 6,230; all but two were the checker measuring too early. The real bugs: default-width inputs in 1fr grids.
-
The Checkbox That Gave Way: 423 Squashed Boxes on Phone-Width Tool Pages
A phone-only min-width:0 on every input squashed checkboxes beside long captions to 3-11 px slivers on 287 pages. Two CSS lines fixed 421.
-
The finding you only see when a field is empty
Eight tool pages skipped from h2 to h4 only after an empty field or an edge value. Clicking Example never got there; changing each input did.
-
The header that jumped: one script moved, 135 of 507 page loads stopped shifting
A script at the end of each tool page stretched its header to full width after first paint. Running it inline cut shifting loads from 135 of 507 to 1.
-
The heading that only appears after you click
281 calculator and checker pages jumped from an h2 to an h4 once they drew a result. A static scan never saw it. A browser that clicks Run did.
-
The headline that was one line too tall for a small iPhone
After a shorter intro, the hub's search box still sat below the fold on 375 px and 320 px phones. A phone-only headline size and tighter gaps fixed it.
-
The search box below the fold
On a common Android phone our homepage search box sat below the first screen, behind a 13-line paragraph. Cutting what the page said again lower down fixed it.
-
The slow part was the promise, not the hash
Naming the offline cache meant hashing 26,184 files. Async reads took 3.8 s, plain sync reads 1.4 s, with identical hashes.
-
The tool's name comes first now: two bars moved below the heading on 171 bid calculators
On 174 bid calculators the first line was 'Save your rates once', not the tool's name. The bars now sit under the heading. The h1 moved up 128 px on phones.
-
The width nobody checks: five tools that scrolled sideways on a tablet
Every page here is checked at phone width. Swept at 820 px, five of 8,679 scrolled sideways by up to 477 px, all from the same CSS grid rule.
-
Two Bars That Couldn't See the Page: Lining Up 36 Tool Pages
On 36 of 168 tool pages the shop-rates and saved-bids bars sat 10 to 170 px off the heading below them. A 40-line aligner fixed all 168 at every width.
-
1073 beside 8,985: one way to write a count across the site
The research index printed "1073" beside "8,985". 26 counts on seven index pages had no thousands separator; one helper and a check fix it.
-
436 stories were filed under Tools
Every Hearth & Horizon and Saints by Candlelight page marked Tools as its section and led through Learning & practice. They now sit under Stories.
-
475 pages on the guides index were not guides
The guides index promised how a price is built, from free calculators. A fifth of its links were bedtime stories, videos and a demo abbey's About page.
-
A fade that says there is more: a scroll hint for 105 stuck result cards
Result cards that scroll inside now fade at the foot until you reach the end. It is pure CSS on a scroll timeline: 802 bytes, no handler, no layout change.
-
A sticky card in a CSS grid travels the whole grid, not its cell
On 83 calculator pages the sticky result card slid down over the FAQ or the proposal form below it. One desktop-only grid rule per page fixed all 83.
-
Our contrast check had never looked at dark mode
axe found 176 light-mode and 80 dark-mode contrast failures on our ten index pages. What caused them, and the check that now runs both colour schemes.
-
Our first Lighthouse run: the index pages, not the tools, failed accessibility
We ran Lighthouse on 16 pages of marisstella.app. All 11 flagship tools scored 100 for accessibility. The research and writing indexes scored 88 and 92.
-
Fixing links for 1,331 tools, 16 at a time
The site build fixed links and wrote sitemaps one tool at a time: 6.5 s. Split into two concurrent passes, 3.9 s, with byte-identical output.
-
Calling getComputedStyle on every element cost us 100 ms on a phone
A shared script asked every element for its overflow to find scroll boxes: 100 ms on a 4,204-element page. Reading the stylesheet rules first cut it to 8.
-
Our Guides page laid out 265,000 pixels before anyone scrolled
A 1,626-card index cut mobile blocking time from 883 ms to 50 ms with content-visibility, once the placeholder heights could never be too short.
-
Lighthouse blamed a 35 ms reflow on one line. Fixing it saved under 2 ms
A script added a style element after load and Lighthouse charged it 35 ms of forced reflow. Moving the CSS into a shared stylesheet saved 1.7 ms. Here is why.
-
98 of Our Tools Were Shipping in Times New Roman
A browser sweep of 1,344 tool pages found 98 in browser-default styling. All are fixed now, and a test stops a bare page from shipping again.
-
One "+ 1" made 352 blog posts skip a heading level
Desktop Lighthouse scored 100 everywhere. A mobile sample of other page types found 415 pages with a heading skip or a layout shift, fixed in three places.
-
A sticky card taller than the window hides its own bottom
On an 800 px window, 110 sticky result cards ran past the bottom edge while stuck, hiding their copy buttons. A capped height that scrolls inside fixed 101.
-
The Homepage Hero Stopped Jumping, and Three Speed Fixes That Didn't Work
The homepage's rotating audience line wrapped and moved the page on phones. It now holds its tallest height. Three speed ideas, measured, did not help.
-
Why our bid calculators jumped after they loaded, and the Lighthouse fix we didn't make
Median layout shift on 14 tool pages fell from 0.113 to 0.002. The bigger Lighthouse win, dropping module preloads, was a simulation artifact.
-
The Search Button That Sat on Its Own Row
From 721px up, every page but the hub put Search on a row of its own. A container query on the header bar fixed it, and no header got taller.
-
The site build was reading one folder at a time
Listing the built site's 25,196 files took 375 ms, one folder at a time. Reading sibling folders together: 200 ms, and 268 ms instead of 774 ms cold.
-
Three different Search buttons in one site header, and the one that replaced them
On a phone, marisstella.app's header drew Search as bare text, as a pill, or not at all, depending on the page. Now there is one pill everywhere.
-
A 70-character title limit, a post that broke it, and the check that said so
A post merged with an 80-character seo_title. The front-matter check flagged it, and the fix was one line. Why the limit exists and where it is enforced.
-
Australia's GST registration line: AUD 75,000 and 21 days, now stated up front
The GST registration checker now opens with the threshold, the deadline and the ATO source, with a test that keeps the figures in step with the calculator.
-
Every local build of the site still named the address it moved away from
The site moved to marisstella.app, but the build default stayed github.io, so local builds and nightly checks used an address that only redirects.
-
The Research Page Scrolled Sideways on a Phone, and 4,538 Pages Had No Guard
One long file path in a research card made /research/ 428px wide on a 390px phone. The real cause: site pages never got the reflow CSS tool pages had.
-
Social Security taxation, answered in the first sentence
The benefits-tax calculator now opens with the 50% and 85% rule, its source (26 U.S.C. 86, Pub 915) and a date, with a test tying figures to the code.
-
Two audits of 1,500 tool pages that found nothing wrong
We checked every free tool page for a disclaimer and for a no-JavaScript notice. Both came back clean, and why that was worth knowing.
-
The estimated tax penalty safe harbor, stated up front
The estimated tax penalty calculator now leads with the IRS safe harbor, sourced and dated.
-
The home office deduction page now answers first, with its source
The home office deduction calculator opens with a one-sentence answer, the IRS source and an as-of date, and a test ties its figures to the calculator.
-
The 2026 IRS mileage rate is two numbers, so the page now says so first
The mileage deduction calculator now opens with a sourced, dated answer: 72.5 cents a mile to June 30, 76 cents from July 1.
-
Do any two of our calculator pages share the same search snippet?
A new check compares the meta description of every venture page. Of 3,611 pages, none share one; the check now runs on demand.
-
A title-length lint moved from a nightly health check to every pull request
Posts over the title budget broke main_health twice in two days; the frontmatter check every PR already runs now catches them.
-
Twenty-one paste boxes had only a placeholder for a name
A sweep of 3,632 venture pages found 21 checker tools whose paste-here textareas were named only by their placeholder. Each now has an aria-label.
-
What the 401(k) plan fee calculator now says before anything else
The 401(k) plan fee calculator now opens with the plain answer: no law sets a maximum fee, and ERISA asks that fees be reasonable.
-
How much can you borrow from your 401(k)? The answer now leads the page
The 401(k) loan vs withdrawal calculator now opens with the statutory loan limit, its source and an as-of date, and a test ties the figures to the calculator.
-
Can leftover 529 money go into a Roth IRA? The page now says so first
The 529-to-Roth rollover calculator opens with the rule, its source and a date, and a test pins the dollar figure to the calculator.