Website review, no card needed

helidirect.com logo

helidirect.com website review

Visit site (opens in a new tab)Reviewed 8 November 202657 issues · 103 checks

This review found 57 issues worth fixing on helidirect.com, 24 of them high impact, across 103 checks. The most urgent: render-blocking requests. 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
2.7 s2.2 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
237 ms172 msMay 16Oct 31229 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026182 ms
May 23, 2026179 ms
May 30, 2026181 ms
Jun 6, 2026179 ms
Jun 13, 2026179 ms
Jun 20, 2026182 ms
Jun 27, 2026180 ms
Jul 4, 2026181 ms
Jul 11, 2026187 ms
Jul 18, 2026187 ms
Jul 25, 2026190 ms
Aug 1, 2026202 ms
Aug 8, 2026206 ms
Aug 15, 2026215 ms
Aug 22, 2026221 ms
Aug 29, 2026217 ms
Sep 5, 2026210 ms
Sep 12, 2026202 ms
Sep 19, 2026197 ms
Sep 26, 2026199 ms
Oct 3, 2026201 ms
Oct 10, 2026209 ms
Oct 17, 2026218 ms
Oct 24, 2026222 ms
Oct 31, 2026229 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 helidirect.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. helidirect.com at 1.1 s1.1 s
  2. helidirect.com at 2.2 s2.2 s
  3. helidirect.com at 3.3 s3.3 s
  4. helidirect.com at 4.5 s4.5 s
  5. helidirect.com at 5.6 s5.6 s
  6. helidirect.com at 6.7 s6.7 s
  7. helidirect.com at 7.8 s7.8 s
  8. helidirect.com at 8.9 s8.9 s

Speed

14 to fix34
  • Render-blocking requests

    1.8 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • 12,089 HTML elements

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

  • Main-thread work: 10.8 s

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

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cookiebot, Google Tag Manager and Shopify and others), adding 2.8 MB and 1.7 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

  • Reduce unused JavaScript

    984 KiB

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

  • Use efficient cache lifetimes

    200 ms · 766 KiB

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

  • Improve image delivery

    350 ms · 239 KiB

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

  • Google Tag Manager adds 449 ms

    449 ms

    Google Tag Manager costs a phone 449 ms of main-thread work and 711 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.

  • Cookiebot adds 457 ms

    457 ms

    Cookiebot costs a phone 457 ms of main-thread work and 163 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.

  • Shopify adds 328 ms

    328 ms

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

  • cloudfront.net adds 107 ms

    107 ms

    cloudfront.net costs a phone 107 ms of main-thread work and 299 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.

  • azurefd.net adds 55 ms

    55 ms

    azurefd.net costs a phone 55 ms of main-thread work and 321 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.

  • Reduce unused CSS

    150 ms · 91 KiB

    About 91 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    63 KiB

    Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 53 ms

    53 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Time to Interactive: 33.7 s

    33.7 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 9.9 s

    9.9 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

    The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 336 ms

    336 ms

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

4 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 633 ms

    633 ms

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

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

    -11%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

2 to fix60
  • Page weight: 6.3 MB in 492 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 492 requests on a phone: scripts 3.2 MB (181), other files 1.4 MB (179) and images 1.0 MB (74). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    2 KiB

    1 image is downloaded at several times the size a phone draws it, for example 33581ae3-2aa3-432a-88b0-f9a2b2881436.png at 900 px wide, shown at 295 px. Resized copies would save about 2 KiB.

  • About 1.8 g of CO₂ per visit

    1.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.79 g of CO₂e: 215.0 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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

19 to fixGoogle 6578
  • Certain ARIA roles must be contained by particular parents (6 elements)

    Certain ARIA roles must be contained by particular parents: 6 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must contain particular children (4 elements)

    Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 17 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

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

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle 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.

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

  • 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 (17 elements)

    All page content should be contained by landmarks: 17 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.

  • 52 form fields without a label

    52 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 6 links without text

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

  • 2 tap targets too small

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 68 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 16 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10084
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “HeliDirect - Your #1 Sources for R/C Helicopters, Cars, Jets and More.”.

  • No robots.txt

    There is no robots.txt at helidirect.com/robots.txt, the first file search crawlers ask for.

  • One H1 headline

    Your <h1> is empty.

  • 449 internal links, 4 external

    The homepage links to 449 pages on helidirect.com and 4 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “HeliDirect has a huge selection of RC helicopters, helicopter toys and remote control helicopter. Get ultra fast shippi…”.

  • Canonical URL set

    The canonical URL is https://www.helidirect.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.helidirect.com/sitemap.xml.

AI search readiness

1 to fix81
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.helidirect.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
  • Text is in the HTML

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.helidirect.com/pages/black-friday and https://www.helidirect.com/collections/goosky-helicopter-kit have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.helidirect.com/pages/black-friday, https://www.helidirect.com/collections/new-arrivals, https://www.helidirect.com/collections/helicopter-kits and https://www.helidirect.com/collections/goosky-helicopter-kit 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 178 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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 ()”.

2 checks passed
  • Tap targets are thumb-sized

    111 of 136 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 51 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 12-field form

    Your longest form asks for 12 fields (0 required). Every extra field lowers completion.

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

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

    The homepage carries about 1,759 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop All Kits”, “Shop By Categories” and “« Shop now »”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 46 other companies contacted

    Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 helidirect.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 22 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Cookiebot Cmp · Simprosys Google Shopping Feed · Ufe · Littledata The Data Layer · Gempages Builder · Rebuy Personalization Engine · Judge Me Reviews · Microsoft Clarity · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Cms Shopify · Upsell Funnel Engine Upsells · Pushowl · smile.io · recovermycart.com · helixo.co · fugu-it.com · cloudfront.net · kxcdn.com · bogos.io · 9gtb.com · Swym Wishlist Plus

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Malden

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on helidirect.com, including 24 speed issues, 3 SEO issues and 5 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