oppo.com

Readiness by lane

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

Priority fixes for oppo.com

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

1. Priority 1 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 101 images and none used loading="lazy".

   Why it matters: Images below the fold are only downloaded when the visitor scrolls near them, which frees bandwidth for what is visible first.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Lazy Loading Without Broken Pages

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

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

   Guide: A Practical Website Health Check for Owners

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

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

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

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

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

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What oppo.com already does well

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

• HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.39% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked

https://www.oppo.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-18

Platform or framework

Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

199 KB, gzip

Images on homepage

101 (png 73, jpg 31, svg 15, webp 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 E-Commerce & Marketplaces sites

• newme.asia66
• olympikus.com.br66
• onlinehomeshop.com66
• othoba.com66
• ovs.it66

E-Commerce & Marketplaces readiness benchmark