Core Web Vitals
Images in WebP or AVIF, caching and lazy loading. Live sites are watched against the "good" thresholds: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1.
- Home
- Technology & standards
Technology & standards · How we build
The right tool for each project, and the same checks every time.
Our stack is chosen per project during scoping: most corporate sites are server-rendered PHP with TypeScript, while stores and business software add Laravel, React and PostgreSQL where they help. What does not change from project to project are the quality gates: speed, accessibility, security headers, structured data and automated checks before release.
Checked on every build
SpeedLighthouse report at handover, target 90+
AccessibilityWCAG 2.2 AA audit in the higher plans
SecurityHSTS, CSP and spam protection without CAPTCHA
SearchConnected JSON-LD structured data and sitemaps
How we choose
Constraints first, frameworks second.
A company website, an online store and an ERP system have different needs for traffic, update frequency, integrations and long-term maintenance. Applying one stack to all of them is convenient for the developer and expensive for the client.
The language, database and hosting set-up are decided during scoping by the engineer responsible for the project, after looking at expected scale and the cost of maintaining the system over years. The choice and its reasons are explained to you before work starts.
The ruleNo JavaScript framework where plain server-rendered pages are faster, and no heavy database where a simpler one will do.
- Choice explained in plain language, with alternatives
- Maintenance cost weighed alongside build cost
- No templates, page builders or third-party plugins
Typical stacks
What we usually reach for, by type of project.
A starting point, not a fixed menu. The final choice depends on your scope and is confirmed in the written proposal.
| Project | Typical stack | Why |
|---|---|---|
| Corporate website | PHP 8.3, TypeScript, MySQL, Nginx, Cloudflare | Fast server-side rendering, search-friendly pages and no unnecessary JavaScript |
| Online store | PHP with Laravel, React, MySQL, Redis, Docker | A solid back end for basket and payment flows; React for live filtering and stock |
| ERP, CRM and business software | PHP with Laravel, React, PostgreSQL, Redis, WebSocket | Strong indexing for reports, live notifications and complex forms |
| Integrations and middleware | Node.js, TypeScript, Redis, Docker | Low-latency services, rate limiting, webhooks and queues |
| Modernisation | The existing language, API-first | Staged replacement with the strangler fig pattern, so operations continue |
Quality gates
What every build has to pass.
Which checks apply depends on the plan and scope; each is listed in the quote so you know what you are getting.
Structured data
Connected JSON-LD for organisation, services, products and FAQ, plus XML and image sitemaps, llms.txt and IndexNow.
Accessibility
WCAG 2.2 AA audit, semantic HTML, keyboard navigation and layouts tested on mobile first.
Security headers
HSTS and Content Security Policy, CSRF protection on forms and multi-layer spam protection without CAPTCHA.
Pre-release checks
Automated SEO audit, broken and orphan links, keyword cannibalisation and structured data validation before each release.
Migrations
A 301 redirect map for every old address, each one verified after launch.
For business software
Standards for systems your team uses every day.
Role-based permissions
Each role sees and changes only what it should, checked on the server.
Change history
A record of who changed what, and when, down to field level where needed.
PWA
An installable app that can keep working offline when the connection drops.
Daily backups
Automatic daily backups, with security and penetration tests in the higher plans.
Measured, not claimed
What our tests reported on real projects.
Figures from handover-day test outputs of anonymised projects. Live values can change over time.
652End-to-end test checksBusiness software that replaced a paper ledger for a cold storage operator.
1,034Automated checks, 0 errorsA classifieds platform with government system integration.
22/22Lighthouse scores of 100Every speed measurement on handover day of a local SEO project.
355/355Old URLs verifiedA site migration in which every address reached its new page.
At handover
What you receive when the work is done.
- Speed reportA Lighthouse report for key pages on mobile and desktop, with a target of 90+.
- Core Web Vitals baselineThe starting values for LCP, INP and CLS, then monitored on the live site.
- Redirect mapFor rebuilds, the full list of old and new addresses and the result of each check.
- Acceptance recordA signed record of what was delivered, closing the final milestone.
Questions
Questions about our technology
Do you always use the same framework?
No. Corporate sites are usually plain PHP with TypeScript because they load faster without a heavy front-end framework. Stores and business software often use Laravel, React and PostgreSQL. The choice is made during scoping and explained to you.
Where is our site or system hosted?
Kodem develops your software, hosts it on servers in Türkiye and keeps it up to date. The source code stays with Kodem. Your domain is registered in your name, and your content and data are always yours.
Will our site score 100 in Lighthouse?
Not necessarily, and we do not promise it. We share a Lighthouse report at handover with a target of 90+, and monitor Core Web Vitals on the live site. Scores also depend on content and third-party scripts added later, so we report what we measure.
How do you handle accessibility?
Pages use semantic HTML and support keyboard navigation. Higher plans include a WCAG 2.2 AA audit, and the result is shared with you.
Can you build in English and Arabic?
Yes. Each language has its own address and hreflang tags, and the Arabic version uses a genuine right-to-left layout. This site is built that way.
What happens before each release?
Automated checks run for SEO issues, broken and orphan links, competing pages and structured data. On business software, test suites run as well, and a failed check stops the release.
Ask why we would build it the way we would.
Send a short description of your project. On a free video call we explain the stack we would choose, the alternatives, and what it costs to maintain.