La Ventana, Baja California Sur, México. [email protected]

Thoughts on making a better website.

Practical perspectives on planning your pages, expressing your brand, and bringing a website from idea to launch.

Website Planning

Plan a URL Structure That Survives the Next Redesign

Page addresses get copied into bookmarks, links, and search results that outlast any one design. Here is what a 2024 Pew Research Center study found about how often web pages disappear, and how to plan a URL structure that will not need rewriting the next time the site changes.

Windware StudioRead the Article
Website Redesign

Keep a Staging Site Out of Search Before a Redesign Launch

A redesign in progress can turn up in search results with placeholder copy, or launch carrying the block meant for staging. Here is what Google, Bing, and the IETF's robots.txt standard say about keeping a staging site out of search, and what to change on launch day.

Windware StudioRead the Article
Website Redesign

Set a Performance Budget Before a Website Redesign

Redesigns tend to make pages heavier, one hero video and font weight at a time. A performance budget agreed before design starts gives the team a shared limit, so speed is decided in the brief rather than discovered after launch.

Windware StudioRead the Article
Web Design

How Many Fields Should a Contact Form Ask For?

Contact forms grow field by field until they feel longer than the conversation they start. Here is what checkout research shows about form length, how a question protocol keeps service inquiry forms short, and which fields to require, hide, or drop.

Windware StudioRead the Article
Website Planning

Write a Website Project Brief With Measurable Goals

A website brief that only lists pages and a launch date leaves success undefined. Here is how to write measurable goals into the brief—purpose, a few outcomes, and metrics you can check after launch—drawing on UK service planning guidance and US digital-experience policy.

Windware StudioRead the Article
Website Redesign

Usability Testing a Website Redesign: How Many Users Is Enough?

Five users is the most quoted number in usability testing, and the most misread. Here is what the research behind it actually shows, where later studies push back, and how to plan usability testing for a website redesign as small, repeated rounds instead of one test before launch.

Windware StudioRead the Article
Web Design

Don't Let Color Carry Meaning Alone on Service Pages

Red for errors, green for included, a colored word for a link: service pages often let color carry meaning on its own. WCAG's Use of Color criterion and research on color vision deficiency explain why that fails some visitors, and how to pair color with text, shape, or position instead.

Windware StudioRead the Article
Web Development

Stopping Form Spam Without CAPTCHAs That Block Real Inquiries

A CAPTCHA on a contact form asks every prospective client to prove they are human before they can ask a question. Research on modern CAPTCHAs and W3C accessibility guidance point to a better default for service sites: layered, mostly invisible spam protection, with a challenge only when the evidence calls for one.

Windware StudioRead the Article
Web Design

Body Text Size and Line Length for Readable Service Pages

Reading studies, Baymard's usability testing, and the GOV.UK Design System point toward body text that is not too small and lines that stay under about 75 characters. Here is what the evidence supports, where it stops, and how to set line length and text size on a service website.

Windware StudioRead the Article
Web Development

INP on Service Websites: Keeping Menus and Forms Responsive

Interaction to Next Paint (INP) measures how quickly a page shows a response after a tap, click, or key press. The 2025 Web Almanac shows that mobile responsiveness still trails desktop, especially beyond the homepage, so here is how service sites can keep menus, accordions, and inquiry forms responsive.

Windware StudioRead the Article
Web Development

Autocomplete Attributes That Let Browsers Fill Inquiry Forms

The HTML Standard's autocomplete tokens tell browsers what each inquiry-form field expects. Chrome's field data, an independent autofill study, and WCAG 1.3.5 show why the right tokens help visitors finish, and why the wrong ones do more harm than leaving them out.

Windware StudioRead the Article
Website Redesign

Native HTML Before ARIA in a Website Redesign

The 2026 WebAIM Million found that home pages using ARIA averaged more detected accessibility errors than pages without it. W3C's own guidance explains why: in a website redesign, start with native HTML elements and add ARIA only where HTML has no equivalent.

Windware StudioRead the Article
Web Development

Subresource Integrity for Third-Party Scripts

MDN and the W3C SRI specification explain how integrity hashes stop unexpected CDN or third-party script changes; the 2025 Web Almanac shows adoption is rising, while full script coverage on a typical page remains thin.

Windware StudioRead the Article
Web Design

HTML Landmarks for Skimmable Service Pages

Visual layout alone does not give assistive technology a map of your service page. W3C ARIA practices and MDN show how HTML landmarks—banner, navigation, main, complementary, contentinfo—make regions skimmable and keyboard-reachable.

Windware StudioRead the Article
Web Development

Lazy-Load Images Without Hurting LCP

Native lazy loading saves bandwidth on service pages—but web.dev and HTTP Archive data show that applying loading="lazy" to the hero or LCP image delays discovery and slows the paint visitors notice first.

Windware StudioRead the Article
Website Redesign

Redirect Maps Before Changing Service URLs

When a redesign renames service pages, bookmarks and search results still hit the old URLs. Google Search Central and MDN explain how a URL mapping plus permanent 301/308 redirects preserve visitors—and why a blanket homepage dump is the wrong shortcut.

Windware StudioRead the Article
Website Redesign

Content Inventory Before a Website Redesign

A redesign that starts in Figma without a content inventory inherits forgotten pages and conflicting offers. How GOV.UK’s large-scale audits and the Province of British Columbia’s inventory guidance help service sites decide what to keep, merge, or retire before visual work begins.

Windware StudioRead the Article
Web Design

Meaningful Alt Text for Service Photography

Service photos earn trust when they show real work—but only if the text alternative matches the image’s purpose. How WCAG 1.1.1, the W3C WAI Images Tutorial, and WebAIM’s alt-text guidance help you write alternatives that inform rather than clutter.

Windware StudioRead the Article
Web Development

HTTPS and Mixed Content for Service Sites

Serving a contact form over HTTPS is not enough if images and scripts still load over HTTP. How web.dev’s HTTPS rationale and MDN’s mixed-content rules help service sites keep the padlock meaningful.

Windware StudioRead the Article
Website Planning

Link Text That Names the Destination

“Learn more” and “click here” force visitors to guess. How NN/g link-writing research and WebAIM’s link-text guidance help service pages name destinations in the anchor itself.

Windware StudioRead the Article
Website Planning

Service Page Titles That Earn the Search Click

Google and Bing both rewrite weak titles and invent snippets when yours are vague. How Search Central’s title-link and meta-description guidance—and Bing’s caption rules—help local service pages earn the click.

Windware StudioRead the Article
Website Planning

Open Graph Tags for Service Page Shares

When someone pastes your service URL into a chat or feed, the preview is often the first pitch they see. How ogp.me’s required tags and Meta’s image guidance keep that card accurate.

Windware StudioRead the Article
Web Development

Skip Links That Bypass Repeated Navigation

Keyboard users should not tab through every header link before reaching your offer. How WCAG 2.4.1 Bypass Blocks and the GOV.UK skip-link pattern give service sites a reliable first focus stop.

Windware StudioRead the Article
Website Planning

404 Pages That Recover Lost Visits

A missing URL is normal on a living service site. Plan a custom 404 that explains the miss, offers search and next steps, and still returns a real HTTP 404—following NN/g error-message principles and Google’s soft-404 guidance.

Windware StudioRead the Article
Web Development

Responsive Images for Service Site Layouts

A single full-size photo for every viewport wastes bandwidth and can slow LCP. How srcset, sizes, and picture—backed by MDN, web.dev, and the 2024 Web Almanac—fit a service website’s heroes, galleries, and cards.

Windware StudioRead the Article
Web Design

Non-Text Contrast for UI Components

Passing text contrast is not enough. WCAG 1.4.11 requires 3:1 contrast for control boundaries and states, and the GOV.UK Design System shows how focus styles stay readable on any background.

Windware StudioRead the Article
Web Development

Reserve Space Before Content Shifts

Unexpected layout shifts make pages feel unstable. How Cumulative Layout Shift is measured, what web.dev recommends, and what the 2024 Web Almanac shows about progress on the live web.

Windware StudioRead the Article