Website review, no card needed
myamazonguy.com website review
Visit site (opens in a new tab)Reviewed 27 October 202635 issues · 89 checks
This review found 35 issues worth fixing on myamazonguy.com, 14 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #68,824 of 123,940 reviewed websitesbeats 39%
- #44,546 of 69,726 online storesbeats 31%
- #1,097 of 2,897 WooCommerce storesbeats 57%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 248 ms |
| May 16, 2026 | 248 ms |
| May 23, 2026 | 243 ms |
| May 30, 2026 | 229 ms |
| Jun 6, 2026 | 224 ms |
| Jun 13, 2026 | 225 ms |
| Jun 20, 2026 | 227 ms |
| Jun 27, 2026 | 229 ms |
| Jul 4, 2026 | 237 ms |
| Jul 11, 2026 | 248 ms |
| Jul 18, 2026 | 254 ms |
| Jul 25, 2026 | 274 ms |
| Aug 1, 2026 | 286 ms |
| Aug 8, 2026 | 288 ms |
| Aug 15, 2026 | 291 ms |
| Aug 22, 2026 | 300 ms |
| Aug 29, 2026 | 329 ms |
| Sep 5, 2026 | 344 ms |
| Sep 12, 2026 | 375 ms |
| Sep 19, 2026 | 379 ms |
| Sep 26, 2026 | 371 ms |
| Oct 3, 2026 | 376 ms |
| Oct 10, 2026 | 360 ms |
| Oct 17, 2026 | 354 ms |
| Oct 24, 2026 | 342 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.8 s · 517 KiB8 files are served with short cache lifetimes, so returning visitors download them again (517 KiB).
Google Tag Manager adds 1.9 s
1.9 sGoogle Tag Manager costs a phone 1.9 s of main-thread work and 539 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.
Reduce unused JavaScript
1.2 s · 399 KiBAbout 399 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.3 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.3 s.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 90). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.5 s
A phone's processor spends 9.5 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and reddit and others), adding 1.1 MB and 3.3 s of main-thread time.
Facebook adds 587 ms
587 msFacebook costs a phone 587 ms of main-thread work and 283 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 520 ms. During a long task the page ignores taps.
reddit adds 416 ms
416 msreddit costs a phone 416 ms of main-thread work and 35 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 adds 266 ms
266 msHubspot costs a phone 266 ms of main-thread work and 242 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.
2,244 HTML elements
The page has 2,244 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 90 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Improve image delivery
4 KiB1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 checks passed
Server response: 27 ms
27 msYour server sent the HTML in 27 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “amazon agency steven home page 2025 768x471 mobile”.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 320 ms
320 msReal visitors wait 320 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 248 ms to 342 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 80 requests
2.2 MBYour homepage downloads 2.2 MB in 80 requests on a phone: scripts 1.1 MB (12), fonts 823 KiB (6) and HTML 116 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (167 elements)
All page content should be contained by landmarks: 167 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 85 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
244 internal links, 32 external
The homepage links to 244 pages on myamazonguy.com and 32 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “My Amazon Guy is a full-service Amazon agency. Get your products seen and sold. Learn from experts to boost sales, adve…”.
One H1 headline
Your main headline reads: “The Amazon agency that gets your products seen and sold”.
Title: 48 characters
Your title is a healthy 48 characters: “My Amazon Guy: Full-Service Amazon Growth Agency”.
Canonical URL set
The canonical URL is https://myamazonguy.com/.
Structured data in place
Structured data found: ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://myamazonguy.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://myamazonguy.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,572 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://myamazonguy.com/webinars is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://myamazonguy.com/careers/it-specialist has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://myamazonguy.com/news, https://myamazonguy.com/articles, https://myamazonguy.com/webinars, https://myamazonguy.com/mag-partnership, https://myamazonguy.com/amazon-expert-steven-pope and https://myamazonguy.com/jobs and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://myamazonguy.com/news, https://myamazonguy.com/amazon-expert-steven-pope, https://myamazonguy.com/jobs/employee-reviews and https://myamazonguy.com/jobs/brand-director have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 pages slow to respond
https://myamazonguy.com/mag-partnership, https://myamazonguy.com/amazon-expert-steven-pope, https://myamazonguy.com/seller-support-sucks, https://myamazonguy.com/jobs/employee-reviews, https://myamazonguy.com/jobs/internships and https://myamazonguy.com/jobs/brand-director and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,203 words of copy
The homepage carries about 1,203 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Fast quote” and “Contact Us”.
17 calls to action
The homepage has 17 calls to action, for example “Apply Here (We’re Hiring!)”, “Cold Call Specialist – PH” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 3 customer or partner logos, a star rating, 3 trust badges and “400+ brands”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar, HubSpot and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
No consent tool detected
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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at myamazonguy.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on myamazonguy.com, including 22 speed issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.