What this evidence covers
These checks were performed on ARIENESS’s own public website and app on November 10, 2026. They document product behavior and a dedicated QA workflow. They are not a customer case study, a church attendance result, an SEO ranking result or an independent certification.
Mobile lab measurements
A mobile Google PageSpeed Insights/Lighthouse check returned: homepage 97/100, LCP 1.7 seconds, CLS 0; website-audit page 98/100, LCP 1.2 seconds, CLS 0; app signup 100/100, LCP 0.9 seconds, CLS 0. Tested URLs were https://arieness.com/, https://arieness.com/website-audit/ and https://app.arieness.com/signup. Scores vary between runs and devices.
What the speed results do not establish
No CrUX field sample was available for these checks. Real-user INP and a field Core Web Vitals pass were therefore not established. The app signup test covered its public signup page, not every authenticated workflow. These technical measurements do not establish conversion uplift or customer outcomes.
Website-to-app campaign attribution
A browser test followed a real signup link from the public site into the app after analytics consent. The same GA4 client and session identifiers were preserved. A campaign-name mapping defect was corrected and deployed through PR 110. The production collection request then carried the expected source, medium and campaign name, with its app page URL stripped of query parameters.
Consent and a completed audit
Checks found no Google Analytics requests before a choice or after rejection. Revoking consent in the app was respected when returning to the main site. A single audit of ARIENESS’s public website in a dedicated QA workspace completed successfully; GA4 Realtime displayed one audit_complete event and one matching key event. The report view used a redacted record path.
Limits and how to evaluate the product
This test does not demonstrate new-customer acquisition, a paid purchase, every signup confirmation path, or delivery of customer church outcomes. A separate fresh-signup check remained unverified at publication. Recheck important workflows in your own consented test environment. Ask for evidence tied to the feature you intend to use rather than treating a lab score as a promise of growth.
