bilibili.com

Readiness by lane

Green: bilibili.com. Thin bar: Entertainment & Video Streaming peer median.

Priority fixes for bilibili.com

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   96% of Entertainment & Video Streaming peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 600 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   46% of Entertainment & Video Streaming peers do this.

   Guide: Browser Caching 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.

   31% of Entertainment & Video Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 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.

   42% of Entertainment & Video Streaming peers do this.

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

What bilibili.com already does well

Practices fewer than half of Entertainment & Video Streaming peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=reject.31% of peers
• Modern image formats in useWebP or AVIF images detected.32% of peers

What we saw

Homepage checked

https://www.bilibili.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2026-12-13

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

162 KB, gzip

Images on homepage

16 (avif 16, webp 16)

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 Entertainment & Video Streaming sites

• cdn-videyi.top50
• chipstime.fr50
• sd-milk.com51
• storymax.in51
• villagecinemas.gr51

Entertainment & Video Streaming readiness benchmark