amprg.com website review

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

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

8 third-party services load with your homepage (cdn-website.com, Google Tag Manager and userway.org and others), adding 1.4 MB and 350 ms of main-thread time.

cdn-website.com costs a phone 180 ms of main-thread work and 1.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 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

2 images could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Got a goal? We've got ideas.”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

There are 3 <h1> headlines (“Management Consulting”, “Management Consulting” and “Management Consulting”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 53 pages on amprg.com and 6 external pages.

/, /project-page, /improving-recruiting-velocity, /growing-pains-at-a-turbo-charged-fintech-firm and /transforming-a--700b--asset-management-firm-s-fragmented-systems-into-streamlined-operations all use the title “Amplify Resources Group | Strategic Consulting Services”. Search engines can't tell which page to show for a search, so each competes with the others.

/project-page, /improving-recruiting-velocity, /growing-pains-at-a-turbo-charged-fintech-firm and /transforming-a--700b--asset-management-firm-s-fragmented-systems-into-streamlined-operations use the same meta description. A description written for each page earns more clicks.

/project-page, /improving-recruiting-velocity, /growing-pains-at-a-turbo-charged-fintech-firm and /transforming-a--700b--asset-management-firm-s-fragmented-systems-into-streamlined-operations have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'register')”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 links from your homepage to your own site are broken, for example https://www.amprg.com/mission (404).

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.

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

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

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

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 291 words of visible text.

amprg.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 9 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.