dak.gg

Readiness by lane

Green: dak.gg. Thin bar: Data & Analytics peer median.

Priority fixes for dak.gg

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for dak.gg was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   38% of Data & Analytics peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   54% of Data & Analytics peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 28 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.

   31% of Data & Analytics peers do this.

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 28 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.

   60% of Data & Analytics peers do this.

   Guide: Lazy Loading Without Broken Pages

What dak.gg already does well

Practices fewer than half of Data & Analytics peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.34% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers
• X-Content-Type-Options: nosniffnosniff header present.46% of peers

What we saw

Homepage checked

https://dak.gg/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 393-day validity, expiring 2027-01-17

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

68 KB, gzip

Images on homepage

28 (svg 16, jpg 9, gif 1)

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 Data & Analytics sites

• ariva.de67
• buholegal.com67
• lolalytics.com68
• metatft.com67
• surveroid.jp67

Data & Analytics readiness benchmark