Website review, no card needed

dynacraftwheels.com logo

dynacraftwheels.com website review

Visit site (opens in a new tab)Reviewed 23 October 202643 issues · 89 checks

This review found 43 issues worth fixing on dynacraftwheels.com, 17 of them high impact, across 89 checks. The most urgent: page weight: 20.1 MB in 277 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.0 s1.2 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.8 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
150 ms107 msMay 2Oct 17131 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026120 ms
May 9, 2026114 ms
May 16, 2026112 ms
May 23, 2026112 ms
May 30, 2026115 ms
Jun 6, 2026120 ms
Jun 13, 2026125 ms
Jun 20, 2026129 ms
Jun 27, 2026130 ms
Jul 4, 2026136 ms
Jul 11, 2026139 ms
Jul 18, 2026145 ms
Jul 25, 2026138 ms
Aug 1, 2026136 ms
Aug 8, 2026131 ms
Aug 15, 2026121 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026133 ms
Sep 19, 2026130 ms
Sep 26, 2026130 ms
Oct 3, 2026129 ms
Oct 10, 2026133 ms
Oct 17, 2026131 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 dynacraftwheels.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dynacraftwheels.com at 1.0 s1.0 s
  2. dynacraftwheels.com at 2.0 s2.0 s
  3. dynacraftwheels.com at 3.0 s3.0 s
  4. dynacraftwheels.com at 4.0 s4.0 s
  5. dynacraftwheels.com at 5.0 s5.0 s
  6. dynacraftwheels.com at 6.0 s6.0 s
  7. dynacraftwheels.com at 7.0 s7.0 s
  8. dynacraftwheels.com at 8.0 s8.0 s

Speed

12 to fix18
  • hsappstatic.net adds 1.0 s

    1.0 s

    hsappstatic.net costs a phone 1.0 s of main-thread work and 697 KiB 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.

  • Main-thread work: 10.3 s

    A phone's processor spends 10.3 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: 18

    18/100

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

  • 3,714 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Google CDN and others), adding 3.0 MB and 3.4 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Improve image delivery

    500 ms · 640 KiB

    14 images could be 640 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.

  • Google Tag Manager adds 796 ms

    796 ms

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

  • Render-blocking requests

    700 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Google CDN adds 503 ms

    503 ms

    Google CDN costs a phone 503 ms of main-thread work and 733 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.

  • 20 long tasks on the main thread

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

  • Shopify adds 367 ms

    367 ms

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

  • Use efficient cache lifetimes

    250 ms · 236 KiB

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

  • Reduce unused CSS

    150 ms · 96 KiB

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

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 46 but mobile only 18. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 16 ms

    16 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 13.4 s

    13.4 s

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

  • Time to Interactive: 35.9 s

    35.9 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Cumulative Layout Shift: 0.223

    0.223

    The layout shifts by 0.223 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 1 image without width and height

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

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

    +13%

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

  • Largest content (LCP) got 15% slower for real visitors

    +15%

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

3 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 144 ms

    144 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

Images and page weight

3 to fix62
  • Page weight: 20.1 MB in 277 requests

    20.1 MB

    Your homepage downloads 20.1 MB in 277 requests on a phone: media 13.4 MB (3), scripts 3.1 MB (93) and images 2.0 MB (44). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    menu.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).

  • 12 images below the first screen load straight away

    12 images further down the page (630 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.7 g of CO₂ per visit

    5.69 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.69 g of CO₂e: 682.3 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 7988
  • 15 buttons without a name

    15 buttons have no accessible name, so screen readers announce just “button”.

  • 23 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

  • 12 images without alt text

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

  • All page content should be contained by landmarks (2 elements)

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 9 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), 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. (3 elements).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9289
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Dynacraft Wheels | Shop Bikes, Scooters & Ride-Ons for Kids & Teens”.

  • Structured data has 1 problem

    Structured data found (Organization, Product and WebSite) but with 1 problem, for example “Product: missing name”.

  • 188 internal links, 5 external

    The homepage links to 188 pages on dynacraftwheels.com and 5 external pages.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Discover Dynacraft Wheels—trusted for 40+ years, offering quality bikes, scooters, and ride-ons built for kids, teens, …”.

  • One H1 headline

    Your main headline reads: “Dynacraft Wheels”.

  • Canonical URL set

    The canonical URL is https://dynacraftwheels.com/.

  • 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://dynacraftwheels.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,201 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix85
  • 15 pages without a meta description

    https://dynacraftwheels.com/pages/contact, https://dynacraftwheels.com/pages/faqs, https://dynacraftwheels.com/collections/seasonal-picks, https://dynacraftwheels.com/collections/in-store-only, https://dynacraftwheels.com/collections/new-arrivals and https://dynacraftwheels.com/collections/all and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://dynacraftwheels.com/collections/electric-ride-ons/Electric-Ride-Ons, whose canonical is https://dynacraftwheels.com/collections/electric-ride-ons. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://dynacraftwheels.com/collections/seasonal-picks, https://dynacraftwheels.com/collections/in-store-only, https://dynacraftwheels.com/collections/new-arrivals, https://dynacraftwheels.com/collections/all, https://dynacraftwheels.com/collections/kids-bikes and https://dynacraftwheels.com/collections/pre-school and 7 others 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 81 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.

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

Best practices

3 to fixGoogle 7385
  • 9 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of null (reading 'clientHeight')”.

  • 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

2 to fix83
  • 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 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 689 words of copy

    The homepage carries about 689 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “Shop Now”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Contact”, “Shop” and “Shop Our Top Deals discover more”.

  • 20 short forms

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

  • Social proof on the page

    Social proof on the homepage: 2 trust badges and “More Than 20+ brands”.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 31 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 dynacraftwheels.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on dynacraftwheels.com, including 21 speed issues, 2 SEO issues and 2 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