Website review, no card needed
amainhobbies.com website review
Visit site (opens in a new tab)Reviewed 11 October 202638 issues · 68 checks
This review found 38 issues worth fixing on amainhobbies.com, 15 of them high impact, across 68 checks. The most urgent: avoid multiple page redirects. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 986 ms |
| Apr 25, 2026 | 995 ms |
| May 2, 2026 | 998 ms |
| May 9, 2026 | 989 ms |
| May 16, 2026 | 972 ms |
| May 23, 2026 | 959 ms |
| May 30, 2026 | 952 ms |
| Jun 6, 2026 | 954 ms |
| Jun 13, 2026 | 953 ms |
| Jun 20, 2026 | 955 ms |
| Jun 27, 2026 | 960 ms |
| Jul 4, 2026 | 943 ms |
| Jul 11, 2026 | 935 ms |
| Jul 18, 2026 | 937 ms |
| Jul 25, 2026 | 939 ms |
| Aug 1, 2026 | 950 ms |
| Aug 8, 2026 | 956 ms |
| Aug 15, 2026 | 962 ms |
| Aug 22, 2026 | 969 ms |
| Aug 29, 2026 | 970 ms |
| Sep 5, 2026 | 956 ms |
| Sep 12, 2026 | 936 ms |
| Sep 19, 2026 | 931 ms |
| Sep 26, 2026 | 934 ms |
| Oct 3, 2026 | 948 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 140 ms |
| Apr 25, 2026 | 141 ms |
| May 2, 2026 | 141 ms |
| May 9, 2026 | 141 ms |
| May 16, 2026 | 140 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 140 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 153 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 151 ms |
| Sep 26, 2026 | 147 ms |
| Oct 3, 2026 | 146 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.6 s
1.2 s
1.8 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Avoid multiple page redirects
10.1 sThe page goes through 1 redirect before it starts loading, costing about 10.1 s. Link and advertise the final URL directly.
Reduce unused JavaScript
4.1 s · 879 KiBAbout 879 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.1 s
A phone's processor spends 9.1 s on main-thread work while loading, 6.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,543 HTML elements
The page has 4,543 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.
Reduce unused CSS
600 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Minify JavaScript
600 ms · 34 KiB34 KiB could be saved by minifying JavaScript.
Minify CSS
300 ms · 18 KiB18 KiB could be saved by minifying CSS.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Cloudflare and Other Google APIs/SDKs and others), adding 1.2 MB and 146 ms of main-thread time.
Google CDN adds 134 ms
134 msGoogle CDN costs a phone 134 ms of main-thread work and 297 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.
amain.com adds 1 ms
1 msamain.com costs a phone 1 ms of main-thread work and 899 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
First Contentful Paint: 8.0 s
8.0 sThe first text or image appears after 8.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 16.5 s
16.5 sYour largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 27.4 s
27.4 sThe page becomes fully interactive after 27.4 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 227 ms
227 msReal visitors wait 227 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
52 images without width and height
52 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 140 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 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.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 498 ms
498 msReal visitors wait 498 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 38.0 MB in 287 requests
38.0 MBYour homepage downloads 38.0 MB in 287 requests on a phone: images 35.2 MB (181), scripts 2.2 MB (41) and stylesheets 311 KiB (14). Under 2 MB keeps phones on slow connections fast.
About 10.8 g of CO₂ per visit
10.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.77 g of CO₂e: 1292.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 checks passed
Every image has alt text
All 116 images in the HTML carry an alt attribute.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “AMain Hobbies - Shop a huge selection of Toy RC Cars, Planes, Helicopters and more!”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,187 internal links, 8 external
The homepage links to 1,187 pages on amainhobbies.com and 8 external pages.
4 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “When you want to lay down some serious speed or tear through the sky with cool tricks, shop with us for a great selectio”.
Canonical URL set
The canonical URL is https://www.amainhobbies.com/.
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://www.amainhobbies.com/sitemapindex.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.amainhobbies.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.
1 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.
Other pages
1 page points its canonical at the homepage
https://www.amainhobbies.com/skins/accessible declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.amainhobbies.com/skins/accessible all use the title “AMain Hobbies - Shop a huge selection of Toy RC Cars, Planes, Helicop…”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.amainhobbies.com/contact-us, https://www.amainhobbies.com/rc-parts-department and https://www.amainhobbies.com/brands have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.amainhobbies.com/skins/accessible has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 194 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 console errors
6 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 400 (Bad Request)”).
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 3,444 words of copy
The homepage carries about 3,444 words of visible text.
3 checks passed
111 calls to action
The homepage has 111 calls to action, for example “Contact Us”, “Shop All Top Brands” and “Shop All Cars & Trucks”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
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 amainhobbies.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on amainhobbies.com, including 20 speed issues, 6 SEO issues and 2 conversion gaps. 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.