amazingmuscle.com website review

Signyfyd costs a phone 1.0 s of main-thread work and 280 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Adroll and others), adding 1.1 MB and 1.7 s of main-thread time.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

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

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

11 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Google Tag Manager costs a phone 316 ms of main-thread work and 438 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 37 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

9 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

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

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

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.

Your homepage downloads 3.1 MB in 266 requests on a phone: scripts 1.4 MB (73), other files 761 KiB (118) and images 644 KiB (61). Under 2 MB keeps phones on slow connections fast.

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

2 buttons have no accessible name, so screen readers announce just “button”.

6 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is only 40 characters: “Amazing Muscle Sports Nutrition Products”. 70 to 160 characters is enough to sell the click.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 96 pages on amazingmuscle.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.

https://www.amazingmuscle.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.amazingmuscle.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.amazingmuscle.com/collections/all-non-am-skus, https://www.amazingmuscle.com/collections/amazing-muscle, https://www.amazingmuscle.com/collections/clearance, https://www.amazingmuscle.com/customer_authentication/redirect, https://www.amazingmuscle.com/collections/build-muscle and https://www.amazingmuscle.com/collections/energy-and-endurance and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.amazingmuscle.com/collections/all-non-am-skus, https://www.amazingmuscle.com/collections/amazing-muscle, https://www.amazingmuscle.com/collections/clearance, https://www.amazingmuscle.com/customer_authentication/redirect, https://www.amazingmuscle.com/collections/build-muscle and https://www.amazingmuscle.com/collections/energy-and-endurance and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and TikTok Pixel (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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.