mcdonalds.co.jp

Readiness by lane

Green: mcdonalds.co.jp. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for mcdonalds.co.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   42% of Food & Grocery Delivery peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 78 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   63% of Food & Grocery Delivery peers do this.

   Guide: Lazy Loading Without Broken Pages

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   37% of Food & Grocery Delivery peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

   35% of Food & Grocery Delivery peers do this.

   Guide: CDN Guide for Website Owners

What mcdonalds.co.jp already does well

Practices fewer than half of Food & Grocery Delivery peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.6.6% of peers
• Nameservers spread across providersNameservers spread across more than one operator.12% of peers
• Modern image formats in useWebP or AVIF images detected.40% of peers

What we saw

Homepage checked

https://www.mcdonalds.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-01-16

CDN or edge

Amazon CloudFront

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 0 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

165 KB, gzip

Images on homepage

78 (png 39, svg 27, jpg 19)

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

Compare with other Food & Grocery Delivery sites

• jow.fr75
• kirbiecravings.com75
• marketdino.pl75
• migros.com.tr75
• mindmegette.hu75

Food & Grocery Delivery readiness benchmark