Weblize
Web studio · Doha, Qatar
Loading Weblize

QDP

QDP — a server-rendered luxury property platform for Doha

The project

The QDP homepage at qdp.qa, captured 2026-08-20

QDP is the only one of these five sites that renders on the server: the homepage arrives as roughly 120 KB of finished HTML, property cards included. Its heading, its six section headings and its listing cards are all in the markup before a line of JavaScript runs, so a search engine or a slow phone gets the whole page either way. What it renders is a luxury property catalogue for Doha — villas, penthouses and apartments for sale, rent and investment, filterable by Qatari-riyal price band across both sale and monthly-rental listings, with a detail page per listing. Around the listings sit four separately presented service lines, a documented four-step process from discovery to handover, a leadership section with names on it, and the refund and data-deletion pages that payment providers and app stores require.

Client: QDP · Sector: Property · Live site: qdp.qa

What was built

  • Server-rendered React — the full page, including headings and property cards, arrives in the HTML before any JavaScript executes
  • Property catalogue with a dedicated detail page for each listing
  • Price-band filtering in Qatari riyals across sale and monthly-rental listings
  • Four service lines presented separately: residential rentals, sales and investment, commercial and offices, and property management
  • A documented four-step client process, from discovery to handover
  • A named-leadership section rather than an anonymous team block
  • Support, privacy, terms, refund and data-deletion pages — the set payment providers and app stores require
  • Property, place and opening-hours structured data, plus a site search action
  • Hero and listing imagery preloaded at high fetch priority
  • A language switcher in the interface

The stack

  • React with server-side rendering
  • Vite build pipeline
  • Vercel hosting
  • WebP and remote-CDN imagery
  • schema.org JSON-LD

How this was verified

Every statement above was observed on the live public site on 2026-08-17. There are no outcome metrics here — no traffic, no conversion, no revenue figures — because none of them are observable from outside the client's business.

  • GET https://qdp.qa/ (2026-08-17) → HTTP 200, 120,321 bytes of HTML. Headers: "server: Vercel", "x-vercel-id: bom1::icn1::jp49t-1786979389243-8b6c9e016541".
  • Server rendering is evidenced by content present in the raw response, not by inference: <title>Luxury Properties for Sale &amp; Rent in Doha, Qatar — QDP</title>, <h1>Shape the Skyline. Own the Future.</h1>, and six <h2> headings — "Four services, one seamless experience.", "Properties, curated to shape the Doha skyline.", "From discovery to keys — in four deliberate steps.", "Leadership you can put a name to.", "Your portfolio, always in your pocket.", "Ready to make your next move?". React SSR is further evidenced by the React-style <meta charSet="utf-8"> attribute and a /assets/styles-*.css stylesheet. No __NEXT_DATA__ or _next/static is present, so this is not Next.js.
  • Service lines read from the rendered <h3> elements: "Residential rentals", "Sales & investment", "Commercial & offices", "Property management".
  • Rendered listing cards observed in the same response: "Penthouse — Al Sadd Luxury Tower", "5BR Executive Villa — West Bay Lagoon", "3BR Duplex — Lusail Waterfront", "3BR Waterfront — The Pearl Viva Bahriya".
  • Price-band filters in QAR are present in the rendered markup: four bands for sale listings and a monthly figure for rentals. currenciesAccepted "QAR" appears in the structured data.
  • JSON-LD @type values in the response: ImageObject, Country, City, Place (×3), PostalAddress, OpeningHoursSpecification, WebSite, SearchAction, EntryPoint.
  • GET https://qdp.qa/sitemap.xml → HTTP 200, 39 <loc> entries: /properties, /about, /contact, /support, /privacy, /terms, /data-deletion, /refund, and 20+ /properties/pNN detail pages. GET https://qdp.qa/properties → HTTP 200, 216,308 bytes; GET https://qdp.qa/properties/p16 → HTTP 200, 91,790 bytes; GET https://qdp.qa/support → HTTP 200 — all server-rendered at size.
  • <link rel="preload" as="image" fetchPriority="high"> entries for /qdp-logo-charcoal.webp and /images/doha-hero.jpg, plus preloads for remote CDN listing images.
  • A language switcher is present — "English" appears as a second title-cased control in the rendered markup. Arabic is NOT live: GET https://qdp.qa/ar/ → HTTP 307 to /ar, and GET https://qdp.qa/ar → HTTP 404. The document contains no hreflang annotations and no Arabic characters.
  • The homepage describes a companion resident-services app ("Your portfolio, always in your pocket. Browse listings, save favourites, schedule viewings and track ongoing property management — all in one elegant app."). NO App Store or Google Play link was present on the homepage on 2026-08-17, so no app-store claim is made here.
  • Screenshot captured 2026-08-20 — headless Chromium from this machine, GET https://qdp.qa → HTTP 200, viewport 1440x900 at deviceScaleFactor 2, downscaled to 1600x1000 WebP. Page title at capture: "Luxury Properties for Sale & Rent in Doha, Qatar — QDP". The image on the case-study page is that capture, unedited and uncomposited.

Other client work