haloboard.com website review

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

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

About 274 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.

8 third-party services load with your homepage (Affirm, Shopify and Google CDN and others), adding 809 KiB and 1.1 s of main-thread time.

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

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

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

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

Affirm costs a phone 336 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 costs a phone 220 ms of main-thread work and 305 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.

49 KiB could be saved by minifying JavaScript.

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

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop any of Halo Board's award-winning products. You'll fin…”.

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

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

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 2.1 MB in 207 requests on a phone: scripts 1,016 KiB (71), other files 688 KiB (90) and images 159 KiB (23). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 52 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

There are 2 <h1> headlines (“” and “OFFICIAL HALO BOARD™”). One clear main headline is easier for people and search engines.

The homepage links to 74 pages on haloboard.com and 12 external pages.

There is no /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.

/pages/halo-drone 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.

/ and /pages/halo-drone all use the title “Award-Winning Electric Skateboards & Hoverboards | Halo Board”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'threshold'”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

haloboard.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 496 words of visible text.

DMARC is set to p=none, so mail pretending to be haloboard.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 mores (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.

Opening the homepage sets 18 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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