Website review, no card needed

hbplusrc.com logo

hbplusrc.com website review

Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 77 checks

This review found 30 issues worth fixing on hbplusrc.com, 9 of them high impact, across 77 checks. The most urgent: 5,512 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.0 s845 msMay 16Oct 31881 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026981 ms
May 30, 2026913 ms
Jun 6, 2026868 ms
Jun 13, 2026892 ms
Jun 20, 2026898 ms
Jun 27, 2026911 ms
Jul 4, 2026915 ms
Jul 11, 2026917 ms
Jul 18, 2026913 ms
Jul 25, 2026905 ms
Aug 1, 2026898 ms
Aug 8, 2026899 ms
Aug 15, 2026911 ms
Aug 22, 2026942 ms
Aug 29, 2026953 ms
Sep 5, 2026911 ms
Sep 12, 2026918 ms
Sep 19, 2026909 ms
Sep 26, 2026917 ms
Oct 3, 2026917 ms
Oct 10, 2026880 ms
Oct 17, 2026887 ms
Oct 24, 2026878 ms
Oct 31, 2026881 ms
Real-visitor tap response (INP)75th percentile, phones
90 ms79 msMay 16Oct 3186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202682 ms
May 23, 202682 ms
May 30, 202680 ms
Jun 6, 202682 ms
Jun 13, 202683 ms
Jun 20, 202682 ms
Jun 27, 202686 ms
Jul 4, 202681 ms
Jul 11, 202682 ms
Jul 18, 202683 ms
Jul 25, 202684 ms
Aug 1, 202689 ms
Aug 8, 202689 ms
Aug 15, 202689 ms
Aug 22, 202689 ms
Aug 29, 202685 ms
Sep 5, 202683 ms
Sep 12, 202681 ms
Sep 19, 202681 ms
Sep 26, 202683 ms
Oct 3, 202683 ms
Oct 10, 202685 ms
Oct 17, 202685 ms
Oct 24, 202686 ms
Oct 31, 202686 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

Full-page screenshot of hbplusrc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hbplusrc.com at 1.9 s1.9 s
  2. hbplusrc.com at 3.9 s3.9 s
  3. hbplusrc.com at 5.8 s5.8 s
  4. hbplusrc.com at 7.7 s7.7 s
  5. hbplusrc.com at 9.7 s9.7 s
  6. hbplusrc.com at 11.6 s11.6 s
  7. hbplusrc.com at 13.5 s13.5 s
  8. hbplusrc.com at 15.5 s15.5 s

Speed

6 to fix74
  • 5,512 HTML elements

    The page has 5,512 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 74

    74/100

    Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    650 ms · 268 KiB

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

  • Render-blocking requests

    500 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Shopify adds 299 ms

    299 ms

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

  • Main-thread work: 2.6 s

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, shop.app and ecomsend.com), adding 544 KiB and 299 ms of main-thread time.

  • 13 long tasks on the main thread

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

  • Reduce unused JavaScript

    124 KiB

    About 124 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    17 KiB

    About 17 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    13 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Speed Index: 11.3 s

    11.3 s

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

  • Time to Interactive: 8.0 s

    8.0 s

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (4.1 s).

  • Total Blocking Time: 248 ms

    248 ms

    Scripts block taps and scrolling for 248 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 82 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 100 ms

    100 ms

    Real visitors wait 100 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 580 ms

    580 ms

    Real visitors wait 580 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-31, 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).

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.1 MB in 198 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 198 requests on a phone: other files 686 KiB (75), images 630 KiB (20) and scripts 629 KiB (65). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9093
  • 10 text elements with low contrast

    10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 34 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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

2 to fixGoogle 10092
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 236 internal links, 8 external

    The homepage links to 236 pages on hbplusrc.com and 8 external pages.

6 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Hobby Plus is a conceptualizer, designer, manufacture, implementor and marketer of hobby grade radio controlled (RC) pr…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Hobby Plus Radio Controlled Manufacturer – Hobby Plus RC”.

  • Canonical URL set

    The canonical URL is https://hbplusrc.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://hbplusrc.com/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,840 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://hbplusrc.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix71
  • 1 page points its canonical at the homepage

    https://hbplusrc.com/products/cr18p-2024-trail-hunter-brushless-4x4-rtr-matte-greene 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://hbplusrc.com/products/cr18p-2024-trail-hunter-brushless-4x4-rtr-matte-greene all use the title “Hobby Plus Radio Controlled Manufacturer – Hobby Plus RC”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://hbplusrc.com/collections/1-24-speck-t-2wd-rtr-brushed, https://hbplusrc.com/collections/1-24-speck-t-2wd-rtr-brushless, https://hbplusrc.com/collections/1-18-cr18p-evo-rock-van-4x4-rtr-crawler and https://hbplusrc.com/collections/1-18-cr18p-evo-trail-hunter-4x4-rtr-crawler have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://hbplusrc.com/products/speck-sct-1-24-2wd-rtr-brushed-choose-color and https://hbplusrc.com/products/speck-sct-1-24-2wd-rtr-brushless-choose-color use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://hbplusrc.com/products/speck-b-1-24-2wd-buggy-choose-color, https://hbplusrc.com/products/speck-b-1-24-2wd-buggy-brushless-choose-color, https://hbplusrc.com/products/speck-sct-1-24-2wd-rtr-brushed-choose-color, https://hbplusrc.com/products/speck-sct-1-24-2wd-rtr-brushless-choose-color, https://hbplusrc.com/collections/1-24-speck-t-2wd-rtr-brushed and https://hbplusrc.com/collections/1-24-speck-t-2wd-rtr-brushless and 8 others have 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 110 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

2 to fixGoogle 9687
  • 7 small tap targets

    7 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 655 words of copy

    The homepage carries about 655 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Customer Contact”, “Shop now” and “Contact information”.

  • 12 short forms

    12 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 hbplusrc.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sami Wholesale · Judge Me Reviews · Ecomsend · goaffpro.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

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on hbplusrc.com, including 10 speed issues, 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25