# BeaverCheck Audit Report — https://fzcars.ir

**Date:** September 10, 2026  
**URL:** https://fzcars.ir  
**Overall Grade:** B (87/100)  
**Report:** https://beavercheck.com/results/b5b8bf02-0b4c-4cc9-9c0b-165e51a8ed3b

## Top Findings

1. **[CRITICAL]** 'unsafe-inline' found in script source — Security > Content Security Policy
2. **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Performance > JavaScript Blocking
3. **[WARNING]** 8 render-blocking stylesheet(s) -- recommended: <=3 — Performance > CSS Performance Depth
4. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers
5. **[WARNING]** Cross-Origin-Opener-Policy header is missing — Security > Security Headers

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 99 |
| Accessibility | 100 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

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

*7 of 10 headers properly configured*

- **[PASS]** HSTS is enabled
- **[PASS]** X-Content-Type-Options is properly configured
- **[PASS]** X-Frame-Options is properly configured
- **[PASS]** Referrer-Policy is properly configured
- **[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 (B — 80/100)

*8 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[PASS]** default-src directive is set
- **[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.
- **[PASS]** No 'unsafe-eval' in script source
- **[PASS]** No wildcard in script source
- **[PASS]** object-src is set to 'none'
- **[PASS]** base-uri is properly restricted
- **[PASS]** frame-ancestors directive is set
- **[PASS]** form-action directive is set
- **[PASS]** upgrade-insecure-requests is enabled

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

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[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 87 days)
- **[PASS]** Certificate chain has 4 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

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

*No cookies set — no cookie security risks*

- **[PASS]** No cookies set — no cookie security risks

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

*No cookies set -- cookie-hygiene check is N/A*

- **[PASS]** No cookies set

### 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 (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

### Cross-Origin Tab Safety (A+ — 100/100)

*All 3 new-tab link(s) carry rel=noopener*

- **[PASS]** All 3 new-tab link(s) carry rel=noopener

### CSP Inline-Style Readiness (A+ — 100/100)

*No inline style attributes -- strict CSP is feasible*

- **[PASS]** No inline style attributes detected

### 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.

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

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

*Page has no third-party scripts or stylesheets -- SRI not applicable*

- **[PASS]** No third-party scripts or stylesheets to protect with SRI

### 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 (A+ — 100/100)

*Referrer-Policy is `no-referrer` (strictest -- no Referer header sent at all)*

- **[PASS]** Referrer-Policy: `no-referrer` -- strictest -- no Referer header sent at all — The strictest setting: no `Referer` header is ever sent. Maximum privacy, but breaks referrer-based analytics and any cross-origin auth flow that relies on the Referer header. Use only when the page handles no referrer-dependent flows.

### Source Map Exposure (A+ — 100/100)

*No source maps accessible (probed 10 candidate URL(s))*

- **[PASS]** No source maps accessible across 10 probed candidate(s)

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (A+ — 100/100)

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### 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 — 92/100)

*813 KB transferred, 83 requests*

- **[PASS]** Page weighs 994 KB (813 KB transferred)
- **[INFO]** Fonts are 352 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks.
- **[INFO]** 83 HTTP requests
- **[INFO]** Estimated 0.17 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 (B — 75/100)

*50 images, 0 KB saveable*

- **[PASS]** All images are well-optimized

### JS Execution Cost (C — 60/100)

*1383ms total JS execution*

- **[WARNING]** https://fzcars.ir/: 891ms CPU time
- **[WARNING]** Unattributable: 492ms CPU time

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

*6 fonts (352 KB)*

- **[INFO]** 6 font(s) use font-display: swap (FOUT risk but functional)

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

*15 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)

*1 hints, 0 missing preconnects*

- **[PASS]** Page uses 1 resource hint(s)

### 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 (A+ — 100/100)

*Document response uses brotli*

- **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it.

### 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 (A+ — 100/100)

*1 Server-Timing entries advertised*

- **[PASS]** Server-Timing header advertises 1 timing entries

### 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)

*83 resources · 813 KB · 0 KB savings available*

- **[PASS]** Within 1MB page-weight target

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

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

*No third-party resources detected*


### JavaScript Blocking (A — 94/100)

*1 JS blocking issue(s) detected*

- **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.

### CSS Performance Depth (A — 88/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 8 render-blocking stylesheet(s) -- recommended: <=3 — Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.

---

## Content Quality

### Links (A+ — 100/100)

*132 links checked, 132 healthy, 0 broken*

- **[PASS]** 132 of 132 links are healthy

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (F — 0/100)

*No Open Graph tags found — social sharing previews will be generic.*

- **[WARNING]** No Open Graph meta tags found — Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

### Open Graph / Twitter Card Depth (A+ — 100/100)

*No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)*

- **[PASS]** No OG image / Twitter card to evaluate

### Structured Data (C — 40/100)

*No structured data (JSON-LD) found.*

- **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results.

### Rich Results Eligibility (C — 75/100)

*No JSON-LD found -- no rich-result eligibility*

- **[INFO]** No JSON-LD structured data on the page — No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.

### Image Optimization (F — 55/100)

*5 issues found across 107 images*

- **[WARNING]** 1 images significantly larger than display size — Resizing to display dimensions could save approximately 5 KB.
- **[WARNING]** 41 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 27 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 50 of 107 images use legacy formats
- **[INFO]** 10 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://fzcars.ir/images/hero/hero-desktop.webp?v=1789027220959, https://fzcars.ir/images/body-types/sedan.webp?v=1789026989688, https://fzcars.ir/images/body-types/hatchback.webp?v=1789026981780 (+7 more).

### Autoplay Media (A+ — 100/100)

*No autoplay media on the page*

- **[PASS]** No autoplay media on the page

---

## Infrastructure

### DNS Records (A+ — 95/100)

*2 A records, 151 ms lookup*

- **[PASS]** Resolves to 2 IPv4 address(es)
- **[INFO]** No IPv6 (AAAA) records
- **[PASS]** 2 nameserver(s) configured
- **[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'.
- **[PASS]** DNS resolution time: 151 ms

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

*No subdomain takeover risk detected*

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

### DNSSEC (C — 55/100)

*Zone signed but parent has no DS record*

- **[WARNING]** DNSSEC keys published but parent zone has no DS record — The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.

### 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 185.143.234.238: lookup 185.143.234.238: 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 185.143.233.238: lookup 185.143.233.238: 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 (B — 80/100)

*Mean 68ms across 3 resolvers (spread 121ms)*

- **[PASS]** Google: 20ms
- **[PASS]** Cloudflare: 44ms
- **[PASS]** Quad9: 141ms

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

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (C — 60/100)

*No IPv6 support*

- **[INFO]** No IPv6 (AAAA) records found — IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

### Crawlability (B — 75/100)

*no robots.txt, no sitemap*

- **[INFO]** No robots.txt found — robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
- **[INFO]** No sitemap.xml found — A sitemap helps search engines discover and index your pages more efficiently.

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

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

- **[CRITICAL]** Both www and non-www versions serve content
- **[PASS]** HTTP correctly redirects to HTTPS permanently

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

*fzcars.ir — hosted on ARVANCLOUD-CDN-IR - Noyan Abr Arvan Co. ( Private Joint Stock), IR*

- **[PASS]** Hosting: ARVANCLOUD-CDN-IR - Noyan Abr Arvan Co. ( Private Joint Stock), IR

---

## Compliance

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

*No testable criteria*


### Cookie Consent & Privacy (A — 85/100)

*No consent signals detected*

- **[WARNING]** No privacy policy found (page links and common paths checked) — No link matching the privacy-policy vocabulary was found in the rendered page, and the common privacy-policy paths returned nothing. A privacy policy page is recommended for transparency and may be legally required.
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[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 known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

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

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

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

*No hreflang tags on this page*

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

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

*1 i18n signal(s) detected*

- **[PASS]** Right-to-left language properly declared with dir attribute — The page declares an RTL language and uses `dir="rtl"` on the document or relevant subtree. Browsers correctly mirror layout (text alignment, scroll direction, list bullet positions) for the visitor.

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

*Font sizes and tap targets checked*


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

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

### 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: fa) — The privacy policy appears to be written in "fa", 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

### Tracking Pixel Inventory (A+ — 100/100)

*No tracking pixels detected*

- **[PASS]** No tracking pixels 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 cookies on the page*

- **[PASS]** No cookies set on the page response

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

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 30/100)

*1 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[PASS]** Terms of Service detected — Found at /terms, linked from footer.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*0 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators.

### Third-Party Data Sharing

*0 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## 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 (A — 90/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.
- **[PASS]** HSTS enabled (includeSubDomains)
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

### CDN Cache Observability (A+ — 100/100)

*Cache state: BYPASS*

- **[PASS]** CDN cache state observable via 1 header(s)

---

## Accessibility

### Landmark Structure (A — 85/100)

*12 landmarks*

- **[PASS]** <main> landmark present
- **[PASS]** 1 <nav> landmark(s) found
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (A — 90/100)

*58 headings*

- **[PASS]** Single H1 present
- **[WARNING]** 2 empty heading(s) — Empty headings appear in the document outline but provide no information.

### Heading Text Quality (A+ — 95/100)

*1 heading-text-quality issue(s) detected*

- **[INFO]** 51 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

### Alt Text Quality (A+ — 100/100)

*All 107 images OK*

- **[PASS]** 97 decorative image(s) correctly marked
- **[PASS]** 10 image(s) with good alt text

### Form Accessibility (A+ — 100/100)

*All 14 controls labeled*

- **[PASS]** 14 control(s) properly labeled

### Link & Button Quality (A — 91/100)

*48 links, 74 buttons — all OK*

- **[WARNING]** 3 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 45 link(s) with descriptive text

### Form Input Types (A+ — 100/100)

*14 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (A+ — 100/100)

*14 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "fa"*

- **[PASS]** <html lang="fa"> is set and valid

### Tabindex Anti-Patterns (A+ — 100/100)

*1 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (A+ — 100/100)

*No iframes on this page*

- **[PASS]** No iframes on this page

### 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)

*All 7 visible text node(s) render at >= 12 CSS pixels*

- **[PASS]** All text uses legible mobile font sizes (>= 12 CSS px)

---

## UX

### 404 Error Page (A — 90/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page
- **[PASS]** Navigation links present on 404 page
- **[PASS]** Homepage link present on 404 page
- **[PASS]** Search form present on 404 page

### Favicon & Branding (B — 80/100)

*8 icon(s) detected*

- **[PASS]** favicon.ico present at site root
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (B — 80/100)

*Valid manifest*

- **[PASS]** Name present: FZ Cars
- **[WARNING]** No 192x192 icon — A 192px icon is required for PWA installation.
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

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

*No PWA depth issues detected*

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

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

*Theme color only*

- **[INFO]** Theme-color present but no dark variant — A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
- **[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 — 15/100)

*No navigation patterns*

- **[PASS]** 1 navigation landmark(s) detected
- **[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)

*2 mobile-depth signal(s) detected*

- **[PASS]** Browser-chrome `theme-color` meta tag present — The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
- **[PASS]** Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices — The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

---

## SEO

### Canonical URL (B — 80/100)

*Minor issues*

- **[WARNING]** No canonical tag found — Search engines will determine the canonical URL themselves, which may cause duplicate content issues.

### Meta Tags (B — 80/100)

*Title: 14 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 14 characters — consider expanding
- **[INFO]** Meta description is only 67 characters — too short to be informative
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

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

*5087 words, Very Easy*

- **[PASS]** Page has 5087 words — good depth for search engines
- **[INFO]** Reading level: Very Easy (grade 8)

### Internal Links (A+ — 100/100)

*47 internal, 1 external*

- **[PASS]** 47 internal links (98%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 47 internal / 1 external links

### Image SEO (A+ — 100/100)

*107 images, 107 descriptive filenames*

- **[PASS]** All images have descriptive filenames

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

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

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (C — 75/100)

*No sitemap.xml found*

- **[INFO]** No sitemap.xml found — Sitemaps help search engines discover and prioritize URLs. Not strictly required for small sites where every page is linked from the homepage, but recommended once a site grows beyond a few dozen URLs.

### Sitemap × Robots Consistency (C — 75/100)

*Sitemap or robots.txt missing -- consistency check skipped*

- **[INFO]** Cross-check skipped (sitemap or robots.txt absent)

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

*No sitemap to evaluate -- depth check is N/A*

- **[PASS]** No sitemap fetched -- depth check skipped

### Markup Quality (A+ — 100/100)

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

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

*0.22g CO2 per view*

- **[PASS]** 0.22g CO2 per page view — This page transfers 0.8 MB, producing an estimated 0.22g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.04g, network 0.04g, end-user device 0.14g.
- **[INFO]** At 10,000 monthly views: 27.0 kg CO2/year — With 10,000 page views per month, this page would generate approximately 27.0 kg of CO2 annually — equivalent to charging 3372 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)

*96% cached*

- **[PASS]** 96% reduction on repeat visits — Returning visitors download only 29 KB (vs 812 KB first visit). 82 of 83 resources are served from browser cache, saving 0.22g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.22g)

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

*12th percentile*

- **[PASS]** 0.22g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 88% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 12th 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.

### Web Font Weight Variants (B — 90/100)

*No detectable Google Fonts weights*

- **[INFO]** No detectable Google Fonts weights — The analyzer detects font weights via Google Fonts URL parameters (~70% of font-using sites). Self-hosted fonts and non-Google CDN fonts aren't visible to URL-based detection. If you self-host fonts, manually audit how many @font-face weights you ship -- 2-3 weights per family is typically enough; 5+ is usually unused payload.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/b5b8bf02-0b4c-4cc9-9c0b-165e51a8ed3b*