Skip to content

Our standards

What every website and system we build is held to

Six standards, each with the published reference behind it and a project you can check. They apply to a QAR 8,000 site as much as to a booking system, because a customer cannot tell which one they are using when it fails.

Applies to
Every website and system we build
Last reviewed
October 2026
Check us
Ask on the first call

01 · Reliability

It keeps working, and it refuses bad data

The rules that matter are written into the database, not only into the code. A rule such as "this camera cannot be in two bookings at once" then holds for every screen, form and import, including the ones nobody has written yet. Automated tests run before every release, and an action left half-finished, such as a checkout someone abandons, has an ending decided in advance.

In the system behind Ottora Studio, overlapping equipment is refused by a database constraint, so the system accepts zero double-bookings, and an unpaid booking releases its slot after 15 minutes.

The Ottora Studio system

02 · Speed

Measured on a mid-range phone, against Google's thresholds

Pages are built ahead of time wherever they can be, so no server assembles them while a customer waits. We measure on a mid-range phone, because that is how most customers in Qatar meet a site, and against Google's Core Web Vitals: main content within 2.5 seconds, a response to a tap within 200 milliseconds, and a layout that does not jump.

The Masas site is 104 pre-rendered pages in English and Arabic. On a mid-range phone, Lighthouse scores it 94–95 for performance and 100 for accessibility, best practices and SEO. You can test any site, ours included, with Google's free PageSpeed Insights.

The Masas website

03 · Security

Access is decided by the database, not by the screen

Hiding a button is not a lock. The most common serious weakness in web applications is broken access control, first on the OWASP Top 10. So the database checks every request against the user's role and returns only the rows that role may read. Payment keys and passwords live in a protected store, never in the code, and every response carries security headers.

In Ottora Studio's admin dashboard, an admin without finance access gets 0 rows from the ledger, even querying the database directly. Its 16 modules each open only to the roles whose work it is.

04 · Usability and accessibility

Phones first, both languages, and usable by everyone

We design the phone screen first and widen it, not the other way round. We follow the W3C's Web Content Accessibility Guidelines 2.2: text with enough contrast to read outdoors, every action reachable by keyboard and screen reader, a label on every field, and buttons large enough to tap. Errors say what to fix, and a form keeps what the customer typed.

Arabic is designed right to left from the first layout, with its own typeface and copy written for Arabic readers, not an English page mirrored. The Masas site scores 100 for accessibility in Lighthouse. An automated score is a floor, not proof of full conformance.

Arabic and RTL websites

05 · Privacy and honest tracking

Consent first, then count enquiries

Analytics and advertising tags wait for the visitor's answer, and the site works the same if they decline. On corethreeweb.com, analytics waits for the consent banner. We collect only what a form needs, keep it where the client controls it, and measure the enquiry, not the page view: a form sent, a call made, a WhatsApp chat opened, recorded with the page and the search that led to it.

For Bushra Pharmacy, that meant counting 475+ qualified patient enquiries in 60 days across WhatsApp, calls and delivery apps.

Bushra Pharmacy

06 · Ownership

Yours, in your name, and ready to hand over

The domain, the hosting plan, the code and the data are in the client's name. We choose the hosting and set it up, then work with the access the client gives us. We build with widely used tools such as Next.js, Webflow and Postgres, document how each system is built and run, and leave content you can edit yourself.

Lanyardy has published 18 pages on its own through its CMS: 11 articles and 7 event case studies.

The Lanyardy website

07 · Check us

Ask us to show you, on the first call

Every result on this page links to its project. On a first call, ask us to show you any of them: the rule the database enforces, the score on a phone, the role that sees nothing. If we cannot show it, it does not belong on this page.

Websites start from QAR 8,000, or QAR 15,000 with a system behind them, as one-off projects.

What we offerThe work

Put your project to the same test

Fifteen minutes with the founders, your site or system on the screen.