# BeaverCheck Audit Report — https://xinyong.boai.gov.cn

**Date:** October 21, 2026  
**URL:** https://xinyong.boai.gov.cn  
**Overall Grade:** C (78/100)  
**Report:** https://beavercheck.com/results/d8a94dc8-92aa-476d-8308-c964c54a22da

## Top Findings

1. **[CRITICAL]** 'unsafe-eval' found in script source — Security > Content Security Policy
2. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
3. **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — Accessibility > 404 Error Page
4. **[WARNING]** 47 inline style attribute(s) detected — Security > CSP Inline-Style Readiness
5. **[WARNING]** Cookie 'JSESSIONID' has no SameSite attribute — Security > Cookie Security

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 79 |
| Accessibility | 66 |
| Best Practices | 96 |
| SEO | 75 |

---

## Security

### Security Headers (C — 55/100)

*5 of 10 headers properly configured*

- **[WARNING]** HSTS is enabled but max-age is short (172800s, should be >= 31536000s) — The header is present and enforced, so first-visit protection is already in place; a short max-age just means the browser forgets it sooner. Set max-age to at least 31536000 (1 year).
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[PASS]** Content-Security-Policy is present
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 20/100)

*2 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[WARNING]** default-src directive is missing — default-src provides a fallback for other directives. Set it to restrict default resource loading.
- **[CRITICAL]** 'unsafe-inline' found in script source — 'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
- **[CRITICAL]** 'unsafe-eval' found in script source — 'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
- **[PASS]** No wildcard in script source
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[WARNING]** frame-ancestors directive is missing — frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

### TLS & Certificates (A+ — 100/100)

*TLS 1.2, 7 checks passed*

- **[PASS]** TLS 1.2 is used
- **[INFO]** TLS 1.3 is not negotiated — TLS 1.3 offers improved performance and security. Consider enabling it.
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 102 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 1 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 95/100)

*1 cookies analyzed, 2 checks passed*

- **[PASS]** Cookie 'JSESSIONID' has the Secure flag
- **[PASS]** Cookie 'JSESSIONID' has the HttpOnly flag
- **[WARNING]** Cookie 'JSESSIONID' has no SameSite attribute — Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

### Cookie Hygiene (A+ — 100/100)

*All 1 cookie(s) pass hygiene checks*

- **[PASS]** All 1 cookie(s) pass hygiene checks

### WAF / Bot Protection (B — 75/100)

*No WAF detected via response headers*

- **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

### security.txt (B — 70/100)

*Vulnerability disclosure policy*

- **[PASS]** security.txt found
- **[WARNING]** security.txt: Missing required 'Contact' field
- **[WARNING]** security.txt: Missing required 'Expires' field (RFC 9116)

### CSP Inline-Style Readiness (C — 75/100)

*47 inline style attribute(s) detected*

- **[WARNING]** 47 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 47 inline style(s) is moderate. Affected element types include: div, span, h4, a, img. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (B — 95/100)

*Trusted Types not enabled*

- **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (A+ — 100/100)

*No external resources*

- **[PASS]** No external resources to protect

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC, no SPF*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (A+ — 100/100)

*489 KB transferred, 41 requests*

- **[PASS]** Page weighs 767 KB (489 KB transferred)
- **[PASS]** 41 HTTP requests
- **[INFO]** Estimated 0.10 g CO2 per page load

### Third-Party Impact (A+ — 100/100)

*No third-party resources*

- **[PASS]** No third-party resources detected

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (C — 60/100)

*32 images, 0 KB saveable*

- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/meng... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/meng... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/file/ueditorgroup/hong... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/wap/images/... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (D — 40/100)

*2628ms total JS execution*

- **[WARNING]** https://xinyong.boai.gov.cn/: 1798ms CPU time
- **[WARNING]** https://xinyong.boai.gov.cn/henan/boai/js/plugin/S...: 334ms CPU time
- **[WARNING]** Unattributable: 260ms CPU time
- **[INFO]** https://xinyong.boai.gov.cn/henan/boai/wap/cms/plu...: 133ms CPU time
- **[INFO]** https://xinyong.boai.gov.cn/henan/boai/js/jquery-3...: 102ms CPU time

### Font Loading (A+ — 100/100)

*No web fonts (system fonts)*

- **[PASS]** No web fonts loaded — system fonts are fastest

### JS Bundles (A+ — 100/100)

*5 scripts, 0 KB unused*


### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*No optimization needed*

- **[PASS]** No resource hint issues

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Document Compression (B — 80/100)

*Document response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### Asset Compression

*No text asset hosts to measure*

- **[INFO]** No third-party or subdomain host served enough text assets to measure — Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (B — 80/100)

*No Cache-Control header on main HTML response*

- **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 95/100)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (A+ — 100/100)

*41 resources · 489 KB · 0 KB savings available*

- **[PASS]** Within 1MB page-weight target
- **[INFO]** 1 resources over 200KB

---

## Infrastructure

### DNS Records (B — 75/100)

*1 A records, 1119 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[PASS]** Has 1 IPv6 (AAAA) record(s)
- **[INFO]** No NS records found
- **[INFO]** No MX records — email not configured via DNS
- **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
- **[WARNING]** DNS resolution is slow (1119 ms) — Slow DNS adds latency to every page load. Consider a faster DNS provider.

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** No CNAME record present

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (C — 60/100)

*0/2 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 124.42.8.135: lookup 124.42.8.135: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
- **[INFO]** PTR lookup failed for 240a:2001:1811:2007::88: lookup 240a:2001:1811:2007::88: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (D — 50/100)

*Mean 458ms across 3 resolvers (spread 185ms)*

- **[PASS]** Google: 337ms
- **[PASS]** Quad9: 516ms
- **[PASS]** Cloudflare: 522ms

### Redirect Chain (A+ — 100/100)

*No redirect data available*

- **[INFO]** No redirect data captured

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (181 ms)*

- **[PASS]** IPv6 is configured and reachable at 240a:2001:1811:2007::88

### Crawlability (C — 60/100)

*no robots.txt, sitemap with 0 URLs*

- **[INFO]** No robots.txt found — robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
- **[PASS]** sitemap.xml is present
- **[WARNING]** sitemap.xml contains invalid XML — Search engines may not be able to parse the sitemap. Fix XML validation errors.
- **[WARNING]** sitemap.xml is empty — no URLs found — An empty sitemap provides no value. Add <url> entries for your pages.

### URL Variants (B — 75/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[CRITICAL]** HTTP version does not redirect to HTTPS

### Domain Intelligence (A+ — 100/100)

*boai.gov.cn — via 北京新网数码信息技术有限公司, 18 years, 1 months old*

- **[PASS]** Domain registered until Dec 2, 2027 (1 years, 1 months remaining)
- **[PASS]** Registrar: 北京新网数码信息技术有限公司
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (B — 80/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected in the page — No link matching the privacy-policy vocabulary was found in the rendered page. The common privacy-policy paths were not probed for this scan, so this is an unconfirmed absence and is excluded from the regulatory-risk estimate.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[PASS]** 1 essential cookie(s) on initial load — no consent required
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No script URLs to scan -- tracker inventory is N/A*

- **[PASS]** No script URLs to scan -- tracker inventory is N/A

### Language & i18n (A+ — 100/100)

*Lang attribute + Content-Language header*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[PASS]** Content-Language header is set
- **[PASS]** Language signals are consistent

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No HTML captured -- i18n extras check is N/A*

- **[PASS]** No HTML captured -- i18n extras check is N/A

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (F — 30/100)

*No viewport meta tag*

- **[CRITICAL]** No viewport meta tag found — Without a viewport meta tag, the page will not render correctly on mobile devices.

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (D — 50/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[INFO]** GDPR Article 13 disclosures not assessed (policy language: zh-CN) — The privacy policy appears to be written in "zh-CN", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate.

### Third-Party Trackers (A+ — 100/100)

*No third-party trackers detected*

- **[PASS]** No third-party trackers detected

### Cookie & Tracker Inventory (A+ — 100/100)

*1 cookies · 0 trackers · 0 pre-consent*

- **[PASS]** No pre-consent tracking cookies detected

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No SameSite=None cookies -- no cross-site travel surface*

- **[PASS]** No cookies opted in to cross-site travel (SameSite=None)

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No HTML captured -- beacon-tracking check is N/A*

- **[PASS]** No HTML captured -- beacon-tracking check is N/A

---

## Availability

### CDN & Delivery (D — 50/100)

*No CDN (document or assets)*

- **[WARNING]** No CDN (document or assets) — Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (F — 30/100)

*No cache headers*

- **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (B — 75/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** HSTS max-age is short: 2 days — HSTS max-age should be at least 1 year (31536000 seconds).

### Health Check Endpoint (A+ — 100/100)

*Health endpoint at https://xinyong.boai.gov.cn/health (HTTP 200)*

- **[PASS]** Public health endpoint at https://xinyong.boai.gov.cn/health

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (A+ — 100/100)

*Font-size measurement not available for this scan*

- **[PASS]** Font-size measurement not available for this scan

---

## UX

### 404 Error Page (F — 20/100)

*Soft 404 detected*

- **[CRITICAL]** Soft 404: server returns HTTP 200 for non-existent pages — The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

### Favicon & Branding (F — 15/100)

*1 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[INFO]** No apple-touch-icon detected — iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

### Web Manifest (F — 30/100)

*Invalid JSON*

- **[WARNING]** Manifest contains invalid JSON — Manifest at https://xinyong.boai.gov.cn/manifest.json contains invalid JSON. Browsers cannot parse it.

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (D — 40/100)

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (F — 0/100)

*No navigation patterns*

- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

### Mobile UX Depth (A+ — 100/100)

*No HTML captured -- mobile-depth check is N/A*

- **[PASS]** No HTML captured -- mobile-depth check is N/A

---

## SEO

### SEO Audit Unavailable

*Content probe data missing -- see finding for details*

- **[INFO]** SEO checks could not run for this scan — Content probe data is missing for this scan -- SEO checks need the rendered DOM (canonical tag, meta description, hreflang, etc.). Common causes: bot-detection block (Akamai/Cloudflare/Imperva served the worker a challenge instead of the page), worker timeout, or the site redirected to an unrelated host.

---

## Sustainability

### CO2 Per Page Load (A+ — 100/100)

*0.14g CO2 per view*

- **[PASS]** 0.14g CO2 per page view — This page transfers 0.5 MB, producing an estimated 0.14g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.03g, network 0.02g, end-user device 0.09g.
- **[INFO]** At 10,000 monthly views: 16.2 kg CO2/year — With 10,000 page views per month, this page would generate approximately 16.2 kg of CO2 annually — equivalent to charging 2030 smartphones.

### Green Hosting (D — 50/100)

*Unknown*

- **[INFO]** Hosting provider could not be identified — Without knowing the provider, we cannot determine their energy sourcing. Check with your hosting provider about their renewable energy commitments.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*98% cached*

- **[PASS]** 98% reduction on repeat visits — Returning visitors download only 9 KB (vs 489 KB first visit). 40 of 41 resources are served from browser cache, saving 0.13g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.00g CO2 (first visit: 0.14g)

### Carbon Budget (A+ — 100/100)

*10th percentile*

- **[PASS]** 0.14g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 90% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 10th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (A+ — 100/100)

*100% efficient*

- **[PASS]** Transfer efficiency: 100% — Only 0 KB of potential savings identified. Your page is well-optimized for size.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/d8a94dc8-92aa-476d-8308-c964c54a22da*