PatientsForce
PatientsForce 致力於打造各類型的病患服務平台,民眾可輕鬆下載簡單操作,即可享有醫療小秘書協助您各項醫療服務需求。.
Report generated on April 5, 2026
A note on how to read this
This report is ProdPoke's take on your site — think of it as a first impression from a very opinionated robot. We check real things (load times, broken links, accessibility patterns), but we also try to understand what your site is trying to do and whether the technical details support that goal. Some of our observations might not apply to your specific situation, and that's okay. We're getting sharper with every scan. If something feels off, tell us — it makes us better.
Key Insights for PatientsForce
360 unlabeled interactive elements mean patients can't navigate your financial tools without vision.
PatientsForce serves patients managing medical costs — many may have disabilities. Your calculators, insurance benefit tools, and assistance service buttons are invisible to screen readers, blocking access to core features for users with visual impairments.
5-second load time costs you conversions when patients are researching treatment costs in real time.
Your Financial Toxicity Calculator and cost estimation tools are decision-support features — patients use them when facing urgent medical decisions. A 5034ms load time vs. the 3-second expectation means users abandon before your core value proposition loads.
11 Content Security Policy violations are silently blocking inline styles, potentially breaking UI on patient-facing calculators.
Healthcare financial services handle sensitive patient data. These CSP errors indicate your styling isn't properly secured — this creates both a user experience problem (broken layouts) and a security debt that regulators and auditors will flag.
No cookie consent, terms of service, or canonical URLs — your site lacks basic legal and technical compliance for a regulated healthcare platform.
As a healthcare financial services provider, you're subject to GDPR (EU patients), consumer protection laws, and industry scrutiny. Missing terms, cookie consent, and canonical tags expose you to legal risk and SEO penalties that hurt discoverability.
214 H1 tags on one page destroy your SEO signal — search engines can't identify what PatientsForce actually does.
Patients discovering you through search expect clarity about your financial assistance and cost estimation services. Multiple H1s confuse search ranking algorithms and dilute your message, making it harder for patients to find you when researching medication costs.
What ProdPoke understands about PatientsForce
PatientsForce is a healthcare financial services platform operated by Media-WIND Health Holdings that helps patients manage the financial aspects of medical treatment. The platform offers several key services visible across the pages: a 'Financial Toxicity Calculator' for patients using self-paid medications, medication cost estimation tools, insurance benefit calculators that let users log multiple insurance policies to understand their coverage, and financial assistance services for medication costs. The site also displays six subsidiary companies under the Media-WIND umbrella (pharmacy chains, health e-commerce, consultation services, biotech, medical financing, and home care), indicating this is part of a larger healthcare ecosystem. The product aims to help patients understand treatment costs upfront and navigate financial resources before beginning medical therapies.
Based on exploring 5 pages across the site
First Impression — How clear is your site?
PatientsForce is a patient service platform by Media-WIND Health Holdings that provides medical support resources and tools. According to the page, it offers services including drug subsidy assistance (PAP), patient support programs (PSP), and special import programs (EAP), along with insurance calculations, medication expense trials, and social resource matching services. The hero text states: 'PatientsForce不僅伴隨病患踏上治療旅程,依照病患在不同階段的需求,提供各式醫療照護服務與資源方案' (accompanies patients through their treatment journey, providing various medical care services and resource solutions based on different treatment stages).
This score measures how quickly a first-time visitor understands what your site does — based on visible headings, navigation, and visual hierarchy alone.
Overall Score
Good start — room to grow.
Performance
85/100Slow page load: 5034ms
Your page took 5034ms to fully load. Users expect pages to load in under 3 seconds.
Found: 5034ms
SEO
89/100Multiple H1 tags (214)
Best practice is one H1 per page. Multiple H1s dilute the page's primary topic signal.
Found: 214 H1 tags
No canonical URL specified
A canonical tag helps search engines understand the preferred URL for this content, preventing duplicate content issues.
Accessibility
54/100360 interactive element(s) without accessible names
These elements have no text content, aria-label, aria-labelledby, or title attribute. Screen reader users cannot understand what they do.
Found: 360 missing: <a>, <input[type=hidden]>, <input[type=text]#keyword.seach-input>, <button[type=button].close>, <a>
1 form input(s) without labels
Form inputs without associated labels are difficult for screen reader users and reduce form usability for everyone.
Found: Missing labels: text: keyword
7 image(s) without alt text
Images without alt text are invisible to screen readers. Decorative images should use alt="".
Found: 7 images missing alt
Focus indicators not visible on most elements
Tabbing through the page: 10 of 10 focusable elements have no visible focus indicator. Keyboard users can't see where they are.
Found: 10/10 elements lack visible focus
Functional
84/100Form has no submit button
A form (action: https://media-wind.ai/zh/content/search) has 2 inputs but no visible submit button.
Found: No submit button found
5 button(s) with no visible text or icon
Buttons without text or icons are confusing — users don't know what they do.
Found: 5 empty buttons
Technical Health
Network request failed: https://resource.patientsforce.com.tw/website/assets/images/video/ad016232-ba0d-
GET https://resource.patientsforce.com.tw/website/assets/images/video/ad016232-ba0d-49f9-960c-c6313fb35fd2.mp4 failed: net::ERR_ABORTED
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-ZdHxw9eWtnxUb3mk6tBS+gIiVUPE3pGM470keHPDFlE='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-LYKbgzsmMmBxkvnHk+0qW7BQPPZNPKj6L/pM0RbE2Yw='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Applying inline style violates the following Content Security Policy directiv...
[error] Applying inline style violates the following Content Security Policy directive 'style-src 'self' https://resource.patientsforce.com.tw https://fonts.googleapis.com https://maxcdn.bootstrapcdn.com https://cdn.datatables.net 'nonce-NnTwpPiJtgnqpgahUVisqBnNsIJ9YDlI''. Either the 'unsafe-inline' keyword, a hash ('sha256-HM3TDTqZAXAXyMIKAYi/2OiZZCAtHdj/imXzEShnwoQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.
Compliance
84/100No terms of service link found
Your site doesn't have a terms of service or conditions link found. This is recommended for any commercial site or service.
No cookie consent mechanism detected
Your site doesn't have a cookie consent banner or dialog was detected. If this site uses cookies (including analytics or session cookies), a consent mechanism is required under GDPR for EU visitors.
Key Metrics
Crawlability
Standards
Improvement Plan
PatientsForce has built valuable financial tools for patients, but three systemic issues are undermining both user experience and business viability. First, your site is not accessible — 360 interactive elements lack labels, and keyboard focus indicators are invisible. For a healthcare platform, this is both a legal exposure and a missed market: patients with disabilities are potential customers, and accessibility compliance is increasingly expected. Second, your site is slow (5 seconds vs. 3-second expectations) and structurally broken: 11 CSP style violations suggest your front-end build process is applying inline styles that conflict with your security policy. This needs immediate remediation because broken styling degrades trust in financial calculators — patients need visual clarity when estimating costs. Third, you're missing basic compliance: no terms of service, no cookie consent for EU traffic, and 214 H1 tags that confuse search engines about your value proposition. These aren't just audit issues — they're barriers to discoverability and legal risk.
Your improvement roadmap should prioritize three phases. Phase 1 (Week 1–2): Fix the CSP violations by moving all inline styles to external stylesheets or adding proper nonce attributes; this will restore visual consistency and unblock performance gains. Simultaneously, audit and label all 360 interactive elements with aria-labels or title attributes — focus on your core tools (Financial Toxicity Calculator, cost estimators, insurance benefit calculator, and assistance request buttons) first. Phase 2 (Week 2–3): Reduce load time from 5s to <3s by identifying the culprit (likely the video asset that failed to load at resource.patientsforce.com.tw/website/assets/images/video/ad016232-ba0d-..., which may be blocking page rendering). Lazy-load non-critical resources and compress images. Add visible focus indicators via CSS (:focus-visible) so keyboard users can navigate your financial forms. Phase 3 (Week 3–4): Consolidate your H1 tags to one per page (your main value proposition), add a canonical URL to prevent duplicate content indexing, implement a cookie consent banner (critical for GDPR), and publish a terms of service linked in your footer. Add missing alt text to 7 images and ensure your search form has a visible submit button.
Post-remediation, this work unlocks three business outcomes: (1) accessibility compliance signals to healthcare buyers and regulators that you take patient inclusion seriously, (2) faster load times improve conversion on your calculators and financial assistance intake, and (3) cleaner SEO (one H1, canonical URL, compliance signals) helps patients find you when researching medication cost assistance. Assign a front-end engineer to CSP and performance fixes, an accessibility specialist to label interactive elements, and legal/compliance to terms and cookies. Test all changes with keyboard navigation and a screen reader before launch.
Suggested priority order:
- CSP inline style violations (11 instances)
- 360 interactive elements without accessible names
- Slow page load (5034ms)
- Visible focus indicators not present
- 214 H1 tags (SEO and clarity issue)
- No terms of service link
- No cookie consent mechanism
- No canonical URL specified
- 7 images without alt text
- Form with no visible submit button
- Video asset failed to load
This is your site? Get the full picture.
Claim this report to unlock ongoing monitoring, deeper analysis, and actionable alerts.
What is ProdPoke?Automated analysis generated on April 5, 2026. Not professional advice. Contact us to modify or remove this report.

