Website Design for Nigerian Architects: Portfolio That Performs

Architecture is the one professional service where the portfolio genuinely is the pitch. A prospective client scrolling through your projects is forming a judgement about taste, competence and whether you understand the kind of building they want.

The trouble is that the portfolio is also the technical problem. Most Nigerian architecture websites are built as if every visitor is on office broadband, and then quietly lose the visitor who opened the site on a phone with a weak signal. This guide covers how to solve both halves, plus how to qualify enquiries so that meetings are worth having.

What an architecture website is really for

Three audiences, three different needs.

The private client building a house. Usually building once, often anxious, frequently uncertain about what an architect does and what it costs. They want to see completed work that resembles what they imagine, understand the process, and know roughly what engaging you involves. They are as interested in reassurance as in aesthetics.

The developer or corporate client. Assessing whether you can handle their building type and scale. They look for comparable projects, delivery capacity, consultant coordination experience and evidence you have worked through Nigerian approvals and construction realities.

The professional peer and collaborator. Engineers, quantity surveyors, contractors and other architects. They judge from the quality of the drawings and the precision of the descriptions, and they refer work.

A portfolio alone serves only the first audience, and only partially. What converts is a portfolio plus process plus proof of delivery. Beautiful renders with no built work behind them are quickly identified by anyone with experience.

The portfolio problem: heavy images on Nigerian mobile data

This is the decision that separates architecture websites that work from those that do not. A typical render exported from visualisation software is several megabytes. Twelve of them on a homepage produce a page that costs a visitor real money in data and takes an uncomfortable time to appear.

The practical targets. Aim for a homepage that fully loads in a few seconds on a mid-range Android phone on a typical mobile connection. In practice that means keeping the initial page payload modest, with large images loading only as the visitor scrolls.

The techniques that matter, in order of impact:

1. Serve modern image formats. Modern formats such as WebP and AVIF typically produce far smaller files than JPEG at equivalent visual quality, with a JPEG fallback for older devices.
2. Serve the right size for the device. A phone does not need a 3,000-pixel-wide image. Responsive image sets let the browser choose an appropriate version instead of downloading the desktop one.
3. Lazy-load everything below the first screen. Images further down the page load as the visitor reaches them, so a visitor who leaves early never pays for them.
4. Compress deliberately. Renders and photographs tolerate meaningful compression before a viewer notices. Test on a phone screen, not a 27-inch monitor.
5. Limit the hero. One strong image at the top, not a rotating slider of six. Sliders multiply the payload and almost nobody watches past the first slide.
6. Use a content delivery network. Serving images from edge locations reduces latency for Nigerian visitors.
7. Avoid autoplay video backgrounds. They are the single most expensive element you can put on a page, and on a weak connection they simply fail.
8. Thumbnail grids at genuinely small sizes. A project index needs recognisable thumbnails, not full-quality images scaled down in the browser.

Keep a high-quality path for the people who want it. Serious clients and peers may want to see detail. Provide a larger version on click or a downloadable project sheet, so the default experience stays light while the option exists.

How to Make a Website Load Faster in Nigeriarticle 040: How Website Speed Affects Nigerian Businesses explains why it converts.

How to structure a project page that wins work

A gallery shows what a building looks like. A project page should show how you think, because that is what a client is buying.

A structure that works:

• Project identity. Type, location, approximate size, status, year, your scope.
• The brief. What the client wanted, in one short paragraph.
• The site. Constraints that shaped the design: plot dimensions, orientation, access, drainage, neighbours, ground conditions.
• The response. Two or three design decisions and the reasoning behind them. This is the section most practices omit and the one that most demonstrates competence.
• Images in sequence. Approach, exterior, key spaces, one or two details. Six to ten images, ordered as a walk-through rather than scattered.
• Drawings. A clean site plan or floor plan, redrawn for web legibility. Never a screenshot of a full construction drawing.
• Delivery. Consultants involved, construction status, and whether you supervised.

Confidentiality and client privacy come first. Where a residential client does not want their home identified, publish without the name and without the precise location, and consider omitting images that identify the property from the street. Get written permission before publishing any private residence in identifiable detail.

Distinguish built work from unbuilt proposals clearly. Labelling competition entries, concepts and unbuilt schemes honestly costs nothing and protects your credibility; presenting renders as completed buildings destroys it when someone asks to visit.

Qualifying enquiries before the first meeting

Architects lose enormous amounts of time on meetings with people who have no site, no budget and no timeline. The website can filter without being off-putting.

Ask five things on the enquiry form:

1. Project type: residence, commercial, institutional, interior, renovation.
2. Location: state and area, and whether the land is already acquired.
3. Stage: idea, land acquired, survey done, approvals started, building underway.
4. Intended construction budget range, as a band rather than a figure.
5. Target timeline.

Budget bands are the sensitive one, and they are also the most useful. Framing matters: explain that the construction budget shapes the design approach and that the question helps you advise properly. Most serious clients answer.

Publish a process page. Many private clients in Nigeria do not know what stages an architect delivers, what drawings they receive, or when payments fall due. A clear page covering briefing, concept, developed design, approval drawings, construction documentation and supervision removes confusion and reduces the number of calls that begin with "how does this work?".

Explain fees in principle. Professional fee scales and practice rules affect what you may publish, so confirm the current position with ARCON and your professional body. What you can almost always do is explain how fees are structured, what stages they cover, and what is excluded, so that a prospect arrives with realistic expectations.

Offer a paid first consultation where appropriate. A modest, clearly described consultation fee filters casual enquiries and signals that your time has value. Many Nigerian practices find this reduces volume and raises quality.

Credentials, registration and professional conduct

Architectural practice in Nigeria is regulated. Registration status and practice conduct rules affect both what you may claim and how you may promote the practice.

• State the registration status of the practice and of each architect exactly as held, using the correct terminology.
• Name the professional bodies you belong to and the grade of membership.
• Avoid superlative and comparative claims about other practices.
• Do not publish another practice's work, even as inspiration, without attribution and permission.
• Where images were produced by a visualisation studio or photographer, credit them.
• Confirm current advertising, promotion and fee publication rules with the Architects Registration Council of Nigeria and the Nigerian Institute of Architects before publishing anything commercial.

Clients increasingly verify registration before engaging. Making your status easy to find is a conversion feature, not a compliance chore.

What changes for Nigerian architects

Diaspora clients are a significant market. Nigerians abroad building family homes and investment properties often select an architect entirely online, having never met them. That raises the bar on the website: they need to see built work, understand the process, judge responsiveness, and have confidence in supervision while they are not in the country. Say explicitly if you work with clients abroad, and describe how you report progress.

Instagram brings the audience, the website converts it. Many Nigerian practices build a following on social media and then lose the serious enquiry because there is nowhere to assess depth. Treat social as discovery and the site as the place where a client verifies you. Website vs Instagram for Nigerian Businesses.

Clients often arrive mid-process. Land bought, a builder already engaged, foundations sometimes started. A page on renovation, remedial work and taking over part-built projects captures a real and underserved search demand.

Approvals are a genuine client worry. Building approval processes vary by state and are a frequent source of anxiety and delay. A page explaining, in general terms, what approval involves and what you handle is highly valued. Tell readers to confirm current requirements with the relevant state planning authority, since rules and fees change.

Phased construction is normal. Many Nigerian private clients build over several years as funds allow. A practice that explains how it designs for phasing is speaking to reality rather than to an idealised project.

Trust concerns run deep. Stories of abandoned buildings, disappearing professionals and poor supervision shape expectations. Real photographs of your team, a physical office address, registration details and a clear contract process address this more effectively than any design flourish.

Local search has specific patterns. Enquiries cluster around area names, such as Lekki, Ikoyi, Gwarinpa, Asokoro, Enugu GRA or Port Harcourt. Where you genuinely work in those areas, say so on relevant pages rather than sprinkling city names everywhere.

Example (hypothetical): a six-person practice in Lekki

The following is a hypothetical scenario used for illustration only. It is not a Linestech client.

A six-person architectural practice in Lekki designs private residences, small commercial buildings and interior fit-outs. Its website presents 18 projects as one long scrolling gallery with no text, and a contact form asking only for name, email and message.

The symptoms. The homepage carries eleven full-resolution renders and takes an uncomfortably long time to appear on a phone. Enquiries are frequent but poor: many have no land, no budget and no timeline. Two diaspora enquiries went quiet after asking how supervision would work, a question the site never answered.

The rebuild. An image pipeline converting all project images to modern formats with responsive sizes, lazy loading below the fold and a single hero image. Eighteen project pages restructured around brief, site, response, sequence and delivery, with built and unbuilt work clearly labelled. A process page covering the stages of an architectural commission. A page on working with clients abroad, including progress reporting and supervision arrangements. An enquiry form with project type, location and land status, stage, budget band and timeline. Registration details in the footer and on the about page.

Indicative budget. ₦1,700,000 for design, build and the image pipeline, plus practice time rewriting the project narratives.

What the practice measures. Homepage load time on a mid-range phone, proportion of enquiries with land already acquired, proportion supplying a budget band, and enquiry-to-consultation conversion. Fewer total enquiries with a higher proportion worth meeting is the intended outcome, and it is measurable.

What an architecture website costs in Nigeria

Indicative 2026 ranges. Actual quotations vary with project count, image preparation, design depth, functionality and vendor. Compare two or three written quotations on identical scope.

Recurring costs. Domain ₦3,000–₦30,000 per year, hosting ₦20,000–₦120,000 per year for shared hosting or ₦150,000–₦800,000 per year for cloud hosting with heavy media, maintenance ₦20,000–₦150,000 per month or an annual retainer, plus a CDN and storage where image volume is large.

The hidden cost is photography. Professional photography of completed buildings is what separates a convincing portfolio from a folder of renders. Budget for it project by project as buildings complete, and agree usage rights with the photographer in writing.

Building it: a practical sequence

1. Step 1: audit the portfolio honestly. Which projects are built, which are unbuilt, which you have permission to publish, and which you would rather not be known for.
2. Step 2: get permissions. Written consent from private clients before publishing identifiable residences, and credits agreed with photographers and visualisers.
3. Step 3: write eight to twelve project narratives. Brief, site, response, delivery. An architect must write these; a copywriter can only tidy them.
4. Step 4: prepare images. Select six to ten per project, sequence them as a walk-through, redraw one plan per project for web legibility.
5. Step 5: specify the image pipeline before design. Formats, responsive sizes, lazy loading, compression targets, CDN. This is a build requirement, not a later optimisation.
6. Step 6: write the process and fees-in-principle pages. Confirm what you may publish with your professional body first.
7. Step 7: design and build. Test every page on a mid-range Android phone on mobile data, not only on a desktop.
8. Step 8: set up the enquiry flow. Five qualifying fields, an automatic acknowledgement stating your response time, and a route into whatever you use to track enquiries.
9. Step 9: maintain. Add a project at each completion, replace renders with photographs as buildings finish, and review load performance twice a year.

Mistakes to avoid

Uploading renders straight from the visualisation export. It is the single most common cause of an unusably slow architecture website in Nigeria.

Presenting unbuilt work as built. It damages credibility permanently with exactly the professional audience that refers work.

A gallery with no words. Images show taste; narrative shows judgement. Clients hire judgement.

A rotating hero slider. Heavy, rarely watched past the first image, and it delays everything else on the page.

Publishing private residences without consent. A privacy and professional problem, and an avoidable one.

An enquiry form with three fields. It guarantees meetings with people who have no site and no budget. Five fields cost you nothing but unserious enquiries.

Ignoring the process question. Private Nigerian clients frequently do not know what an architect delivers or when fees fall due. Silence on this costs commissions.

Forgetting attribution. Uncredited photography and visualisation work creates disputes and looks careless.

Conclusion

An architecture website in Nigeria succeeds when it is visually convincing and technically light. The practices that get this right treat the image pipeline as a build requirement rather than an afterthought, write project pages that explain design decisions instead of displaying pictures, label built and unbuilt work honestly, and use five qualifying questions to protect their own time.

Curate rather than upload everything. Get written permission before publishing private homes. Explain the commission process, because most private clients genuinely do not know it. Confirm what your professional body allows before publishing anything about fees. A professional build in the ₦600,000 to ₦2,500,000 range covers this, and the photography budget is what keeps it convincing over time.

If your practice needs a portfolio site that stays fast on mobile data while showing work properly, Linestech designs and builds performance-focused websites for Nigerian firms and can set up the image pipeline as part of the build.

Frequently asked questions

How many projects should an architecture website show?

Between eight and twenty, curated rather than exhaustive. Show the work you want more of, and include enough variety to demonstrate range without diluting the impression. A practice known for residences should not bury them behind six unbuilt commercial concepts.

Should we publish renders or only completed buildings?

Publish both, clearly labelled. Renders communicate intent and are legitimate for unbuilt or in-progress work. What matters is that a visitor can tell immediately which is which, because implying that a rendering is a completed building is the fastest way to lose professional credibility.

How do we keep image quality high without a slow site?

Serve modern formats such as WebP or AVIF, generate several sizes so phones receive small versions, lazy-load anything below the first screen, compress with testing on a phone screen, and offer a larger version on click for visitors who want detail. The quality loss at sensible compression is imperceptible on a phone.

Is a WordPress site enough or do we need a custom build?

A well-built content-managed site is right for most practices, because you need to add projects yourself. What matters more than the platform is whether the build includes a proper image pipeline. Many template portfolio themes look excellent and perform poorly, so test performance before committing.

Can we publish a client's house on our website?

Only with written permission, and preferably without the exact address. Some clients will allow interior images but not exterior, or images but not the location. Ask at handover, record the answer, and respect it. Where consent is refused, publish the project with generalised details or leave it out.

How do we attract diaspora clients?

Show built work, explain the full commission process, describe how you supervise construction and report progress to a client who is abroad, publish clear contact routes including video call scheduling, and respond quickly. Trust is the barrier, and specificity about supervision is what removes it.

Should we show our fees?

Check the current rules with ARCON and the Nigerian Institute of Architects first. Even where publishing figures is not appropriate, you can explain fee structure, the stages covered, what is excluded and how payment is phased, which is what most private clients actually want to understand.

What is the best way to handle renovation and part-built project enquiries?

Give them a dedicated page. A large share of Nigerian enquiries involve land already bought, a partially completed structure or a build that has gone wrong. A page that explains how you assess and take over such projects captures demand that most practice websites ignore entirely.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• MDN Web Docs — web platform reference
• Core Web Vitals — web.dev
• Cloudflare Learning Center