Website review, no card needed

dashstartoys.com logo

dashstartoys.com website review

Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 85 checks

This review found 39 issues worth fixing on dashstartoys.com, 13 of them high impact, across 85 checks. The most urgent: render-blocking 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
4.3 s2.2 sMay 30Nov 143.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.0 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.0 s
Aug 15, 20262.7 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20263.2 s
Sep 26, 20263.6 s
Oct 3, 20263.2 s
Oct 10, 20263.9 s
Oct 17, 20264.0 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.5 s
Nov 14, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
198 ms113 msMay 30Nov 14144 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026123 ms
Jun 20, 2026165 ms
Jun 27, 2026160 ms
Jul 4, 2026167 ms
Jul 11, 2026171 ms
Jul 18, 2026149 ms
Jul 25, 2026168 ms
Aug 1, 2026188 ms
Aug 8, 2026139 ms
Aug 15, 2026141 ms
Aug 22, 2026132 ms
Aug 29, 2026124 ms
Sep 5, 2026155 ms
Sep 12, 2026154 ms
Sep 19, 2026152 ms
Sep 26, 2026155 ms
Oct 3, 2026128 ms
Oct 10, 2026124 ms
Oct 17, 2026130 ms
Oct 24, 2026142 ms
Oct 31, 2026146 ms
Nov 7, 2026144 ms
Nov 14, 2026144 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 dashstartoys.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dashstartoys.com at 0.8 s0.8 s
  2. dashstartoys.com at 1.5 s1.5 s
  3. dashstartoys.com at 2.3 s2.3 s
  4. dashstartoys.com at 3.1 s3.1 s
  5. dashstartoys.com at 3.9 s3.9 s
  6. dashstartoys.com at 4.6 s4.6 s
  7. dashstartoys.com at 5.4 s5.4 s
  8. dashstartoys.com at 6.2 s6.2 s

Speed

11 to fix57
  • Render-blocking requests

    7.8 s

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

  • Reduce unused CSS

    1.5 s · 296 KiB

    About 296 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • 3,026 HTML elements

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

  • Reduce unused JavaScript

    900 ms · 175 KiB

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

  • Mobile performance score: 57

    57/100

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

  • Use efficient cache lifetimes

    400 ms · 380 KiB

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

  • Document request latency

    750 ms

    The HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    728 ms

    Reduce initial server response time. Google estimates savings of 728 ms on a phone.

  • Font display

    650 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

  • Main-thread work: 2.8 s

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

  • Server response: 828 ms

    828 ms

    Your server takes 828 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify JavaScript

    150 ms · 19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Improve image delivery

    104 KiB

    3 images could be 104 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    17 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (hostinger.com and Google Fonts), adding 135 KiB and 3 ms of main-thread time.

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

Core Web Vitals

8 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 LCP: 4.5 s

    4.5 s

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

  • Largest Contentful Paint: 15.4 s

    15.4 s

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

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

  • Time to Interactive: 15.8 s

    15.8 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed
  • Real-user INP: 153 ms

    153 ms

    Real visitors wait 153 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 59 ms

    59 ms

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

Images and page weight

3 to fix53
  • Page weight: 18.1 MB in 177 requests

    18.1 MB

    Your homepage downloads 18.1 MB in 177 requests on a phone: media 14.1 MB (1), images 2.5 MB (33) and scripts 627 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (1.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • An image on the first screen is lazy-loaded

    BU8-650x572.png 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 5.1 g of CO₂ per visit

    5.14 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9493
  • All page content should be contained by landmarks (10 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

    13 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 (h1 → h6, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 168 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

3 to fixGoogle 8584
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:title, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 302 internal links, 23 external

    The homepage links to 302 pages on dashstartoys.com and 23 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Dash star – Dash Star Grow With Us”.

  • Canonical URL set

    The canonical URL is https://dashstartoys.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://dashstartoys.com/wp-sitemap.xml.

AI search readiness

1 to fix83
  • 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://dashstartoys.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.

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://dashstartoys.com/product/humr-ev, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages without a meta description

    https://dashstartoys.com/about-us, https://dashstartoys.com/shop, https://dashstartoys.com/product-category/cars, https://dashstartoys.com/product-category/ev, https://dashstartoys.com/product-category/ride-ons and https://dashstartoys.com/product-category/scooters and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://dashstartoys.com/wp-content/uploads/2020/05/product-image5-copyright.jpg.

  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 142 words

    The homepage has only about 142 words of visible text; thin pages give Google and first-time buyers little to go on.

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

5 checks passed
  • Clear next step on the first screen

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

  • 35 calls to action

    The homepage has 35 calls to action, for example “Contact us”, “Get in touch” and “Shop Now”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 6 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 4 email links.

Privacy and tracking

  • 8 cookies set on arrival

    8

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

  • 3 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 dashstartoys.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on dashstartoys.com, including 19 speed issues, 3 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