Website review, no card needed

ohmybabybook.com logo

ohmybabybook.com website review

Visit site (opens in a new tab)Reviewed 12 November 202644 issues · 83 checks

This review found 44 issues worth fixing on ohmybabybook.com, 18 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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
3.3 s2.5 sMay 23Nov 72.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20262.9 s
Sep 12, 20263.2 s
Sep 19, 20263.1 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Nov 7, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
133 ms109 msMay 23Nov 7128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026113 ms
May 30, 2026117 ms
Jun 6, 2026123 ms
Jun 13, 2026126 ms
Jun 20, 2026121 ms
Jun 27, 2026126 ms
Jul 4, 2026121 ms
Jul 11, 2026129 ms
Jul 18, 2026130 ms
Jul 25, 2026130 ms
Aug 8, 2026121 ms
Aug 15, 2026128 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026127 ms
Sep 19, 2026112 ms
Nov 7, 2026128 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 ohmybabybook.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ohmybabybook.com at 0.8 s0.8 s
  2. ohmybabybook.com at 1.5 s1.5 s
  3. ohmybabybook.com at 2.3 s2.3 s
  4. ohmybabybook.com at 3.0 s3.0 s
  5. ohmybabybook.com at 3.8 s3.8 s
  6. ohmybabybook.com at 4.6 s4.6 s
  7. ohmybabybook.com at 5.3 s5.3 s
  8. ohmybabybook.com at 6.1 s6.1 s

Speed

11 to fix28
  • Use efficient cache lifetimes

    3.0 s · 1.2 MB

    63 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Improve image delivery

    1.9 s · 1.6 MB

    19 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused JavaScript

    2.1 s · 358 KiB

    About 358 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 28

    28/100

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

  • Reduce unused CSS

    840 ms · 193 KiB

    About 193 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 840 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 981 KiB and 857 ms of main-thread time.

  • Font display

    850 ms

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

  • Google Tag Manager adds 554 ms

    554 ms

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

  • Legacy JavaScript

    300 ms · 23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 112 ms

    112 ms

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

Core Web Vitals

6 to fix31
  • Largest Contentful Paint: 26.0 s

    26.0 s

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

  • Time to Interactive: 27.3 s

    27.3 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Cumulative Layout Shift: 0.369

    0.369

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

  • Total Blocking Time: 426 ms

    426 ms

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +5%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 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.

Images and page weight

4 to fix38
  • Page weight: 7.4 MB in 83 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 83 requests on a phone: images 5.9 MB (33), scripts 1.0 MB (27) and stylesheets 216 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.

  • 19 images in older formats

    19 images (5.6 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.

  • 15 images below the first screen load straight away

    15 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.09 g

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

9 to fixGoogle 8389
  • 16 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 3 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 8570
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “Oh My Baby Book — перша книга для малюка від Oh My Look! | Oh My Baby Book”.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 46 internal links, 14 external

    The homepage links to 46 pages on ohmybabybook.com and 14 external pages.

3 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Збережи найцінніші спогади про малюка на сторінках Oh My Baby Book! Мінімалістичний дизайн. Продуманий зміст. Доставка …”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

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://ohmybabybook.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.

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 fix85
  • 15 pages point its canonical at the homepage

    https://ohmybabybook.com/ua/product-category/oh-my-baby-book, https://ohmybabybook.com/ua/product/sertifikat-na-oh-my-baby-book, https://ohmybabybook.com/ua/print-photos, https://ohmybabybook.com/ua/personalization, https://ohmybabybook.com/ua/payment-delivery and https://ohmybabybook.com/ua/blog and 9 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 1 page without an H1

    https://ohmybabybook.com/ua/order has no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://ohmybabybook.com/ua/product/sertifikat-na-oh-my-baby-book, https://ohmybabybook.com/ua/print-photos, https://ohmybabybook.com/ua/personalization, https://ohmybabybook.com/ua/payment-delivery, https://ohmybabybook.com/ua/blog and https://ohmybabybook.com/ua/contacts and 8 others have 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.

  • 2 pages slow to respond

    https://ohmybabybook.com/ua/product-category/oh-my-baby-book and https://ohmybabybook.com/ua/order took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 5 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 91 words

    The homepage has only about 91 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.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “2950.00 грн Oh My Baby Book рожевий”, “2950.00 грн Oh My Baby Book бежевий” and “2950.00 грн Oh My Baby Book блакитний”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Hotjar and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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.

  • 8 cookies set on arrival

    8

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 ohmybabybook.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
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on ohmybabybook.com, including 17 speed issues, 6 SEO issues and 3 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