phonexia.com website review

About 368 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

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

8 images could be 282 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

8 third-party services load with your homepage (framerusercontent.com, Google Tag Manager and ClickDimensions and others), adding 3.6 MB and 795 ms of main-thread time.

Your mobile performance score is 57 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

framerusercontent.com costs a phone 446 ms of main-thread work and 3.0 MB 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.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

Google Tag Manager costs a phone 211 ms of main-thread work and 357 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.

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

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

12 KiB could be saved by minifying JavaScript.

Desktop scores 94 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Transform audio into actionable intelligence using our on-p…”.

The first text or image appears after 7.1 s on a phone. Good is under 1.8 s.

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

Visually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your homepage downloads 3.7 MB in 97 requests on a phone: media 2.0 MB (1), scripts 1.1 MB (56) and images 468 KiB (15). Under 2 MB keeps phones on slow connections fast.

0PeGMxKzY2UhNy9uJfq1EUQC60.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example 6N404TAgvh9Y53dKfQgnt5oxs.webp at 1,918 px wide, shown at 344 px. Resized copies would save about 107 KiB.

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

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

17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 elements hidden from screen readers can still receive keyboard focus.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 54 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

8 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Who Is Saying What?” and “Who Is Saying What?”). One clear main headline is easier for people and search engines.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 84 pages on phonexia.com and 18 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://phonexia.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://phonexia.com/privacy-policy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://phonexia.com/privacy-policy all use the title “On-Premises Voice Biometrics and Speech Recognition | Phonexia”. Search engines can't tell which page to show for a search, so each competes with the others.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 502 words of visible text.

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

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

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