alphapoint.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Hubspot and others), adding 1.1 MB and 602 ms of main-thread time.

About 108 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.

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

23 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

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

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

website-files.com costs a phone 86 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.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

3 images could be 34 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.

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

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

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Your homepage downloads 2.8 MB in 76 requests on a phone: media 1.6 MB (1), scripts 870 KiB (31) and images 123 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 130 pages on alphapoint.com and 10 external pages.

/case-studies/how-coinext-became-a-top-brazilian-crypto-exchange and /case-studies/bancolombia-group-brings-digital-asset-exchange-wenia-to-retail-customers have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343094472&tm=gtm002&Ver=2&mid=e1faffbd-a1ea-4845-a957-86abcf726f57&bo=1&sid=f1924930cf0b11f1b27eeb6660e2af1d&vid=f1927bc0cf0b11f19d3027903c8c4b25&vids=1&msclkid=N&gtm_.

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

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

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

alphapoint.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.

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

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 599 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 Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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