amplify.com website review

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

Your mobile performance score is 36 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, salespeak.ai and Hubspot and others), adding 1.8 MB and 1.4 s of main-thread time.

Google Tag Manager costs a phone 632 ms of main-thread work and 514 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 HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

salespeak.ai costs a phone 397 ms of main-thread work and 559 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.

Hubspot costs a phone 203 ms of main-thread work and 407 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,409 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

83 KiB could be saved by minifying JavaScript.

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.

3 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A blue square note with a white star and the text, "Learn a…”.

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

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

Scripts block taps and scrolling for 812 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 436 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

Real visitors wait 1.1 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 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.7 MB in 134 requests on a phone: media 11.9 MB (1), scripts 2.6 MB (65) and stylesheets 778 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

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

The homepage links to 193 pages on amplify.com and 28 external pages.

/program-filters and /programs all use the title “Amplify | Our programs”. Search engines can't tell which page to show for a search, so each competes with the others.

/program-filters and /programs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /programs, whose canonical is /program-filters. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

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

2 links go through two or more redirects, for example https://facebook.com/AmplifyEducation.

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.

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

amplify.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 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 has only about 146 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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.

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, Hotjar and HubSpot 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 17 cookies, 1 of them by other companies (measured from a US location before any click).

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