giants.jp

Readiness by lane

Green: giants.jp. Thin bar: Sports Broadcast & Fantasy Games peer median.

Priority fixes for giants.jp

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

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   89% of Sports Broadcast & Fantasy Games peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · 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.

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

   27% of Sports Broadcast & Fantasy Games peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 7 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 Next.js: The next/image component serves optimized formats automatically.

   35% of Sports Broadcast & Fantasy Games peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   73% of Sports Broadcast & Fantasy Games peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What giants.jp already does well

Practices fewer than half of Sports Broadcast & Fantasy Games peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.4.6% of peers
• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• HTTP/3 advertisedHTTP/3 advertised.34% of peers

What we saw

Homepage checked

https://www.giants.jp/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-28

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

Homepage HTML

275 KB, gzip

Images on homepage

7

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 Sports Broadcast & Fantasy Games sites

• betexplorer.com60
• bongdanet.online60
• filgoal.com60
• hihi2.com60
• keeptradecut.com60

Sports Broadcast & Fantasy Games readiness benchmark