Masuma
Client · Website
A made-to-measure site for a company that has cleaned, built and maintained workspaces since 2005.
Masuma has cleaned, built and maintained offices, shops and industrial sites since 2005. We rebuilt its website to load instantly, show up when someone searches for what it does and turn visits into quote requests.
Eleven pages generated at build time and served from Cloudflare’s network; a single Worker for the one thing that needs a server, the quote request; technical SEO end to end and a repository with tests, CI and documentation. The photos are the client’s own, as their crews took them.
- Client
- CIA. Mantenimientos y Suministros Azteca
- Since
- 2005, in Mexico City
- Built with
- Astro 7, TypeScript and Tailwind 4
- In production
- Cloudflare Workers, Turnstile and Resend
Static at the edge. A server only for quotes.
The whole site is generated at build time: Cloudflare serves each page as a file from the point of its network closest to whoever asks, without running any code. The only dynamic part is the form action, on a stateless Worker that uses nothing but web APIs.
GET A visit
- Cloudflare network
- Static file
- HTML, WebP and font, cached
POST A quote request
- Rate limiting
- Worker · zod
- Honeypot and timing
- Turnstile
- Resend
- Masuma’s inbox
- One URL per page
- Files like servicios.html and no trailing slash: canonicals, sitemap and links match, and /servicios/ redirects.
- Images at build time
- Every photo ships as WebP with srcset and sizes from the build, without paying for an image service.
- A self-hosted font
- Archivo variable served from the domain, preloaded and with a metric fallback: text doesn’t jump on load.
- Typed variables
- Public values are written at build time; secrets are read only by the Worker and never reach the browser.
Each service, its own page. Each page, its own data.
Someone searching for “office cleaning” isn’t looking for “remodeling”: each service has its own page, with what it covers, its projects and its FAQ. And each page tells Google what it is, where and for whom with structured data: the company, site, page and services linked together as a single entity.
What Google reads on this page
- Company GeneralContractor Masuma, with its address, hours, phone and service catalog
- Website WebSite masuma.mx, in Mexican Spanish
- Page WebPage Limpieza de oficinas e inmuebles en CDMX
- Path BreadcrumbList Inicio › Servicios › Limpieza de inmuebles
- Service Service Building cleaning in Mexico City, for corporate offices, industry and schools
- FAQ FAQPage Three frequently asked questions, each with its answer
- masuma.mx/servicios/limpieza-de-inmuebles Limpieza de oficinas e inmuebles en CDMX
- masuma.mx/servicios/obra-civil-y-remodelacion Obra civil y remodelación de oficinas en CDMX
- masuma.mx/servicios/mantenimiento-integral Mantenimiento integral de edificios en CDMX
- masuma.mx/servicios/suministro-de-bienes Suministro de materiales y mobiliario en CDMX
- A page sitemap and an image sitemap with the photos of each project
- robots.txt and llms.txt generated from the same data as the pages
- Titles of up to 60 characters and descriptions of up to 155, checked by tests
- A single canonical URL per page and the 404 kept out of the index
A quote request that gets through.
The form is the only thing that runs on a server, and we treat it that way: the same schema validates in the browser and in the Worker, bots are stopped in layers without asking anything of a person, and if the email doesn’t go out it says so and offers WhatsApp: it never fakes a send.
What the server answers
- A bot fills the hidden field 200 Fake success: nothing is sent
- Sent in under 3 s 200 Fake success: nothing is sent
- No Turnstile token 403 Rejected
- Fourth request in 10 s 429 Cloudflare cuts it off before the Worker
- A person 200 Email to the inbox, with an idempotency key
What you don’t see.
A company website gets attacked too. Every page ships with strict security headers and a policy that only runs the scripts it recognizes by their hash; analytics use no cookies and only run on masuma.mx, and the privacy notice follows Mexico’s 2025 data protection law.
On every page
- Every script carries its SHA-256 hash: an injected one won’t run CSP
- HTTPS only, and the browser remembers it for a year HSTS
- No one can put the site inside someone else’s frame frame-ancestors
- The browser never guesses a file’s type nosniff
- No access to camera, microphone, location, payments or USB Permissions-Policy
- Other sites only get the domain, never the path Referrer-Policy
- SEO on mobile Lighthouse
- 100
- Accessibility on mobile Lighthouse
- 100
- Tests on every change
- 39
- Tracking cookies
- 0
- Strict TypeScript, formatting and tests in CI on every push
- Tests for the schema, bots, Turnstile, the email and SEO
- Documentation by domain and a decision log
- Every push to main goes live; rolling back takes seconds
Measured on November 5, 2026.
Next case
Anter House