mureka.ai

Readiness by lane

Green: mureka.ai. Thin bar: Design & Content Creation peer median.

Priority fixes for mureka.ai

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

1. Priority 1 · Accelerate

   Modern image formats in use

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

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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.

   56% of Design & Content Creation peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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.

   37% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GoDaddy.com had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   72% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for mureka.ai, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What mureka.ai already does well

Practices fewer than half of Design & Content Creation peers use.

• Content Security Policy presentContent-Security-Policy present.29% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers
• HTTP/3 advertisedHTTP/3 advertised.43% of peers

What we saw

Homepage checked

https://www.mureka.ai/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 198-day validity, expiring 2027-01-14

CDN or edge

Amazon CloudFront

DNS operators

GoDaddy DNS

DMARC policy

p=reject

Homepage HTML

103 KB, gzip

Images on homepage

5 (png 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 Design & Content Creation sites

• noorediting07.com77
• photoroom.com76
• traceparts.com77
• watermarkremover.io77
• xtool.com76

Design & Content Creation readiness benchmark