nathaniel@dalencon:~/dalenconlancaster$
Back to the portfolio

Live · dalenconlancaster.com

D’Alençon LancasterLegal & Financial Services

The platform of a legal and financial firm based in Rianxo (Spain): a public website presenting its eleven practice areas and success stories, a private area where each client follows their case, and the admin panel that runs it all. Three applications with separate access, designed and built by me.

dalenconlancaster.com
clientes.dalenconlancaster.com
apps: website, client area and panel
3
practice areas
11
documented success stories
4
service languages
3

The platform, inside

Real screenshots of the live website.

  • Eleven practice areas

    Eleven practice areas

    From business accounting to insurance and usury: each area has its own page, plus a way in for anything that does not fit.

  • Success stories

    Success stories

    A carousel of real resolved cases, each with its own page.

  • Client area

    Client area

    Sign-in with an ID or tax number and password, access requests and password recovery, on its own subdomain.

On mobile

The same website, adapted to every screen: real screenshots on a phone.

dalenconlancaster.com on mobile
dalenconlancaster.com on mobile
dalenconlancaster.com on mobile

Measured in production

The dalenconlancaster.com home page, measured on 4 November 2026 with the browser’s own tools.

Total weight
104KB
Requests
7
External dependencies
0
Frameworks
0
  • HTML13 KB
  • CSS14 KB
  • JavaScript7 KB
  • Fonts68 KB
  • Images2 KB
  1. D'Alençon Lancaster104 KB22× lighter
  2. Average website (mobile)2,311 KB

Average website: 2,311 KB and 70 requests on mobile, according to HTTP Archive’s Web Almanac 2024.

  • HTTP/3 + Brotli compression
  • Zero third-party requests: no CDN, no analytics, no Google Fonts
  • Security headers: HSTS, CSP, nosniff, X-Frame-Options, Referrer and Permissions
  • Strict CSP: everything from its own domain, no inline scripts
  • Alt text on 100% of images (5/5)
  • Fonts served from its own domain
  • Structured data: LegalService, FinancialService, Person, WebSite, WebPage
  • Canonical URL and 10 Open Graph tags
  • Sitemap with 8 URLs
  • Full semantic structure: header, nav, main and footer
~ — curl

$ curl -sI https://dalenconlancaster.com

HTTP/3 200

strict-transport-security: max-age=31536000

content-security-policy: default-src 'self'; script-src 'self'; style-src 'self'; font-src 'self'; img-src 'self' data:; connect-src 'self'; form-action 'self'; frame-ancestors 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests

x-content-type-options: nosniff

x-frame-options: SAMEORIGIN

referrer-policy: strict-origin-when-cross-origin

permissions-policy: geolocation=(), microphone=(), camera=()

Real HTTP headers of dalenconlancaster.com

What it had to solve

A small firm needs to build trust online and save time running the practice.

  • Explain without overwhelming

    Eleven areas presented clearly, each with its own page, and a way in for matters that fit none of them.

  • Show results

    Real success stories with their outcome, each with its own page.

  • Serve remotely

    In-person or online service across Spain, in Spanish, Galician and English.

  • Give clients access

    A private area to follow their case without calling the firm.

  • Manage in one place

    An admin panel for the firm’s internal work.

  • A consistent identity

    A “dark tech” design shared by the website, the client area and the panel.

Architecture: three apps, one firm

The public website, the client area and the admin panel are separate applications, with separate access and the same visual identity.

LayerWhat is thereOrigin
Public websiteHome, eleven areas, success stories, team and contact form (PHP and JavaScript)Hand-made
Client areaSign-in with an ID or tax number, access requests and password recovery, at clientes.dalenconlancaster.comHand-made
Admin panelThe firm’s internal managementHand-made
DataClients, cases and access accounts (MySQL)Hand-made
MapsLink to the firm’s location on Google MapsExternal service

How a client signs in

  1. Request

    The client requests access from the client area.

  2. Activation

    The firm activates their account.

  3. Sign-in

    They sign in with their ID or tax number and password.

  4. Follow-up

    They check their case without calling the firm.

  5. Recovery

    If they forget the password, they reset it themselves.

  6. Secure connection

    The whole area runs over an encrypted connection.

clientes.dalenconlancaster.com

What it does

The features you can find on the website today.

  • Public

    Eleven practice areas

    Accounting, corporate, consumer, contract, tax and property law, investments, litigation, financial planning, data protection, and insurance and usury.

  • Public

    Success stories

    A carousel of resolved cases, each with its own page.

  • Public

    Live opening hours

    A clock showing whether the firm is open or when it opens again.

  • Public

    Contact by area

    A form where the client picks the area of their matter.

  • Public

    Team and location

    Professional profile and a link to the firm’s location.

  • Public

    Social media

    LinkedIn, Instagram and X.

  • Private

    Client area

    Private sign-in with an ID or tax number and password.

  • Private

    Access management

    Access requests and password recovery.

  • Private

    Admin panel

    The firm’s internal management.

Challenges and how I solved them

Real problems from the project, the solution I applied and what it achieved.

Knowing someone is there

Problem
People who write outside office hours do not know when they will get an answer.
Solution
The home page shows a live clock with the opening hours and says whether the firm is open or when it opens again.
Result
Clear expectations before getting in touch

Three audiences, three access points

Problem
Visitors, clients and the firm itself need to see very different things.
Solution
A public website, a client area on its own subdomain and an admin panel, each with its own access.
Result
Every user sees only what is theirs

Signing in without a username

Problem
Asking clients to invent a username adds one more step and one more thing to forget.
Solution
Sign-in uses their ID or tax number and a password, with access requests and password recovery.
Result
Clients sign in with something they already know

Eleven areas, no clutter

Problem
A firm with many areas risks looking scattered.
Solution
Uniform cards with their category, one page per area and a way in for “Does your matter not fit?”.
Result
The whole offer at a glance

Tech stack

~/dalenconlancaster — bash
Languages
PHP, JavaScript, SQL, HTML5, CSS3
Database
MySQL
Applications
Public website, client area on its own subdomain and admin panel
Security
Separate access per application, encrypted connection and password recovery
Design
A “dark tech” identity shared by all three apps
Search
Technical SEO

Try it live

The firm’s website is live: browse its practice areas, its success stories or the client-area sign-in.

Visit dalenconlancaster.com

Shall we talk?

If you would like me to show you how it is built inside, or you are interested in my profile, write to me.

Or, if you prefer, another channel:

See the rest of the portfolio

dalenconlancaster.com Email me