paradromics.com website review

About 3.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 38.9 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 20.1 s.

3 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.

4 third-party services load with your homepage (JSDelivr CDN, Google Tag Manager and Google Analytics and others), adding 23.3 MB and 268 ms of main-thread time.

Vimeo costs a phone 0 ms of main-thread work and 23.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.

About 178 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

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

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

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

11 KiB could be saved by minifying JavaScript.

8 KiB could be saved by minifying CSS.

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.2 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 53.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Some of the most important breakthroughs”.

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

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

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

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

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

Your homepage downloads 36.3 MB in 58 requests on a phone: media 25.6 MB (5), stylesheets 3.8 MB (7) and other files 3.8 MB (8). Under 2 MB keeps phones on slow connections fast.

‘I-Have-a-Lot-to-Say-Brain-Implant-Helps-a-Disabled-Patient- weighs 1.6 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example ‘I-Have-a-Lot-to-Say-Brain-Implant-Helps-a-Disabled-Patient- at 1,489 px wide, shown at 310 px. Resized copies would save about 1,002 KiB.

2 images further down the page (1.7 MB) 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 10.29 g of CO₂e: 1234.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

There are 2 <h1> headlines (“Some of the most important breakthroughs” and “Start with a simple act of connection”). One clear main headline is easier for people and search engines.

2 links have no real href, so search engines can't follow them.

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

The homepage links to 37 pages on paradromics.com and 10 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://paradromics.com/platform, https://paradromics.com/company and https://paradromics.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 13 pages linked from your homepage 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.

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 295 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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