seokopat

service · interface

> seokopat.render("brand")

Web Design

The site is the most looked at face of a brand. Built from a template it still loads, it just leaves nothing behind. That difference is the part we work on.

What makes a site good is not the number of effects. It is typography, spacing, hierarchy and speed. When those are wrong every added animation makes it worse; when they are right even a plain page looks expensive.

We do not treat design as separate from content. Page templates, heading hierarchy and internal linking are set up from the beginning so the site does not fall apart as it grows and SEO is not patched on later.

The same team designs and builds. That is why we do not produce layouts that look great in a design file and collapse in a browser; every screen is tested on real devices, with real content and real loading conditions.

01

Four pillars of the work

Brand language

Type scale, colour system, motion rhythm and component set are built for the brand. Buying a theme and changing its colour is not design, it is a costume.

Speed

Image and font loading strategy, removing unnecessary JavaScript, Core Web Vitals. Speed is not a later optimisation, it is the result of design decisions.

Content structure

Page templates, heading hierarchy, internal links and metadata. Search should be ready the day the site launches, not rebuilt three months later.

Accessibility and upkeep

Keyboard navigation, sufficient contrast, semantic HTML. Plus a structure you can update yourselves, so a text change does not require an email to us.

02

What we see most often

A theme was bought and the speed left

A plugin for every need; the page fires dozens of requests on load. On mobile the first meaningful content arrives seconds later and the visitor does not wait.

Nice design, no structure

Pages were drawn one by one with no template system. Adding a new page breaks the rhythm and the site slowly becomes a collection of unrelated screens.

Mobile was an afterthought

A layout designed for desktop cramps on a phone: headings overflow, buttons are too small for a thumb, forms are painful. Most of the traffic is on mobile.

The site launched and nobody can update it

Even a text change needs a developer. The site freezes, campaign pages never happen and the blog stays empty.

Images uploaded straight from the camera

Original files go directly onto the site. A single product page weighs several megabytes and the mobile visitor pays that bill.

03

Scope

Scope depends on the type of site. A corporate showcase and a large catalogue do not require the same work.

Design

  • Discovery, competitor review and sitemap
  • Design system: typography, colour, components
  • Homepage and critical template design
  • Motion and interaction language
  • Mobile layouts designed separately

Development

  • Built with Next.js and React
  • Reusable component library
  • Forms, search and filtering flows
  • Multilingual support
  • Analytics and conversion event setup

Performance

  • Image and font loading strategy
  • Core Web Vitals improvement
  • Measurement on real devices, not only lab tests
  • Page weight and request count audit

Launch and handover

  • Content entry and management structure
  • Redirect plan for old URLs
  • Launch checklist and go live
  • Team training, source files handed over
04

How we work

  1. 01

    Discovery and map

    We work out who you are talking to and what job the site has to do. The sitemap comes out of that, and design does not start before the map is clear.

  2. 02

    Design language

    Typography, colour and components get established. Approval happens on the language rather than page by page, which speeds up everything after it.

  3. 03

    Template production

    Critical templates are designed and built. Real copy goes in early, because approval given on placeholder text falls apart at launch.

  4. 04

    Testing

    Appearance, speed and accessibility checked on real devices. Forms, error states and empty states get tested too.

  5. 05

    Launch and handover

    We go live with redirects, analytics and a search checklist. Source files and code are then transferred to you.

05

Who this is for

Good fit

  • Brands that want out of the template look
  • Businesses whose site grew and lost its structure
  • E-commerce sites with speed and mobile problems
  • Brands repositioning or launching a new product family

Not a good fit

  • Work expected to be delivered in a few days
  • Projects where nobody will make time for content
  • Processes with no clear decision maker, where every screen goes to a separate approval
  • Engagements built on an expectation of unlimited revisions
06

What we watch

Whether the design works is not decided by taste. These are the things we look at.

Core Web Vitals field data: LCP, INP, CLSMobile and desktop conversion rateForm start and completion ratePage weight and request countExit rate on critical pagesAccessibility audit findings

This site is our own work

The continuous WebGL journey you see on seokopat.com was built by us. Where image weight has become a speed problem, Compresify steps in. Not every project needs this much; the real job is choosing the right dose for the brand.

07

How the engagement works

Scope and duration

We price by number of page templates; template logic is more predictable for both sides than an open ended page count. A typical corporate site runs six to ten weeks.

Team and communication

Designer and developer sit at the same table. You see work in progress on a live link and feedback is collected in one place.

Delivery and handover

Code, design source files and content management move to you. After that we can keep maintaining it, or you can.

08

Frequently asked

How long does it take?

A corporate site usually takes six to ten weeks. The biggest factor is not design but when the content is ready. If content exists, the timeline shortens.

Do you build on WordPress?

Our default is Next.js. If your team's habits or a specific plugin need call for WordPress we will build it, but we discuss the trade off first. Speed and maintenance cost sit at the centre of that decision.

Who writes the content?

Structure and briefs from us, copy from you or written together. We can take on the writing as well. We do not seek design approval on placeholder text; real copy changes the design.

Can I update the site myself afterwards?

Yes, that is the goal. Content areas and page structure are built so you can maintain them, and we run a short training session with your team.

Can you speed up my current site without a rebuild?

In most cases yes. Image and font strategy, removing unnecessary scripts and server settings get you a long way. If a rebuild is genuinely needed, we say so based on a measurable constraint.

Do you build e-commerce sites?

We do. Platform choice and product data structure get decided together with the e-commerce consulting side, and the design is built on top of those decisions.

Let us talk about your site

Send the current address and what bothers you about it. In the first conversation we will tell you whether it needs a redesign, a structural fix, or only speed work.

Related services