exelatech.com website review

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

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

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

About 133 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

The page has 2,021 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 third-party services load with your homepage (Cookiebot, cloudflare.com and WordPress and others), adding 333 KiB and 213 ms of main-thread time.

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

18 KiB could be saved by minifying CSS.

1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.

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 wait 6.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “digitization”.

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

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

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

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

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

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

Your homepage downloads 13.7 MB in 136 requests on a phone: other files 5.9 MB (24), images 5.6 MB (54) and HTML 896 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

[role]s are not contained by their required parent element (5 elements).

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (2 elements).

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

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

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

Some list items are not inside a list.

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

Elements with role="none" or role="presentation" have conflicts (1 element).

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

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

The homepage links to 200 pages on exelatech.com and 14 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 /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.

/blog/xbp-europe-insights-podcast-maintaining-company-culture-across-multiple-geographies is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/fr/americas and /de/americas all use the title “Home - Americas - XBP Global”. Search engines can't tell which page to show for a search, so each competes with the others.

/solutions/invoice-to-pay and /solutions/legal-administration took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 102 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: the server responded with a status of 429 ()”.

Opening https://exelatech.com goes through 3 redirects before the homepage loads.

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

xbpglobal.com 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.

xbpglobal.com'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.

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

Your longest form asks for 16 fields (7 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

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

The page uses urgency cues (a countdown or limited-time wording).

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.

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.