STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

restaurant-board.com

restaurant-board.com's public homepage, certificate and DNS checked against 31 practices and compared with 125 Workplace Productivity sites.

Readiness index
42/100

Workplace Productivity median 66

Ahead of
8%

of measured Workplace Productivity sites

Practices observed
10/30

1 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:03:41 UTC from one location. How we measure

Readiness by lane

Green: restaurant-board.com. Thin bar: Workplace Productivity peer median.

Enable

67/100

Peers 77

Harden

38/100

Peers 63

Accelerate

24/100

Peers 62

Recover

0/100

Peers 5

Priority fixes for restaurant-board.com

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    93% of Workplace Productivity peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    90% of Workplace Productivity peers do this.

  3. Priority 3 · Harden

    HSTS kept for at least a year

    Observed: The homepage response did not include a Strict-Transport-Security header.

    What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

    59% of Workplace Productivity peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

    Observed: The homepage had 54 images and none used WebP or AVIF.

    What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

    On Nuxt: Nuxt Image can output WebP and AVIF.

    49% of Workplace Productivity peers do this.

What we saw

Homepage checked
https://restaurant-board.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.2
Certificate
DigiCert, 198-day validity, expiring 2027-04-21
Platform or framework
Nuxt
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=quarantine
Homepage HTML
33 KB, gzip
Images on homepage
54 (png 51, jpg 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 10

  • HTTP requests move to HTTPS
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • HTML compressed
  • robots.txt published
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • At most one redirect to the homepage

Not measured 1

  • Static files cached for 30 days or more

Own restaurant-board.com?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: restaurant-board.com. This profile covers configuration only.

Compare with other Workplace Productivity sites