"Our website looks beautiful now, but inquiries have somehow dropped"—this is a frequent concern we hear from SMBs after redesigning corporate websites or submission forms. The aesthetics are modern, and animations glide smoothly. Yet looking under the hood reveals that form completions have declined compared to before. In most cases, the culprit is not visual design, but rather that "over-engineering reliant on JavaScript drops users on weak connections or low-spec devices."
Recently, an article published by an overseas engineer titled How building an HTML-first site doubled our users overnight sparked significant discussion on Hacker News. When an external vendor built an application form for a public service using React, it turned into an unusable bundle of loading spinners and global JavaScript state, leading to its withdrawal within three days due to user complaints. After rebuilding it with an HTML-first approach (building functional HTML first, using JS only as an enhancement), the number of users completing applications doubled overnight. Furthermore, the operator's analytics tools failed to capture this increase—because JS-based analytics tags fundamentally cannot track users who abandon a site due to JS execution failures. Supporting corporate websites through custom development, we view this not as a "framework debate," but as a direct revenue issue: "Is excessive JavaScript secretly eroding incoming inquiries?"
Why inquiries drop even when a site "looks like it works"
When a site depends on JavaScript, a hiccup in network connectivity, device hardware, or browser extensions breaks the experience for the user by rendering a blank screen or making the submit button unresponsive. The visitor simply thinks, "this site is broken," and silently leaves.
What makes this insidious is that this drop-off leaves no trace in site analytics. Because most analytics tools, including GA4, operate via JavaScript, visitors unable to execute JS are never counted as sessions. Consequently, while metrics appear healthy, a predictable volume of prospective clients gets stuck on the other side of the screen. When the original author noted that "analytics tools had no idea where the growth came from," it struck right at this structural blind spot.
Visitors to SMB websites are not all equipped with high-speed connections and cutting-edge devices. Older smartphones, poor cellular coverage, and restricted corporate firewalls all amplify the cost of heavy JS. On high-stakes user funnels like inquiries and applications—where losing someone directly translates to lost revenue—reducing reliance on JS offers immense returns.
HTML-first does not mean "abandoning JS"
Contrary to common misunderstandings, HTML-first is not an anti-JavaScript philosophy. It is a matter of priority: "first build HTML that functions completely without JS, then layer JS on top to enhance the experience." Standard <form> tags can submit without JavaScript, and page navigations function natively through browser capabilities. When this foundation works, users can at least submit forms and read content even if JS execution fails.
| Dimension | JS-dependent (SPA style) | HTML-first |
|---|---|---|
| Initial render | Waits for JS download and execution | HTML displays immediately |
| Form submission | Fails completely if JS breaks | Submits reliably via standard forms |
| Analytics blind spot | Users experiencing JS failures cannot be tracked | Server logs capture drop-offs |
| Weak connections/devices | Experience degrades severely | Functions relatively robustly |
| Maintenance | State management tends to become complex | Straightforward architecture, easier handovers |
This concept is by no means novel. In GH Media articles such as Will Jamstack Become the New Standard? (GH Media) and Custom Development: Improving Perceived Speed with Streaming SSR (GH Media), we have explored strategies for avoiding excessive JS to boost perceived responsiveness. Think of HTML-first as applying this mindset specifically to inquiry and conversion funnels.
"HTML-first rebuilds" offered in custom development
In our custom development services, rather than immediately undertaking a complete site overhaul, we adopt an approach of "measuring where and how many users are being lost, and rebuilding only the highest-impact funnels."
First, visualizing "lost prospects"
The first step is diagnosis rather than rebuilding. By reconciling server-side access logs (independent of JS) with form "starts" versus "completions," we estimate drop-offs likely caused by JS failures. For a professional services client, abandonment between starting and submitting an inquiry form was unusually high; investigation revealed an input assistance script executing during data entry was freezing on older mobile devices. Replacing this with standard forms and server-side validation noticeably restored completion rates. For fundamentals of form optimization, see also How to Approach Form Input Optimization (EFO) (GH Media).
Rebuilding high-impact conversion funnels first
Once diagnostics pinpoint bottlenecks, we prioritize rebuilding funnels closest to revenue (inquiries, applications, bookings) with an HTML-first architecture rather than reworking the entire site. A single functioning form often impacts revenue far more than decorative touches on the home page. For isolating why inquiries drop off, see our overview in How to Fix Websites That Fail to Generate Inquiries (GH Media).
Retaining form input on the backend
In the referenced case study, an example was noted where a user began a form and completed it one month later. This was possible because partial inputs were retained in server-side sessions. In custom development, especially for lengthy forms, we incorporate architectures that allow users to resume where they left off after abandoning, preventing lost business opportunities.
Criteria for rebuilding — not everything should be pure HTML
HTML-first is best suited for corporate websites centered on information delivery, applications, and inquiries. Conversely, building post-login administration panels or dashboards that involve complex interactivity entirely in HTML is unnatural; those interfaces are better served by JS (and SPA architectures where appropriate). Exercising sound judgment here is the hallmark of custom development expertise.
| Well-suited | JS engineering appropriate |
|---|---|
| Corporate and service introduction sites | Post-login business web applications |
| Inquiry, application, and booking forms | Screens requiring real-time updates |
| Recruiting and IR information pages | UIs with complex drag-and-drop actions |
| Landing pages and marketing campaign sites | Internal dashboards |
A clean separation—"making public sites robust with HTML-first, while keeping post-login experiences rich"—is the pragmatic sweet spot for most SMBs. When considering migrations from SPAs, please also read Revisiting SPA Transitions Using the Navigation API (GH Media).
Common pitfalls to avoid
First, assuming that "speeding up" means adding more JS optimizations. Before adding compression or lazy loading, question whether you are overly dependent on JS in the first place. Second, relying exclusively on analytics metrics. Because users experiencing JS failures vanish from client tracking, you cannot spot lost conversions without auditing server-side logs. Third, attempting to rebuild every page indiscriminately. Business impact varies by conversion path, so prioritize sections closest to revenue. For building solid foundations for page speed, refer to Core Web Vitals Improvement Guide (GH Media).
Conclusion — "Never dropping users" matters more than "looking like it works"
Even if a site appears to run smoothly, if heavy JavaScript silently turns away visitors on weak connections or older devices, inquiries and revenue are lost accordingly. Worse, those losses never show up in analytics reports. For teams supporting corporate websites through custom development, our "rebuild" service—first visualizing lost visitors via server-side measurement, then reconstructing revenue-critical funnels with HTML-first—is our premier offering for reviving sites where inquiries dropped following a redesign.
If you are wondering why inquiries dropped after a renewal or suspect your form conversion rates are sluggish, please feel free to reach out via our contact form. We can start with a diagnostic review of lost conversions.
Sources
- How building an HTML-first site doubled our users overnight（mohkohn.co.uk）
- Building an HTML-first site doubled our users overnight（Hacker News）
- HTML performance optimization（MDN）
- Will Jamstack Become the New Standard? (GH Media)
- Custom Development: Improving Perceived Speed with Streaming SSR (GH Media)
- How to Approach Form Input Optimization (EFO) (GH Media)
- How to Fix Websites That Fail to Generate Inquiries (GH Media)
