toluna.com

Readiness by lane

Green: toluna.com. Thin bar: Data & Analytics peer median.

Priority fixes for toluna.com

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (190 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

   95% of Data & Analytics peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Harden

   HSTS kept for at least a year

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

   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.

   34% of Data & Analytics peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   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.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 16 external scripts 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.

   54% of Data & Analytics peers do this.

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

What toluna.com already does well

Practices fewer than half of Data & Analytics peers use.

• Content Security Policy presentContent-Security-Policy present.24% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• X-Content-Type-Options: nosniffnosniff header present.46% of peers

What we saw

Homepage checked

https://www.toluna.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2027-05-08

CDN or edge

Amazon CloudFront

DNS operators

Vercara UltraDNS

HSTS

max-age 30 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

190 KB, uncompressed

Images on homepage

7 (png 12)

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

• 22s5.com55
• coinglass.com56
• porofessor.gg56
• qcc.com56
• webgia.com56

Data & Analytics readiness benchmark