realme.com

Readiness by lane

Green: realme.com. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for realme.com

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (275 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.

   97% of E-Commerce & Marketplaces 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 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   94% of E-Commerce & Marketplaces peers do this.

   Guide: CDN Guide for Website Owners

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

   32% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

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

   72% of E-Commerce & Marketplaces peers do this.

   Guide: Lazy Loading Without Broken Pages

What realme.com already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked

https://www.realme.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 198-day validity, expiring 2027-03-10

Platform or framework

Nuxt

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

275 KB, uncompressed

Images on homepage

44 (webp 9, svg 8, jpg 6, png 2)

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 E-Commerce & Marketplaces sites

• made-in-china.com54
• moov.com.ar54
• mysnep.com54
• starbucks.co.jp54
• uzum.uz54

E-Commerce & Marketplaces readiness benchmark