Website review, no card needed

kidyzz.com logo

kidyzz.com website review

Visit site (opens in a new tab)Reviewed 16 November 202610 issues · 59 checks

This review found 10 issues worth fixing on kidyzz.com, 3 of them high impact, across 59 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

Full-page screenshot of kidyzz.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix85
  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 85

    85/100

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

  • Improve image delivery

    250 ms · 92 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, Google Tag Manager and WordPress and others), adding 535 KiB and 250 ms of main-thread time.

  • Use efficient cache lifetimes

    187 KiB

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

  • Reduce unused CSS

    150 ms · 37 KiB

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

  • Reduce unused JavaScript

    175 KiB

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

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    17 KiB

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

  • 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: 0.7 s

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

  • Server response: 498 ms

    498 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 7.6 s

    7.6 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

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

    1.3 s

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 751 ms

    751 ms

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.35 g

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

1 checks passed
  • Page weight: 1.2 MB in 82 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 82 requests on a phone: scripts 559 KiB (36), images 420 KiB (12) and fonts 136 KiB (3). That is a lean page.

Accessibility

1 to fix95
  • 90 text elements with low contrast

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

  • Headings skip levels

    Headings skip levels (h1 → h3), 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. (1 element).

1 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

SEO

Google 100100
  • 126 internal links, 4 external

    The homepage links to 126 pages on kidyzz.com and 4 external pages.

8 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Are you looking baby Shop in Dhaka, Bangladesh? You are in the right place. We have many types of Toys, Kids Book & Dra…”.

  • One H1 headline

    Your main headline reads: “Heaven for Childhood Delight”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Best Baby Shop in Dhaka, Bangladesh - KidyZz”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and ToyStore.

  • 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://kidyzz.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://kidyzz.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
  • 4 linked pages are broken

    Your homepage links to https://kidyzz.com/contact, https://kidyzz.com/product/%f0%9d%90%8f%f0%9d%90%ab%f0%9d%90%a8%f0%9d%90%a3%f0%9d%90%9e%f0%9d%90%9c%f0%9d%90%ad%f0%9d%90%a2%f0%9d%90%a7%f0%9d%90%a0-%f0%9d%90%85%f0%9d%90%a5%f0%9d%90%9a%f0%9d%90%ac%f0%9d%90%a1%f0%9d%90%a5, https://kidyzz.com/product/parenting-book and https://kidyzz.com/product/baby-sensory-squeeze-balls-set-6pcs, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages without a meta description

    https://kidyzz.com/product-category/toy, https://kidyzz.com/product-category/book, https://kidyzz.com/product-category/mom-baby and https://kidyzz.com/product-category/gear have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://kidyzz.com/about has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://kidyzz.com/shop, https://kidyzz.com/product/premium-baby-rattle-and-teether-ball-1-pcs and https://kidyzz.com/product/talking-dancing-cactus-%f0%9f%8c%b5%f0%9f%8c%b5 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 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 11 pages that loaded have a <title>.

Best practices

Google 100100
1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 872 words of copy

    The homepage carries about 872 words of visible text.

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact”, “Shop Now” and “Alphabet (Cloth Book)”.

  • Social proof on the page

    Social proof on the homepage: 16 testimonial or review blocks, a star rating and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on 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 kidyzz.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Code For Host Inc Ltd

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 10 issues on kidyzz.com, including 6 speed issues. 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