Website review, no card needed

ducatiomaha.com logo

ducatiomaha.com website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 77 checks

This review found 31 issues worth fixing on ducatiomaha.com, 10 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.1 s883 msMay 23Nov 7909 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 2026963 ms
Jun 6, 2026918 ms
Jun 13, 2026902 ms
Jun 20, 2026912 ms
Jun 27, 2026932 ms
Jul 4, 2026956 ms
Jul 11, 2026983 ms
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 2026989 ms
Aug 8, 2026992 ms
Aug 15, 2026963 ms
Aug 22, 2026945 ms
Aug 29, 2026953 ms
Sep 5, 2026916 ms
Sep 12, 2026956 ms
Sep 19, 2026969 ms
Sep 26, 2026965 ms
Oct 3, 2026995 ms
Oct 10, 2026955 ms
Oct 17, 2026949 ms
Oct 24, 2026937 ms
Oct 31, 2026929 ms
Nov 7, 2026909 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms73 msMay 23Nov 775 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202681 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202684 ms
Aug 15, 202681 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202675 ms
Sep 12, 202678 ms
Sep 19, 202679 ms
Sep 26, 202680 ms
Oct 3, 202687 ms
Oct 10, 202685 ms
Oct 17, 202679 ms
Oct 24, 202679 ms
Oct 31, 202675 ms
Nov 7, 202675 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 ducatiomaha.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ducatiomaha.com at 0.4 s0.4 s
  2. ducatiomaha.com at 0.8 s0.8 s
  3. ducatiomaha.com at 1.1 s1.1 s
  4. ducatiomaha.com at 1.5 s1.5 s
  5. ducatiomaha.com at 1.9 s1.9 s
  6. ducatiomaha.com at 2.3 s2.3 s
  7. ducatiomaha.com at 2.7 s2.7 s
  8. ducatiomaha.com at 3.0 s3.0 s

Speed

7 to fix61
  • Improve image delivery

    1.6 s · 700 KiB

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

  • Render-blocking requests

    1.7 s

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

  • Use efficient cache lifetimes

    900 ms · 123 KiB

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

  • Mobile performance score: 61

    61/100

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

  • 2,971 HTML elements

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

  • Shopify adds 112 ms

    112 ms

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

  • smile.io adds 74 ms

    74 ms

    smile.io costs a phone 74 ms of main-thread work and 459 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, smile.io and omnisnippet1.com and others), adding 967 KiB and 237 ms of main-thread time.

  • Reduce unused JavaScript

    140 ms · 88 KiB

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

  • Reduce unused CSS

    27 KiB

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

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 605 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 11.3 s

    11.3 s

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

  • Time to Interactive: 11.5 s

    11.5 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

8 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: 95 ms

    95 ms

    Real visitors wait 95 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: 611 ms

    611 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

3 to fix68
  • Page weight: 3.1 MB in 347 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 347 requests on a phone: other files 954 KiB (152), images 914 KiB (16) and scripts 726 KiB (132). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    346 KiB

    2 images are downloaded at several times the size a phone draws them, for example 20thfrontpage.jpg at 2,672 px wide, shown at 360 px. Resized copies would save about 346 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (295 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 8995
  • 33 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 1 link without text

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • Title is short (12 characters)

    Your title is only 12 characters: “Ducati Omaha”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (216 characters)

    Your meta description is 216 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 149 internal links, 20 external

    The homepage links to 149 pages on ducatiomaha.com and 20 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.ducatiomaha.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.

  • 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.ducatiomaha.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 (1,494 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 2 pages share a title

    https://www.ducatiomaha.com/pages/e-bikes-at-ducati-omaha and https://www.ducatiomaha.com/collections/cyclezoo-e-bikes-at-ducati-omaha all use the title “E-Bikes at Ducati Omaha”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.ducatiomaha.com/pages/finance-application has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.ducatiomaha.com/collections/new-ducati-motorcycles-off-road, https://www.ducatiomaha.com/pages/ducati-oem-parts, https://www.ducatiomaha.com/pages/find-accessories-by-model, https://www.ducatiomaha.com/pages/ducati-desert-x-accessories and https://www.ducatiomaha.com/pages/ducati-diavel-xdiavel-accessories 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 64 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • No phone number on the homepage

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

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

    The homepage carries about 401 words of visible text.

2 checks passed
  • 29 calls to action

    The homepage has 29 calls to action, for example “Retired Ducati Demo Models”, “Book Your Demo Ride” and “Ducati Priority Reservation Request”.

  • 4 short forms

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

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.

  • 14 cookies set on arrival

    14

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

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

Inbox · Omnisend · Year Make Model Advance Search · smile.io

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 31 issues on ducatiomaha.com, including 11 speed issues, 4 SEO issues and 6 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