gomacro.com website review

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

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

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

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

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

8 third-party services load with your homepage (rebuyengine.com, Klaviyo and Shopify and others), adding 1.5 MB and 360 ms of main-thread time.

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

rebuyengine.com costs a phone 120 ms of main-thread work and 648 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 1,752 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 50 ms of main-thread work and 506 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.

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

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

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

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

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

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.

For real visitors the layout shifts by 0.96 (75th percentile). Good is under 0.1.

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

Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GoMacro Buy Two Get One”.

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

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

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

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

Your homepage downloads 5.5 MB in 292 requests on a phone: images 2.5 MB (54), scripts 1.5 MB (87) and other files 785 KiB (106). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example Jessica.png at 671 px wide, shown at 150 px. Resized copies would save about 181 KiB.

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

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

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

Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 175 pages on gomacro.com and 8 external pages.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

2 links go through two or more redirects, for example https://gomacro.com/customer_authentication/redirect?locale=en&region_country=US.

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.

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

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

Social proof on the homepage: 68 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 552 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 Klaviyo (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 21 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.