Website review, no card needed
outdoortechnology.com website review
Visit site (opens in a new tab)Reviewed 11 November 202641 issues · 84 checks
This review found 41 issues worth fixing on outdoortechnology.com, 21 of them high impact, across 84 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
71C- #88,474 of 109,140 reviewed websitesbeats 16%
- #54,235 of 61,805 online storesbeats 10%
- #50,451 of 56,383 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 104 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 117 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 123 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 128 ms |
| Nov 7, 2026 | 121 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.0 s
2.1 s
3.1 s
4.2 s
5.2 s
6.2 s
7.3 s
8.3 s
Speed
Reduce unused JavaScript
12.0 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.0 s faster on a phone.
Improve image delivery
4.5 s · 870 KiB7 images could be 870 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.5 s faster on a phone.
YouTube adds 1.4 s
1.4 sYouTube costs a phone 1.4 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
1.1 s · 258 KiB21 files are served with short cache lifetimes, so returning visitors download them again (258 KiB).
Mobile performance score: 20
20/100Your mobile performance score is 20. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 3.7 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 (YouTube, loox.io and Cloudflare CDN and others), adding 3.8 MB and 2.2 s of main-thread time.
Render-blocking requests
900 ms14 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused CSS
410 ms · 171 KiBAbout 171 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 410 ms faster on a phone.
1,954 HTML elements
The page has 1,954 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 87 ms
87 msShopify costs a phone 87 ms of main-thread work and 345 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.
Minify JavaScript
260 ms · 21 KiB21 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 187 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 15.6 s
15.6 sThe first text or image appears after 15.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 34.2 s
34.2 sYour largest element takes 34.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.4 s
17.4 sVisually, the page fills in at 17.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.2 s
40.2 sThe page becomes fully interactive after 40.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.435
0.435The layout shifts by 0.435 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 625 ms
625 msScripts block taps and scrolling for 625 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 688 ms
688 msReal visitors wait 688 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 7.9 MB in 333 requests
7.9 MBYour homepage downloads 7.9 MB in 333 requests on a phone: scripts 4.0 MB (105), images 2.1 MB (28) and other files 1.0 MB (155). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
ChipsPRO_Launch_Banner_Desktop_v.4_6500x2448_3d72bebb-0212-4 weighs 541 KiB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
611 KiB2 images are downloaded at several times the size a phone draws them, for example ChipsPRO_Launch_Banner_Mobile_v.4_2250x4650_3109b65a-f9e5-49 at 2,250 px wide, shown at 390 px. Resized copies would save about 611 KiB.
About 2.3 g of CO₂ per visit
2.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.25 g of CO₂e: 270.1 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
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 images without alt text
21 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
17 form fields without a label
17 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail 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.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
117 internal links, 3 external
The homepage links to 117 pages on outdoortechnology.com and 3 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Audio that keeps the good vibes flowing & Power that keeps you going. Premium helmet audio, rugged wireless speakers, a…”.
One H1 headline
Your main headline reads: “<img class="inline-block" src="//www.outdoortechnology.com/cdn/shop/files/ODT-Logo_2048x2048.png?v=1729020041" alt="Out…”.
Title: 61 characters
Your title is a healthy 61 characters: “Outdoor Tech Wireless Audio – The Original Helmet Audio Brand”.
Canonical URL set
The canonical URL is https://www.outdoortechnology.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://www.outdoortechnology.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.outdoortechnology.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.
3 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 (1,070 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
1 checks passed
Linked pages load
3 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
15 small tap targets
15 of 70 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of null (reading 'add')”.
16 distorted images
16 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 330 words of copy
The homepage carries about 330 words of visible text.
3 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Partner Shop”, “Shop All” and “Contact Us”.
14 short forms
14 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Meta Pixel and Hotjar.
Privacy and tracking
8 trackers load before any consent
8Before 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
54 other companies contacted
Loading the homepage contacts 54 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 outdoortechnology.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Videowise Video Commerce · Monster Cart Upsell Free Gifts · Monster Upsells · Avada Cookie Bar · loox.io · cloudfront.net · printful.com · govx.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
- The footer still says © 2025.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Irvine
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on outdoortechnology.com, including 18 speed issues, 2 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.