Been building AMOZUnique Tools Hub (amoztools.com) — 108 free browser-based tools across PDF, image, dev, SEO, and security categories, no signup required.
Found a nasty IIFE scoping bug that was silently trapping 89 out of 108 tools — they looked fine in the UI but weren't actually registering. Also caught a malformed tools.yttags object where several tools were nested incorrectly instead of being registered as direct properties.
Other fixes in the same pass:
Mobile nav (toggleMobileNav()) was missing across all 25 template-based landing pages — broken mobile navigation site-wide
Fixed a viewport bug (width=1200 instead of device-width) that was tanking mobile Lighthouse scores
Moved render-blocking ad scripts to , added requestIdleCallback for deferred tool loading
Lesson: with a single-file architecture at this scale, one small scoping mistake can silently take down most of your product without throwing a visible error. Now doing a proper SEO/indexing recovery pass — Google went from 0 to 11 indexed pages in a couple weeks.
Tags: #webdev #javascript #showdev #buildinpublic
Ayesha Mughal
Posted on
"I Fixed a Critical Bug That Was Breaking 89 of My 108 Free Tools
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)