amount.com website review

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

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

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

About 167 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

99 KiB could be saved by minifying JavaScript.

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

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

4 third-party services load with your homepage (Google Tag Manager, Optanon and Google CDN and others), adding 630 KiB and 331 ms of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

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

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

13 KiB JavaScript is shipped twice across bundles.

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

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.

Your largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When you visit any website, it may collect and store inform…”.

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

Visually, the page fills in at 7.7 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.

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

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

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

The layout shifts by 0.132 while loading, so content jumps under the reader's thumb. Good is under 0.1.

7 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-24, real Chrome visitors' tap response (inp) went from 197 ms to 185 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.8 MB in 74 requests on a phone: scripts 1.5 MB (34), images 547 KiB (11) and fonts 388 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example products-area-callout-computer.webp at 1,236 px wide, shown at 354 px. Resized copies would save about 16 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.8 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: 2 elements on the page fail this check, rated serious by axe-core.

ARIA attributes must be used as specified for the element's role: 1 element on the page fails this check, rated serious by axe-core.

5 images have no alt text, which hurts accessibility and image search.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 5 <h1> headlines (“Unified, AI-powered platform for digital account …”, “How does Origination Suite simplify digital depos…” and “How does Origination Suite accelerate lending ori…”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, FAQPage, Organization and Product) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

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

The homepage links to 60 pages on amount.com and 10 external pages.

/developers is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/global-sustainability and /about-us/ethics use the same meta description. A description written for each page earns more clicks.

/about-us/media-room, /about-us/awards, /about-us/ethics and /fisinnovatein48 have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://players.brightcove.net/5076297064001/default_default/index.min.js' violates the following C…”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

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.

X-XSS-Protection is set to “1;mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

fisglobal.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

fisglobal.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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 687 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 Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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