Web Development Projects

Terapys

Service: Corporate site with SEO and advertising.

Who it’s for: A neurolinguistics, speech therapy and learning practice in Querétaro.

Details: Custom design with their logo, colors and typography. Services, team, blog and patient reviews. A WhatsApp button on every page. It appears on Google for the services it offers. A Google Ads campaign that tracks every WhatsApp contact.

Result: 189 contacts in 90 days at MXN $56.65 per contact, versus MXN $107 on the 12-month average.

terapys.com (opens in a new tab)

Screenshot of the Terapys home page on desktop
Screenshot of the Terapys home page on mobile

BJFIT

Service: Corporate site.

Who it’s for: An information and communications technology company serving the public sector, with an office in Puebla.

Details: Custom design with brand identity. A page for each service (consulting, infrastructure, support and document management), contact and privacy notice. Fast, stable loading on mobile. Visible on Google for Puebla, Mexico City and Querétaro.

bjfit.com.mx (opens in a new tab)

Screenshot of the BJFIT home page on desktop
Screenshot of the BJFIT home page on mobile

Sourcing Solutions MX

Service: Corporate site in English.

Who it’s for: A sourcing and sales consultancy for the automotive industry in Mexico.

Details: One page per service (Sourcing, Sales, Network, Quality Assurance and Headhunting), profiles of the advisory team, mission and values, and direct contact by WhatsApp. Designed for clients abroad.

sourcingsolutions.mx (opens in a new tab)

Screenshot of the Sourcing Solutions MX home page on desktop
Screenshot of the Sourcing Solutions MX home page on mobile

Terapystore

Service: Online store.

Who it’s for: The Terapys Store shop, connected to terapys.com.

Details: Catalog by category, cart and secure payment. Its own logo and the same cheerful Terapys identity (colors and typography).

terapystore.com (opens in a new tab)

Screenshot of the Terapystore home page on desktop
Screenshot of the Terapystore home page on mobile

What we take care of when developing with AI

Building fast with AI is worth nothing if the site comes out heavy, inaccessible or insecure. These are the practices we apply on every project, backed by public documentation, and how we check them before launch.

Speed and page weight

Why it matters. A slow page is abandoned before it is seen. Google measures the experience with three signals (Core Web Vitals) and publishes its thresholds; we use them as goals on every project.

See the practices (4)
  • What we do
    No page builders or heavy libraries: native WordPress blocks and a custom theme; each page loads only the CSS and JavaScript it uses.
    How we check it
    Page weight and list of network requests. No libraries, fonts or images from third-party servers. Google measurement loads only if you accept.
    What you gain
    A site that loads only what it needs and is easier to maintain.
  • What we do
    Images in AVIF and WebP in two sizes, with width and height declared; lazy loading except the first visible image, which gets high priority.
    How we check it
    LCP and layout shift (CLS) measured on every view.
    What you gain
    The first screen appears quickly and the content doesn’t jump while loading.
  • What we do
    Fonts hosted on the site itself (WOFF2), showing fallback text immediately, with the headline font preloaded.
    How we check it
    No flashes or jumps while the typeface loads.
    What you gain
    Text is readable from the first instant and doesn’t depend on outside services.
  • What we do
    Measurable targets: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less.
    How we check it
    PageSpeed Insights tests on the published site.
    What you gain
    Measurable goals checked on the live site, not promises.

Functionality and quality

Why it matters. AI-generated code is produced very fast, and it can also leave mistakes just as fast. That is why every delivery is tested and reviewed by a person.

See the practices (5)
  • What we do
    A design that adapts to its container, not just the screen; checked at five widths, from 320 to 1920 pixels, with no horizontal overflow.
    How we check it
    An automated overflow test on every page.
    What you gain
    It looks good on phone, tablet and computer.
  • What we do
    Colors, typefaces and sizes defined in one place in the theme: one change applies to the whole site and nothing is left “by hand”.
    How we check it
    Theme review before each delivery.
    What you gain
    A brand change applies across the site with no manual touch-ups.
  • What we do
    Forms with a honeypot field against spam, with no reCAPTCHA or outside services, mandatory privacy consent and accessible error messages.
    How we check it
    Test submissions: valid, with errors and without consent.
    What you gain
    Less spam and error messages that make sense.
  • What we do
    A full backup and version control before each stage; the site is tested in a private environment, hidden from search engines, before it is published.
    How we check it
    Verified backup and a test environment set to noindex.
    What you gain
    No test error reaches your customers or Google.
  • What we do
    All AI-generated text and code is reviewed by a person; no figure is published without a source.
    How we check it
    Review before every delivery.
    What you gain
    Content you can trust and defend.

SEO and AI visibility

Why it matters. A site that can’t be understood can’t be found. A clear structure and explicit data help search engines and AI assistants interpret your pages.

See the practices (5)
  • What we do
    One H1 per page, headings with no skipped levels, and a title and description of their own on each page.
    How we check it
    Structure audit before launch.
    What you gain
    Every page says clearly what it is about.
  • What we do
    Multilingual sites with hreflang tags, canonical URLs and a sitemap for each language.
    How we check it
    Review in Google Search Console.
    What you gain
    Each person lands on the version in their language.
  • What we do
    Structured data (JSON-LD) for the organization, pages, articles and products.
    How we check it
    Google’s rich results test.
    What you gain
    Information that machines read without guessing.
  • What we do
    301 redirects from old URLs when we migrate a site, to keep its rankings.
    How we check it
    A list of old URLs against the new ones.
    What you gain
    You keep the rankings you already had.
  • What we do
    Content that answers questions directly (FAQs, lists, tables with headers) so search engines and AI assistants can understand it and use it in their answers.
    How we check it
    Each page reviewed against your customers’ real questions.
    What you gain
    Clear content that people, search engines and AI assistants understand alike.

Accessibility (WCAG 2.2, level AA)

Why it matters. WCAG 2.2 AA is the international accessibility reference. Meeting it improves the experience for everyone, not only for people with a disability.

See the practices (4)
  • What we do
    A contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text, measured automatically on every component.
    How we check it
    Zero contrast failures before launch.
    What you gain
    Text that is readable in sunlight, in low light and for tired eyes.
  • What we do
    Full keyboard navigation, visible focus, a skip-to-content link, tables with captions and headers, and the page language declared.
    How we check it
    A keyboard walkthrough of every page and form.
    What you gain
    The site can be used without a mouse and with a screen reader.
  • What we do
    Respect for the browser’s font size (measurements in rem) and touch targets of at least 24 by 24 pixels.
    How we check it
    A test with the browser’s font set to “Very large”.
    What you gain
    Large browser text is respected and it’s easy to tap on a phone.
  • What we do
    Animations turn off if the person asks for that in their system settings.
    How we check it
    A test with “reduce motion” turned on.
    What you gain
    No effect bothers someone who doesn’t want it.

Security and privacy

Why it matters. Your site and your data are yours. We build it so you can withdraw our access whenever you want and never depend on us.

See the practices (3)
  • What we do
    Domain, hosting, email and Analytics and Ads accounts always in the client’s name, with access the client can withdraw whenever they want.
    How we check it
    A list of accesses at handover.
    What you gain
    You own everything and can withdraw access whenever you want.
  • What we do
    Updates with prior testing, backups with an off-server copy and monitoring that the site is online (in the care plans).
    How we check it
    Monthly report.
    What you gain
    You hear about a problem before your customers do.
  • What we do
    Nothing from Google loads until you accept measurement, and you can withdraw it whenever you want.
    How we check it
    Review of network requests before and after accepting: zero requests to Google if you do not accept.
    What you gain
    You comply with what the law requires when collecting data.

Shall we talk about your site?

Tell us what you need. We’ll reply with a clear proposal covering scope, timeline and cost.