Programmable

Website review, no card needed

ritotrike.com logo

ritotrike.com website review

Visit site (opens in a new tab)Reviewed 8 November 202624 issues · 73 checks

This review found 24 issues worth fixing on ritotrike.com, 2 of them high impact, across 73 checks. The most urgent: hidden but focusable. 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

Site score

91A

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.4 s1.1 sMay 23Sep 121.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.2 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
82 ms67 msMay 30Sep 569 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202678 ms
Jun 6, 202679 ms
Jun 13, 202674 ms
Jul 11, 202679 ms
Jul 18, 202673 ms
Jul 25, 202677 ms
Aug 1, 202673 ms
Aug 8, 202674 ms
Aug 15, 202680 ms
Aug 22, 202673 ms
Aug 29, 202671 ms
Sep 5, 202669 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

qplayshop.com (opens in a new tab)
Full-page screenshot of ritotrike.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ritotrike.com at 0.6 s0.6 s
  2. ritotrike.com at 1.2 s1.2 s
  3. ritotrike.com at 1.8 s1.8 s
  4. ritotrike.com at 2.4 s2.4 s
  5. ritotrike.com at 3.0 s3.0 s
  6. ritotrike.com at 3.6 s3.6 s
  7. ritotrike.com at 4.2 s4.2 s
  8. ritotrike.com at 4.8 s4.8 s

Speed

3 to fix93

  • Use efficient cache lifetimes

    494 KiB

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

  • Render-blocking requests

    350 ms

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

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.1 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 (Clarity, Shopify and Hexton and others), adding 417 KiB and 286 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 224 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    167 KiB

    About 167 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    96 KiB

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

  • Reduce unused CSS

    35 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed

  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix99

  • Speed Index: 5.9 s

    5.9 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Largest Contentful Paint: 1.9 s

    1.9 s

    Your largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Our Trikes, Balance Bikes, and Scooters are functionally an…”.

  • Total Blocking Time: 87 ms

    87 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

1 to fix85

  • Page weight: 2.4 MB in 211 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 211 requests on a phone: images 882 KiB (21), other files 852 KiB (129) and scripts 591 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (36 KiB) is 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.

  • 1 image below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.68 g

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

3 to fixGoogle 9796

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

  • 2 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 10087

  • No structured data

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

  • Meta description is long (316 characters)

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

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 49 internal links, 1 external

    The homepage links to 49 pages on ritotrike.com and 1 external page.

5 checks passed

  • One H1 headline

    Your main headline reads: “Rito Trike”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “The Rito Trike - The Ultimate Folding Trike”.

  • Canonical URL set

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

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix76

  • 3 pages share a title

    https://qplayshop.com/collections/the-rito-plus/products/midnight-edition-rito-plus-folding-trike, https://qplayshop.com/collections/the-rito-plus/products/black-rito-plus-folding-trike-1 and https://qplayshop.com/collections/the-rito-plus/products/grey-rito-plus-folding-trike-1 all use the title “Black Rito Plus Folding Trike - Smart Trike for Kids – Rito Trike”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://qplayshop.com/pages/rito-trike, https://qplayshop.com/pages/balance-bikes, https://qplayshop.com/pages/racer-bikes, https://qplayshop.com/pages/tech-balance-bikes and https://qplayshop.com/pages/rito-trike-warranty-registration have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://qplayshop.com/collections/the-rito-plus/products/midnight-edition-rito-plus-folding-trike, https://qplayshop.com/collections/the-rito-plus/products/black-rito-plus-folding-trike-1, https://qplayshop.com/collections/the-rito-plus/products/grey-rito-plus-folding-trike-1, https://qplayshop.com/collections/the-rito-plus/products/glacier-gray-rito-plus-folding-trike, https://qplayshop.com/collections/the-rito-plus/products/sequoia-green-rito-plus-folding-trike and https://qplayshop.com/collections/the-rito-plus/products/sierra-brown-rito-plus-folding-trike use the same meta description. A description written for each page earns more clicks.

  • 6 links to non-canonical URLs

    Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://qplayshop.com/collections/the-rito-plus/products/midnight-edition-rito-plus-folding-trike, whose canonical is https://qplayshop.com/products/midnight-edition-rito-plus-folding-trike. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://qplayshop.com/pages/rito-trike, https://qplayshop.com/pages/stages-of-the-rito-trike, https://qplayshop.com/pages/balance-bikes, https://qplayshop.com/pages/racer-bikes, https://qplayshop.com/pages/tech-balance-bikes and https://qplayshop.com/collections/scooters and 3 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 27 found) and read each the way a search engine does.

3 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 9693

  • 4 JavaScript errors while loading

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

2 checks passed

  • Tap targets are thumb-sized

    26 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93

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

  • About 436 words of copy

    The homepage carries about 436 words of visible text.

6 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY THE RITO TRIKE”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Buy the Rito Folding Trike”, “Contact Us” and “Subscribe”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 17 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Microsoft Clarity (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.

  • 13 cookies set on arrival

    13

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 ritotrike.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

Okendo · Powerful Form Builder · Instagram Story App · nofraud.com · chimpstatic.com · gorgias.chat · hextom.com · useifsapp.com · 9gtb.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

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on ritotrike.com, including 7 speed issues, 4 SEO issues and 1 conversion gap. 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