Website review, no card needed

dualsportplus.com logo

dualsportplus.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 87 checks

This review found 36 issues worth fixing on dualsportplus.com, 7 of them high impact, across 87 checks. The most urgent: 1 button without a name. 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.5 s986 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.0 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
107 ms83 msMay 16Oct 3186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202687 ms
Jun 13, 202686 ms
Jun 20, 202692 ms
Jun 27, 202694 ms
Jul 4, 202695 ms
Jul 11, 202697 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 2026104 ms
Aug 8, 2026103 ms
Aug 15, 2026100 ms
Aug 22, 2026102 ms
Aug 29, 202693 ms
Sep 5, 202690 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202692 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202687 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 dualsportplus.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dualsportplus.com at 0.7 s0.7 s
  2. dualsportplus.com at 1.4 s1.4 s
  3. dualsportplus.com at 2.2 s2.2 s
  4. dualsportplus.com at 2.9 s2.9 s
  5. dualsportplus.com at 3.6 s3.6 s
  6. dualsportplus.com at 4.3 s4.3 s
  7. dualsportplus.com at 5.0 s5.0 s
  8. dualsportplus.com at 5.8 s5.8 s

Speed

9 to fix70
  • Reduce unused JavaScript

    630 ms · 576 KiB

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

  • Mobile performance score: 70

    70/100

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

  • Improve image delivery

    500 ms · 281 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Yotpo and Shopify and others), adding 1.3 MB and 628 ms of main-thread time.

  • Google Maps adds 265 ms

    265 ms

    Google Maps costs a phone 265 ms of main-thread work and 463 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.

  • Yotpo adds 249 ms

    249 ms

    Yotpo costs a phone 249 ms of main-thread work and 395 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.3 s

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

  • 1,821 HTML elements

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

  • Shopify adds 107 ms

    107 ms

    Shopify costs a phone 107 ms of main-thread work and 420 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 · 76 KiB

    About 76 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.

  • Use efficient cache lifetimes

    215 KiB

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

  • 5 long tasks on the main thread

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

  • Render-blocking requests

    50 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save 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 JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 6.8 s

    6.8 s

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

  • Time to Interactive: 13.2 s

    13.2 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 88 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.2 s

    1.2 s

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

  • Real-user INP: 92 ms

    92 ms

    Real visitors wait 92 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 315 ms

    315 ms

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

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

    -22%

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

  • Total Blocking Time: 133 ms

    133 ms

    Scripts block the page for only 133 ms while loading. Good is under 200 ms.

  • 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: 3.7 MB in 224 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 224 requests on a phone: images 1.5 MB (53), scripts 1.1 MB (54) and other files 901 KiB (102). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    MAS_OBMDDX-05999-Large.jpg 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 1.0 g of CO₂ per visit

    1.05 g

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

9 to fixGoogle 7688
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    17 elements hidden from screen readers can still receive keyboard focus.

  • 3 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

1 checks passed
  • 47 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: 47 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

2 to fixGoogle 9293
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • 234 internal links, 34 external

    The homepage links to 234 pages on dualsportplus.com and 34 external pages.

6 checks passed
  • Meta description: 102 characters

    Your meta description is 102 characters: “Bikes, Apparel, Electronics, Luggage, Helmets, Boots and all your gear you need to start riding today.”.

  • One H1 headline

    Your main headline reads: “Dualsport Plus”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Dualsport Plus Adventure Motorcycle & Rider Gear”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.dualsportplus.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.

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.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.dualsportplus.com/pages/shipping-policy, https://www.dualsportplus.com/collections/outback-motortek-brand, https://www.dualsportplus.com/collections/enduristan-brand, https://www.dualsportplus.com/pages/kove, https://www.dualsportplus.com/pages/kove-part-finder and https://www.dualsportplus.com/collections/clearance have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.dualsportplus.com/pages/shipping-policy and https://www.dualsportplus.com/pages/kove-part-finder 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 118 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • 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 “Cannot read properties of null (reading 'addEventListener')”.

2 checks passed
  • Tap targets are thumb-sized

    53 of 55 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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: 15 testimonial or review blocks. 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.

  • No opening hours

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

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

    The homepage carries about 565 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ENDURISTAN” and “SHOP THE SALE”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP ENDURISTAN”, “shop the sale” and “SHOP Outback Motortek”.

  • 5 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 15 cookies set on arrival

    15

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

  • 19 other companies contacted

    Loading the homepage contacts 19 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 dualsportplus.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

Yotpo Loyalty Rewards · Judge Me Reviews · Koala Upsell Gift · Avantify Social Media Icons

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 36 issues on dualsportplus.com, including 14 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

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