Website review, no card needed
hobbywingdirect.com website review
Visit site (opens in a new tab)Reviewed 6 November 202646 issues · 87 checks
This review found 46 issues worth fixing on hobbywingdirect.com, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
74C- #81,821 of 116,232 reviewed websitesbeats 26%
- #52,312 of 66,752 online storesbeats 18%
- #49,271 of 60,924 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 78 ms |
| May 23, 2026 | 77 ms |
| May 30, 2026 | 74 ms |
| Jun 6, 2026 | 74 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 76 ms |
| Jul 4, 2026 | 75 ms |
| Jul 11, 2026 | 75 ms |
| Jul 18, 2026 | 73 ms |
| Jul 25, 2026 | 72 ms |
| Aug 1, 2026 | 73 ms |
| Aug 8, 2026 | 72 ms |
| Aug 15, 2026 | 74 ms |
| Aug 22, 2026 | 74 ms |
| Aug 29, 2026 | 75 ms |
| Sep 5, 2026 | 75 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 74 ms |
| Sep 26, 2026 | 74 ms |
| Oct 3, 2026 | 75 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.4 s
7.4 s
8.5 s
Speed
Reduce unused JavaScript
7.0 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Improve image delivery
1.0 s · 207 KiB4 images could be 207 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.3 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 (Shopify, Vimeo and ZenDesk and others), adding 6.1 MB and 894 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 136 KiB17 files are served with short cache lifetimes, so returning visitors download them again (136 KiB).
Render-blocking requests
750 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Vimeo adds 220 ms
220 msVimeo costs a phone 220 ms of main-thread work and 5.0 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.
Legacy JavaScript
400 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Reduce unused CSS
300 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 298 ms
298 msShopify costs a phone 298 ms of main-thread work and 580 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.
ZenDesk adds 199 ms
199 msZenDesk costs a phone 199 ms of main-thread work and 394 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,233 HTML elements
The page has 2,233 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.
Duplicated JavaScript
100 ms · 5 KiB5 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 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: 23.5 s
23.5 sYour largest element takes 23.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EZRUN MAX10 G2S ESC”.
Time to Interactive: 23.5 s
23.5 sThe page becomes fully interactive after 23.5 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Total Blocking Time: 255 ms
255 msScripts block taps and scrolling for 255 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 78 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, 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).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 455 ms
455 msReal visitors wait 455 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 12.9 MB in 384 requests
12.9 MBYour homepage downloads 12.9 MB in 384 requests on a phone: media 5.2 MB (1), other files 4.8 MB (185) and scripts 2.1 MB (149). Under 2 MB keeps phones on slow connections fast.
About 3.7 g of CO₂ per visit
3.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.67 g of CO₂e: 440.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (8 elements)
ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (23 characters)
Your title is only 23 characters: “HOBBYWING North America”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“HOBBYWING North America” and “Search”). One clear main headline is easier for people and search engines.
Meta description is long (196 characters)
Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
382 internal links, 9 external
The homepage links to 382 pages on hobbywingdirect.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.hobbywingdirect.com/.
Structured data in place
Structured data found: 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://www.hobbywingdirect.com/sitemap.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.
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.
llms.txt published
The site publishes https://www.hobbywingdirect.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.hobbywingdirect.com/collections/skywalker-series and https://www.hobbywingdirect.com/collections/skywalker-motors have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.hobbywingdirect.com/collections/platinum-120a-esc-v5 and https://www.hobbywingdirect.com/collections/platinum-80a-esc-v5 use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 161 found) and read each the way a search engine does.
6 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 an H1
Each page we checked has a main headline.
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
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
24 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 58 words
The homepage has only about 58 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Download”, “Contact us” and “Learn more”.
6 short forms
6 short forms (3 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 7 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.
12 other companies contacted
Loading the homepage contacts 12 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 hobbywingdirect.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Rez Bundle Upsell · Plug In Seo · Seowill Ai Seo · Rez Preorder Back In Stock · Region Restrictions · Aftersell · li-apps.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on hobbywingdirect.com, including 20 speed issues, 5 SEO issues and 4 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.