Website review, no card needed

indigobabyshop.com logo

indigobabyshop.com website review

Visit site (opens in a new tab)Reviewed 17 November 202623 issues · 61 checks

This review found 23 issues worth fixing on indigobabyshop.com, 4 of them high impact, across 61 checks. The most urgent: 1 image over 500 KB. 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 indigobabyshop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix100
  • Improve image delivery

    2.2 MB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cloudflare and b-cdn.net), adding 2.3 MB and 13 ms of main-thread time.

  • b-cdn.net adds 0 ms

    0 ms

    b-cdn.net costs a phone 0 ms of main-thread work and 2.2 MB 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

    12 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

3 checks passed
  • Mobile performance score: 100

    100/100

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

  • Main-thread work: 0.1 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

1 to fix100
  • 1 image without width and height

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

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

6 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “RAKYATPOKER Situs Poker Online IDN Terpercaya | Ceme & Domi…”.

  • Speed Index: 0.9 s

    0.9 s

    Visually, the page fills in at 0.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

4 to fix40
  • 1 image over 500 KB

    rakyapokeridnqqceme.png weighs 2.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    760 KiB

    1 image is downloaded at several times the size a phone draws it, for example rakyapokeridnqqceme.png at 1,672 px wide, shown at 449 px. Resized copies would save about 760 KiB.

  • 2 images in older formats

    2 images (2.2 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.

  • Page weight: 2.3 MB in 8 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 8 requests on a phone: images 2.2 MB (2), scripts 29 KiB (4) and HTML 11 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.65 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9896
  • All page content should be contained by landmarks (9 elements)

    All page content should be contained by landmarks: 9 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.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “RAKYATPOKER – Situs Poker Online Terpercaya 2026 | IDNPlay, Domino QQ & Ceme”.

  • Meta description is long (201 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and Product) but with 1 problem, for example “Product: no offers (price) block”.

  • No XML sitemap

    No XML sitemap at https://rakyatpokerr1.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 7 internal links, 15 external

    The homepage links to 7 pages on indigobabyshop.com and 15 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “RAKYATPOKER Situs Poker Online IDN Terpercaya | Ceme & Domino IDNPlay Resmi”.

  • Canonical URL set

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

AI search readiness

100
  • No llms.txt

    There is no https://rakyatpokerr1.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 form on the homepage

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

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

    The homepage carries about 682 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

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

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on indigobabyshop.com, including 4 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