unified.to website review

Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, posthog.com and cdn-cookieyes.com and others), adding 574 KiB and 688 ms of main-thread time.

Google Tag Manager costs a phone 579 ms of main-thread work and 386 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

12 long tasks block the main thread while loading, the longest for 440 ms. During a long task the page ignores taps.

About 326 KiB of JavaScript is downloaded but never used on this page.

A phone's processor spends 2.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

12 files are served with short cache lifetimes, so returning visitors download them again (128 KiB).

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

About 19 KiB of CSS is downloaded but never applied on this page.

2 images could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB JavaScript is shipped twice across bundles.

The page becomes fully interactive after 11.9 s. Good is under 3.8 s.

Scripts block taps and scrolling for 630 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 197 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

37 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 2.0 MB in 135 requests on a phone: images 1.1 MB (73), scripts 865 KiB (39) and HTML 49 KiB (1). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (531 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example Complete-Unification.svg at 2,248 px wide, shown at 364 px. Resized copies would save about 162 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Your meta description is 260 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 124 pages on unified.to and 36 external pages.

We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

unified.to is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

unified.to has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

unified.to's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 1,435 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.