Report loading
twogethr.us
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
Poor
Health Score
Score by category
The headline health score combines page-level quality and site-wide repeat patterns, then stays anchored to the weakest visible category so it never looks worse than every category beneath it.
Section 01
The Twogether digital presence is currently undermined by critical server-side performance bottlenecks and a complete absence of essential SEO and social sharing metadata.
The site demonstrates a strong brand foundation, utilizing a cohesive color palette and serif typography to establish an emotionally resonant identity. The hero section successfully communicates a clear value proposition, and the desktop experience features a high-contrast primary CTA that effectively directs users toward the core conversion path.
However, the desktop user experience is severely compromised by high latency. A Time to First Byte (TTFB) of 3.31s and a Largest Contentful Paint (LCP) of 4.27s fall well outside acceptable performance thresholds, creating a sluggish first impression. This technical debt is compounded by significant security vulnerabilities, including the absence of Content-Security-Policy and Strict-Transport-Security headers, alongside misconfigured email authentication that leaves the domain vulnerable to spoofing.
There is a massive opportunity to capture organic search and social traffic by implementing a robust metadata strategy. Currently, the site lacks meta descriptions, canonical URLs, and Open Graph tags, meaning any shared links appear as bare, unappealing URLs. Correcting these deficiencies, alongside fixing the broken /sitemap.xml, will transform the site from a closed ecosystem into a discoverable, professional platform.
To stabilize the platform and improve search visibility, the following must be prioritized in the next 30 days:
5 highest-impact findings, ranked.
No HSTS header. Users are vulnerable to protocol downgrade attacks.
How to fix: Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
On /
The LCP is 4272ms, which is significantly above the recommended threshold of 2500ms. This delay in rendering the main hero content can lead to a perceived lack of responsiveness and higher bounce rates.
How to fix: Optimize the hero section by ensuring the primary visual elements (the SVG pet or the hero text) are prioritized. Since the pet is an inline SVG, ensure it doesn't trigger massive layout shifts and consider preloading critical CSS to reduce FCP/LCP.
On /
LCP measures how quickly the largest visible element finishes rendering. Google flags anything above 2.5s as needing improvement and anything above 4s as poor — both signal a slow first impression to users and rank against the page in CrUX.
How to fix: Optimise the LCP element: serve responsive image sizes (srcset/sizes), set fetchpriority="high" on the hero image, preconnect to the image origin, and ensure the LCP element isn't blocked by render-blocking scripts (see PERF-015) or late-mounting React components.
On /
No CSP header found. The site is vulnerable to XSS and injection attacks.
How to fix: Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
On /
Stylesheets and synchronous classic scripts in <head> block the browser from painting until they've downloaded, parsed, and (for scripts) executed. Module scripts and `nomodule` legacy bundles are excluded from this check. This directly inflates First Contentful Paint and Largest Contentful Paint.
How to fix: Add async or defer to non-critical <script> tags, move scripts that aren't needed before the first paint to the end of <body>, and split CSS into critical (inline) + non-critical (load with media=print + onload swap or rel=preload).
On /
