FIXED SCOPEone-off build
Ship an HTML5 product, end-to-end.
A defined product, a fixed price, a senior-only team. From RFC to launch in 8–14 weeks.
$15k–$30k
FIXED SCOPE
- Senior engineers only
- Fixed quote in week 1
- Code, infra, runbook — yours
High-performance frontends,shipped in HTML5.
We don't treat HTML5 as a fallback. Eight years of it in production — semantic markup that search engines actually reward, Canvas and WebGL that don't drop frames, Web APIs that replace native app features without the app store. The platform is more powerful than most teams use it. We use all of it.
- Semantic HTML
- Sub-1s LCP
- Web APIs
- Zero framework overhead
Why Entalogics for HTML5
Four things every HTML5
app actually needs.
Most teams treat HTML5 as the layer underneath their framework — something the bundler outputs and nobody reads. That's where performance, accessibility, and SEO get quietly destroyed. We treat the platform as the product.
Performance01
Sub-1s LCP, by construction.
Preloaded fonts, inlined critical CSS, deferred non-essential scripts, properly sized images with native lazy loading. No framework runtime between the browser and your content. HTML5 delivered correctly is the fastest frontend stack available — most teams just never deliver it correctly.
Component systems02
Web Components, not component soup.
Custom Elements, Shadow DOM, and the HTML Template element give you encapsulated, reusable components with zero runtime dependency. We build component systems that work in any framework, survive any future migration, and add exactly zero kilobytes of third-party JavaScript to your bundle.
State03
Browser APIs, not a state library.
History API for routing. Local Storage and IndexedDB for persistence. BroadcastChannel for cross-tab coordination. The browser ships a capable state layer that most teams replace with a 40kB library because they never learned what the platform provides. We know what the platform provides.
Type safety04
Typed Web APIs, no runtime surprises.
TypeScript's DOM typings are thorough — when you use them. Typed Custom Events, typed Web Component props, typed fetch responses validated at the boundary with Zod. Refactors that touch the DOM layer land cleanly because the compiler does the boring half of the review.
When HTML5, when not
HTML5 is a tool.
Not a religion.
An honest decision matrix. We'll tell you on the first call whether vanilla HTML5 is the right call for your problem — or whether a framework buys you something worth the cost.
PICK HTML5 WHEN
- Performance and SEO are the primary constraints — content sites, landing pages, documentation
- The product needs to work on low-powered devices or slow networks where framework overhead is measurable
- You're building embeddable widgets or Web Components that need to work inside any host application
- Long-term maintenance means zero framework upgrade risk — the platform doesn't break backwards compatibility
CONSIDER OTHERS WHEN
- Complex interactive UI with dozens of interdependent components — React or Vue will pay back the overhead
- Large team building a long-lived SaaS product — framework conventions reduce coordination cost at scale
- Real-time collaborative features — framework ecosystems have better tooling for this specific problem
WE SAY NO WHEN
- "We want to avoid frameworks because we heard they're slow." That's not an architecture decision — that's a rumour. We'll tell you honestly if a framework is the right call.
- "Build our SaaS dashboard in vanilla HTML5." We'll push back. The platform is capable — but the coordination cost at that complexity isn't worth it.
- "We need it in two weeks and the spec is still being written." That ship has sailed.
What we build with HTML5
Six product surfaces.
One quality bar.
The shapes of HTML5 work we ship most often. Each slots cleanly into your existing stack if you already have one.
- S01
Marketing & growth surfaces
Marketing & growth surfacesHigh-traffic landing pages, content sites, documentation. Semantic HTML5, structured data, edge-delivered, Lighthouse 100 by construction. The fastest path from content to indexed, ranking page.
HTML5VITESCHEMA.ORGVERCEL - S02
Web Components & design systems
Web Components & design systemsCustom Elements built to the platform standard — framework-agnostic, Shadow DOM encapsulated, ARIA-compliant. Components that work in React today and in whatever comes next.
WEB COMPONENTSLITSTORYBOOKTOKENS-STUDIO - S03
Canvas & WebGL experiences
Canvas & WebGL experiencesData visualisations, interactive graphics, game-adjacent UIs. Native Canvas 2D for charts and editors, WebGL for 3D and GPU-accelerated rendering. No wrapper library between your logic and the GPU.
CANVAS APIWEBGLTHREE.JSPIXI.JS - S04
Progressive Web Apps
Progressive Web AppsService Workers, Web App Manifest, Background Sync, Push Notifications. A PWA that passes the installability criteria, works offline on the critical path, and loads in under two seconds on a 3G connection.
SERVICE WORKERWORKBOXWEB APP MANIFESTVITE-PWA - S05
Internal tooling
Internal toolingReplace the spreadsheet. Replace the five spreadsheets. Lightweight, zero-dependency internal tools that don't need a framework and don't accumulate one over time.
HTML5VITETYPESCRIPTTAILWIND - S06
Embeddable widgets
Embeddable widgetsThird-party embeds, checkout widgets, comment systems, live chat. Shadow DOM isolation means your widget doesn't leak styles into the host page — and the host page doesn't break your widget.
WEB COMPONENTSSHADOW DOMVITETYPESCRIPT
The playbook
Patterns we
ship on repeat.
The HTML5 patterns that show up on almost every engagement. Not invention — convention, applied carefully.
P01
Semantic markup first
The right element for the right job. article, nav, main, dialog — not div all the way down. Semantic HTML is free SEO, free accessibility, and free document structure. Most teams throw it away without noticing.
P02
Typed contracts
Zod at every data boundary — API responses, form inputs, URL parameters, postMessage payloads. TypeScript's DOM typings used in strict mode. No any near the DOM.
P03
Cache-first data
Service Worker caching strategy matched to data volatility. Static assets at the edge. API responses stale-while-revalidate where staleness is acceptable. The network is optional on the critical path.
P04
Design tokens
CSS custom properties as the token layer — not screenshots, not hardcoded hex values. Light/dark, density, and brand variants fall out of a single token file. The design system and the running application share the same source of truth.
P05
Visual + integration tests
Playwright against real browser APIs — not a simulated DOM. Web Component interaction tests. Accessibility assertions in CI. Catches the regressions humans miss; runs in under five minutes.
P06
Progressive enhancement
Core functionality works without JavaScript. Interactivity layered on top. Users on slow connections, screen readers, and corporate proxy environments get a working product — not a blank screen.
Signature case
A marketing platform,
rebuilt from framework to platform..
A high-traffic B2C marketing platform on a legacy SPA — 5.8s LCP, a 1.6 MB JavaScript bundle for a site that was primarily content, and an SEO profile that hadn't recovered from a framework migration three years earlier. We rebuilt on semantic HTML5 with Vite, progressive enhancement, and edge delivery in 9 weeks. Without a content freeze.
Before
p75 LCP 5.8s · bundle 1.6 MB · Lighthouse SEO 61 · Core Web Vitals failing · 0 structured data
After
p75 LCP 0.78s · bundle 48 kB · Lighthouse SEO 100 · Core Web Vitals passing · full Schema.org coverage
- p75 LCP improvement−87%
- JavaScript bundle−97%
- to fully migrated9wk
- shipped regressions0
Engagement shape
Eight to ten weeks
to a measurable ship.
A typical HTML5 engagement, end-to-end. We migrate route by route — never flag-day. The current product keeps shipping while we work.
- W01
Audit + RFC
Two senior engineers across the codebase. Bundle analysis, render-blocking inventory, semantic markup audit, Core Web Vitals baseline, structured data gaps. You leave week one with a ranked, dollarized RFC — not a list of Lighthouse complaints.
- W02–03
Foundation + first route
Semantic HTML baseline, critical CSS inlined, font loading strategy, one production route migrated end-to-end. Real Core Web Vitals in your Search Console — not a local Lighthouse run on a fast machine.
- W04–08
Migrate by route, not flag-day
Route by route. Old and new coexist behind a reverse proxy. Your content team keeps publishing — we don't ask for a freeze to rebuild your frontend.
- W09+
Cleanup + handoff
Delete the old. Component library documented. Storybook for Web Components. Playwright integration tests. Runbook handed to your team — or we stay on retainer.
Stack
Tools we
reach for first.
Picked by problem, not by resume. Happy to slot into your stack — but greenfield, this is the default.
- PlatformHTML5 · Web Components · Custom Elements · Shadow DOM · Service Workers
- BuildVite · esbuild · Rollup · PostCSS · Lightning CSS
- LanguageTypeScript (strict) · Zod · ESLint + biome
- StylingTailwind · CSS Modules · vanilla-extract · CSS custom properties
- TestingPlaywright · Vitest · Web Test Runner · Storybook · axe-core
- InfraVercel · Cloudflare Workers · Netlify · AWS CloudFront · Datadog · Sentry
Engagement
Three ways
to work with us.
No hourly retainer that bills for "thinking time." Pick a lane that matches your stage; everything is fixed-quote or transparently rated.
DEDICATED TEAMmonthly
Hire dedicated HTML5 engineers.
Embedded engineers in your Slack, your Linear, your standups. A scaled pod of senior HTML5 engineers, augmenting your team. Pause, resize, end with 30 days' notice.
$5k / eng / mo
PER ENGINEER
- Same senior bar as fixed-scope
- Embedded in your team
- Founder-direct escalation
ENGAGEMENTcustom
Strategic HTML5 partnership.
A long-term partner for product orgs that need both delivery and judgement — design system, performance program, hiring help.
custom
PROCUREMENT-FRIENDLY
- Multi-quarter roadmap
- Architecture & hiring partner
- Procurement-friendly paper
FAQ
Sharp questions,
straight answers.
Framework vs platform, Web Components, interactivity — the questions we get on every HTML5 discovery call.When performance and SEO are the primary constraints. Content sites, landing pages, documentation, and embeddable widgets don't need a framework runtime — they need fast, semantic, well-structured HTML. If your page's job is to be found, loaded, and read, the platform beats every framework on those metrics by default.
For a shared design system — yes, and often better. Custom Elements are framework-agnostic, which means the same button component works in your React app, your Vue admin panel, and your static marketing site. If your components are consumed across multiple stacks, Web Components eliminate the "which framework version" problem entirely.
With the platform APIs that most teams don't know exist. Custom Events for component communication, the History API for routing, IndexedDB for persistence, BroadcastChannel for cross-tab state. For genuinely complex UI — a rich text editor, a drag-and-drop canvas — we reach for a focused library like Lit or Shoelace rather than a full framework. The goal is the smallest dependency footprint that solves the actual problem.
Yes. The engineers who write the RFC are the engineers who ship the code. No handoff to a junior team after scoping. No account manager in the middle. You have direct access to the people doing the work throughout the engagement.
Yes. We've worked inside CSS Modules, BEM, Tailwind, vanilla-extract, and fully custom token systems. We adapt to your conventions — we don't ask you to rewrite working CSS to fit our preferences. If your design system needs work, we'll say so in the RFC. If it doesn't, we build on top of it.
Founder-direct
Tell us whatyou're building.
Thirty minutes with the founder. We'll bring a senior HTML5 engineer, the relevant playbook, and a candid read on whether the platform is the right tool — or whether a framework earns its keep for your specific problem.