programmable.watch website review

About 65 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 6 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Upload your supplier list. Watch matches each one to its SA…”.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

By the Sustainable Web Design model, a visit to your homepage emits about 0.09 g of CO₂e: 11.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Your title is 67 characters, so Google will cut it off around 60: “Programmable Watch: know the day a supplier falls out of compliance”.

Your meta description is 292 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 25 pages on programmable.watch and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to /register and /dashboard, which answer with an error. Visitors hit a dead end and search engines drop them.

/docs/api, /terms, /privacy, /dpa and /subprocessors use the same meta description. A description written for each page earns more clicks.

We fetched 7 pages linked from your homepage and read each the way a search engine does.

2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 link from your homepage to your own site is broken, for example https://programmable.watch/cdn-cgi/l/email-protection (404).

3 links go through two or more redirects, for example https://programmable.watch/login.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

programmable.watch was registered in Oct 2026 through NameCheap, Inc.. Spam filters and search engines treat brand-new domains more cautiously, so expect email and rankings to take a few months to settle.

programmable.watch has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

programmable.watch's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 1,223 words of visible text.

programmable.watch has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

programmable.watch has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

programmable.watch has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.