Website review, no card needed
advmotoshop.com website review
Visit site (opens in a new tab)Reviewed 17 November 202643 issues · 83 checks
This review found 43 issues worth fixing on advmotoshop.com, 17 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
75C- #76,860 of 116,487 reviewed websitesbeats 30%
- #49,526 of 66,776 online storesbeats 22%
- #503 of 882 BigCommerce storesbeats 39%
Closest competitors among BigCommerce stores
Compare side by sideOne 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
Improve image delivery
6.6 s · 2.2 MB10 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.6 s faster on a phone.
Render-blocking requests
1.5 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Reduce unused CSS
910 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
760 ms · 142 KiBAbout 142 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Bigcommerce and Google Fonts), adding 3.1 MB and 196 ms of main-thread time.
Bigcommerce adds 195 ms
195 msBigcommerce costs a phone 195 ms of main-thread work and 3.1 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.
1,507 HTML elements
The page has 1,507 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 25 KiB5 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 222 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.5 s
13.5 sYour largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
2 checks passed
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 25 ms
25 msScripts block the page for only 25 ms while loading. Good is under 200 ms.
Images and page weight
3 images over 500 KB
3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.4 MB3 images are downloaded at several times the size a phone draws them, for example advmoto-backissues-new2.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 1.4 MB.
Page weight: 3.2 MB in 41 requests
3.2 MBYour homepage downloads 3.2 MB in 41 requests on a phone: images 2.6 MB (20), scripts 334 KiB (9) and stylesheets 120 KiB (5). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (668 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (11 characters)
Your title is only 11 characters: “ADVMotoShop”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (56 characters)
Your meta description is only 56 characters: “ADVMotoShop - ADVMoto Magazine Shop and Merchandise Site”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://advmotoshop.com/sitemap.xml, so Google discovers your pages only by following links.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
62 internal links, 19 external
The homepage links to 62 pages on advmotoshop.com and 19 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://advmotoshop.com/.
robots.txt in place
robots.txt is in place.
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://advmotoshop.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (912 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://advmotoshop.com/gift, which answers with an error. Visitors hit a dead end and search engines drop it.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
Best practices
13 small tap targets
13 of 50 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 street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 10-field form
Your longest form asks for 10 fields (4 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 431 words of copy
The homepage carries about 431 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “Contact Us”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “Contact us: 5714852910” and “Shop Now”.
Social proof on the page
Social proof on the homepage: 21 testimonial or review blocks and 1 trust badge.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 advmotoshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- BigCommerce
- Hosting
- Bigcommerce Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on advmotoshop.com, including 13 speed issues, 8 SEO issues and 3 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.