Skip to content

potentialspouse.com

https://potentialspouse.com

B89
Performance 70Accessibility 90SEO 92Best Practices 100

11 technologies detected · Last audited May 13, 2026

View full audit

Technology stack

Backend

Elixir Erlang

Cdn

Cloudflare

Frontend

HSTS HTTP/3 Open Graph Phoenix Framework Phoenix LiveView Priority Hints Tailwind CSS

Hosting

Fly.io

Frequently asked questions about potentialspouse.com

What technology does potentialspouse.com use?

potentialspouse.com is built with HSTS, HTTP/3, Open Graph, Phoenix Framework, and Phoenix LiveView.

Is potentialspouse.com fast?

Mostly — potentialspouse.com scores 70/100 on Lighthouse mobile performance, above average but with room to improve.

Is potentialspouse.com accessible?

Yes — potentialspouse.com scores 90/100 on Lighthouse accessibility, meeting most WCAG-aligned automated checks.

What CMS does potentialspouse.com use?

No CMS fingerprint was detected on potentialspouse.com — it may use a static site generator or a custom application.

Where is potentialspouse.com hosted?

potentialspouse.com is hosted on Fly.io.

Does potentialspouse.com use HTTPS?

Yes — potentialspouse.com serves traffic over HTTPS.

Sites with a similar tech stack

stelgano.com

9 shared technologies

fontawesome.com

8 shared technologies

fly.io

7 shared technologies

voidlogue.com

7 shared technologies

allbirds.com

6 shared technologies

allbirds.eu

6 shared technologies

answerthepublic.com

6 shared technologies

astrowealth.store

6 shared technologies

Compare with peer sites

Side-by-side performance, security, and SEO scoreboards against sites running a similar tech stack.

vs stelgano.comvs fontawesome.comvs fly.iovs voidlogue.comvs allbirds.com

Performance Trends

Performance degrading ↓
68 72 76 80May 7May 8May 10May 11May 13May 7, 2026: 76 PerformanceMay 8, 2026: 80 PerformanceMay 10, 2026: 80 PerformanceMay 11, 2026: 68 PerformanceMay 13, 2026: 70 Performance
TTFB improving ↑
169.4 3.4k 6.6k 9.8kMay 7May 8May 10May 11May 13May 7, 2026: 223ms TTFBMay 8, 2026: 231ms TTFBMay 10, 2026: 9.8s TTFBMay 11, 2026: 539ms TTFBMay 13, 2026: 169ms TTFB
FCP degrading ↓
1.3k 1.5k 1.8k 2.0kMay 7May 8May 10May 11May 13May 7, 2026: 1.7s FCPMay 8, 2026: 1.3s FCPMay 10, 2026: 1.7s FCPMay 11, 2026: 2.0s FCPMay 13, 2026: 1.9s FCP
LCP degrading ↓
5.1k 5.7k 6.4k 7.0kMay 7May 8May 10May 11May 13May 7, 2026: 5.2s LCPMay 8, 2026: 5.1s LCPMay 10, 2026: 5.1s LCPMay 11, 2026: 7.0s LCPMay 13, 2026: 5.8s LCP

5 audits

May 13, 2026 07:12 UTC Latest

/

Worker: worker-amsterdam-nl-01

View full report →

Scores

Performance 70Accessibility 90Best Practices 100SEO 92PWA 0

Timing

LCP: 5.83 sFirst Contentful Paint: 1.88 sTTFB: 169 msTotal Time: 171 msCumulative Layout Shift: 0.001
May 11, 2026 15:49 UTC

/

Worker: worker-singapore-sg-01

View full report →

Scores

Performance 68Accessibility 90Best Practices 100SEO 92PWA 0

Timing

LCP: 7.00 sFirst Contentful Paint: 1.99 sTTFB: 539 msTotal Time: 540 msCumulative Layout Shift: 0.001
May 10, 2026 06:26 UTC

/

Worker: worker-madrid-spain-02

View full report →

Scores

Performance 80Accessibility 96Best Practices 100SEO 92PWA 0

Timing

LCP: 5.06 sFirst Contentful Paint: 1.73 sTTFB: 9.83 sTotal Time: 9.83 sCumulative Layout Shift: 0.001
May 8, 2026 15:16 UTC

/

Worker: worker-newyork-us-01

View full report →

Scores

Performance 80Accessibility 96Best Practices 100SEO 92PWA 0

Timing

LCP: 5.11 sFirst Contentful Paint: 1.31 sTTFB: 231 msTotal Time: 238 msCumulative Layout Shift: 0.001
May 7, 2026 16:27 UTC

/

Worker: worker-newyork-us-01

View full report →

Scores

Performance 76Accessibility 95Best Practices 100SEO 45PWA 0

Timing

LCP: 5.15 sFirst Contentful Paint: 1.74 sTTFB: 223 msTotal Time: 223 msCumulative Layout Shift: 0.000

Send Feedback