- @type
- Service
- @id
- /en/services/web-design/#service
- serviceType
- Web Design + Development
- provider
- /#org
- areaServed
- Istanbul Q406 · Turkey Q43 · Europe Q46
- availableChannel
- ServiceChannel · /en/contact/ · tr en de
- hasOfferCatalog
- OfferCatalog · 5 Offer
- audience
- Audience · audienceType
- url
- /en/services/web-design/
- DELIVERABLEShasOfferCatalog › Offer × 5in schema
- Editorial design + type system
- Multilingual architecture (TR · EN · DE)
- Motion choreography — reduced-motion included
- Accessibility: AA baseline
- Performance: built to LCP < 0.8s
- EVIDENCEObservation × 3in schema
- Largest contentful paint on three client sites: 532–764 ms (budget 800 ms)November 16, 2026 · Playwright cold load, 1440×900, 5 runs · Case sheets
@id variableMeasured value observationDate /isler/fersan-tekstil/#olcum-lcp Largest Contentful Paint 764 ms 2026-11-16 /isler/karcem/#olcum-lcp Largest Contentful Paint 552 ms 2026-11-16 /isler/mikro-yazilim-destek/#olcum-lcp Largest Contentful Paint 532 ms 2026-11-16
- WHO IT IS FORaudience.audienceTypein schema
- By corporate web design we mean, whatever the size of the company, a site that speaks several languages, is touched by several teams and has to live for years.
- NOT FOR—not in schema · human only
- We are not the right fit for a site of a few pages whose content is not ready yet and that has to launch within weeks; an off-the-shelf platform does that job at lower cost with the same result.
PROCESS
How does the web design process work?
Discovery + scope
Goals, content and technical ground are set; a written document fixes the scope.
Art direction
Concept, type and motion language; no production without approval.
Build
Static HTML + GSAP/Lenis; performance budgets applied from the start.
Measure + handover
Accessibility and speed audit; documented, maintainable delivery.


MEASURED DIAGRAMS
Largest Contentful Paint — live projects
Layout shift — three measured values
JavaScript weight — weighed on every build
WHY THIS WAY
Why not a CMS
We answer this question by measuring. What decides how fast a page opens is the number of bytes the browser has to download and run before the first paint. A plugin architecture makes those bytes unmanageable: every plugin brings its own styles and scripts, none of them knows the others' budget, and nobody sees the total. This site’s measured values: the stylesheet is 29.0 kilobytes compressed, libraries 36.8 kilobytes, its own code 24.1 kilobytes, third-party scripts zero.
Being static has a cost too, and we do not hide it: when content changes, a build command has to be run, and there is no admin panel. This trade-off is not right for every project. For a news site that publishes several times a day it is the wrong decision. For a corporate site, a portfolio or a service site it is the right one, because content changes rarely while speed and maintenance cost matter all the time. The full list of trade-offs is in a separate guide.
We measure performance at handover
We write the budget at the start of the project and measure it at the end. The first two thresholds sit below Google’s “good” limit: Largest Contentful Paint 0.8 seconds — Google says 2.5; layout shift 0.05 — Google says 0.1; Interaction to Next Paint 200 milliseconds, the same as Google’s limit. In the live measurement dated October 27, 2026, real-user LCP on this site’s slowest page was 616 milliseconds and the worst layout shift was 0.0005; we repeat the measurement after every release.
We take the figures from a test suite that runs on every change. Today the suite runs 1561 measurements, and part of it looks directly at performance: shift during scrolling is calculated separately with session-window logic, the animation frame budget is measured, and the JavaScript total is checked byte by byte. If a budget is exceeded, the build does not pass silently; the test turns red. We have written up performance as a whole and how the budget is set separately.
Accessibility is included in the price
WCAG 2.2 is the version the W3C published on 5 October 2023, and the Turkish Presidential Circular of 21 June 2025 takes level A as the reference for public institutions' websites. In this build the baseline is AA, and it is not priced separately. Measured values: body text gives 15.54:1 contrast against the paper background, more than twice the AAA threshold of 7:1. The focus ring gives 7.66:1. Touch targets are at least 44 pixels.
Treating accessibility as an extra rests on the assumption that it can be added later. When we measure, the assumption proves wrong: contrast is a colour decision, focus visibility is a style decision, keyboard order is a markup decision. All three are made at the design stage; left for later, the decision already made has to be undone. We explain what is what and the difference between the levels separately.
What the handover includes
We hand over the entire code and content source. The package contains three things: a documented file structure, a build pipeline that runs with a single command, and the verification suite itself. The last is the most important, because even after the site changes hands you can measure whether a claim is still true. There is no locked panel, no mandatory subscription and no layer whose source you cannot see.
Why this build is the way it is comes down to one sentence: an improvement that cannot be measured does not count as done. The same discipline appears as principles on the approach page, and on the services overview as the way the three services draw on a single set of decisions. If a design idea does not fit the budget, it is dropped, and the reason it was dropped is written down.
SCOPE
What does custom website development include?
Corporate web design: who it is for
By corporate web design we mean, whatever the size of the company, a site that speaks several languages, is touched by several teams and has to live for years. At that scale what decides is the contract: design tokens, schema at template level, and audits that run before release. We built this site itself under that contract.
Premium and custom web design — why no template
The reason to choose custom web design is that it can be measured. A ready template is fast on day one and heavy in month three: unused scripts, components that cannot move, accessibility that breaks. In this repository, premium web design means a budget line: we start by writing the JS budget and critical CSS, and defend both with a guard.
Custom website development: multilingual architecture
On a three-language site the cost accumulates in architecture, not translation: URL structure, x-default, the language switcher and schema translations. That is exactly why custom website development is chosen: these layers cannot be added later and have to be built on day one. The example is live on this site: three languages, a reciprocal hreflang cluster, one generator.
For manufacturers and exporters
Sites that carry a product catalogue, certificates and a quote flow have rules of their own: product information on the page rather than in a PDF, every market in its own language, a sale that starts with a request for quotation. The details are on the B2B websites page.
Speed as a separate engagement
Every new site ships with a performance budget. If you already have a site that is slow, speed can be a job of its own: we trace why pages are slow for real visitors and fix it at the source — Core Web Vitals optimization.
LOCATION: ISTANBUL
Istanbul, TR — remote by default; on site when it matters.
Related
FREQUENTLY ASKED QUESTIONS
We set the price by scope in a written quote; we do not publish a package list. Three variables carry the cost: how many templates, how many languages, how many third-party systems. The same content in one language and in three is two different projects: language count grows the architecture more than the translation.
Higher build cost, lower cost of ownership. A ready theme is fast on day one and heavy in month three: unused scripts, components that cannot move, accessibility that breaks on update. In a custom build we write the budget first and defend it with a guard.
Yes, multilingual architecture is part of the build: a separate URL tree per language, reciprocal hreflang, x-default and a language switcher. Translation itself is a separate item: you supply the text, or we add translator coordination to the scope.
Usually yes. The audit first says what is possible on your existing stack; image formats, critical CSS, script budget and cache headers rarely need a rewrite. If the gain is not worth it, we say so with numbers.
We treat WCAG 2.2 AA as the baseline and do not price it as an extra: AA contrast, visible keyboard focus, ≥ 24 px touch targets, and a full alternative flow for reduced motion. We audit state by state and do not rely on an automated tool alone.
Static HTML, vanilla JavaScript and GSAP; no CMS. Content lives in JSON files and the generator prints the site from them — so a content change goes through a file, not a panel, and so does its version history.
Yes. Text and image sources sit in plain files; making a change and running the generator is one command. If you have no developer, an update retainer can be added — but you are never tied to a locked panel.
We transfer all code and content sources to you; you are not tied to a locked panel or a subscription. The handover package includes repository access, setup notes and the measurement tools.

