Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Engineering / Page weight

Page weight

How many bytes a visitor downloads on our key pages, split by type, and checked against a budget every day. Heavy pages are slow pages on a hotel wifi or a phone abroad, which is where many of our buyers are.

Loading the latest run...

How it is measured

  • The same daily job that runs the visual tests loads each of the 20 key pages once on a phone (390 px) and once on a desktop (1440 px), with an empty browser cache.
  • For every request we take the bytes that actually crossed the network (compressed body plus headers, as Chrome reports them), after the network goes quiet plus 2.5 seconds, so late scripts such as analytics are included.
  • Bytes from kolaboro.com are split into HTML, CSS, JavaScript, images, fonts and other (mostly the JSON data the page reads). Everything from another host, and code Cloudflare injects under /cdn-cgi/, counts as third party.
  • Each page has a type (home, project, data, tool, content) with a budget per type and screen size. A page over budget marks the daily job as failed, which emails us. It never blocks or rolls back a deploy.
  • Lighthouse scores for the same pages, run separately every day, are on /status and in /data/lighthouse.json.

Limits

  • One load per page from one place (a build machine in the United States), measured as a first-time visitor. Visitors in Europe see the cookie banner first, and their numbers can differ.
  • Third-party vendors change what they serve without notice, so the third-party share can move from one day to the next without any change on our side.
  • Budgets were set from the first measurement on 5 November 2026. They stop pages from getting heavier; they do not say the current weight is good.

Related: real-user speed, software bill of materials (every third-party script we load), visual tests.

Protect my purchase