Website review, no card needed

drbrowns.lt logo

drbrowns.lt website review

Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 74 checks

This review found 41 issues worth fixing on drbrowns.lt, 19 of them high impact, across 74 checks. The most urgent: improve image delivery. 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 drbrowns.lt (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drbrowns.lt at 0.6 s0.6 s
  2. drbrowns.lt at 1.2 s1.2 s
  3. drbrowns.lt at 1.9 s1.9 s
  4. drbrowns.lt at 2.5 s2.5 s
  5. drbrowns.lt at 3.1 s3.1 s
  6. drbrowns.lt at 3.7 s3.7 s
  7. drbrowns.lt at 4.4 s4.4 s
  8. drbrowns.lt at 5.0 s5.0 s

Speed

5 to fix39
  • Improve image delivery

    46.6 s · 8.9 MB

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

  • Use efficient cache lifetimes

    7.3 s · 1.4 MB

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

  • Render-blocking requests

    2.6 s

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

  • Mobile performance score: 39

    39/100

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

  • Reduce unused JavaScript

    500 ms · 92 KiB

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

  • Minify JavaScript

    170 ms · 35 KiB

    35 KiB could be saved by minifying JavaScript.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Cloudflare CDN and Unpkg and others), adding 79 KiB and 46 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 73 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

6 to fix35
  • Largest Contentful Paint: 69.0 s

    69.0 s

    Your largest element takes 69.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DANTUKŲ PRIEŽIŪRA PRADEDANTIS VAIKŠČIOTI KŪDIKIS Dantų šepe…”.

  • Time to Interactive: 69.0 s

    69.0 s

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

  • Cumulative Layout Shift: 0.809

    0.809

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 6 images without width and height

    6 images 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.

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix25
  • Page weight: 13.0 MB in 63 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 63 requests on a phone: images 12.7 MB (31), scripts 177 KiB (14) and fonts 35 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 3 images far larger than shown

    1.7 MB

    3 images are downloaded at several times the size a phone draws them, for example OptionsPlus-home-slider-2019.jpg at 2,500 px wide, shown at 390 px. Resized copies would save about 1.7 MB.

  • 3 images in older formats

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

  • About 3.7 g of CO₂ per visit

    3.68 g

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

6 to fixGoogle 7389
  • 6 text elements with low contrast

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

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

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

  • 1 form field without a label

    1 form field has 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.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

7 to fixGoogle 6150
  • Page is set to noindex

    The robots meta tag says “noindex,follow”: Google is told not to list this page at all.

  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (16 characters)

    Your title is only 16 characters: “Dr. Brown's Baby”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • 4 links crawlers can't follow

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

  • 35 internal links, 5 external

    The homepage links to 35 pages on drbrowns.lt and 5 external pages.

5 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Simply the best baby bottle.® Dr. Brown's® creates innovative baby products to promote good health and optimal nutritio…”.

  • One H1 headline

    Your main headline reads: “DR. BROWN’S kuria inovatyvius produktus kūdikiams ir vaikams jų sveikatai ir maitinimui pagerinti.”.

  • Canonical URL set

    The canonical URL is https://drbrowns.lt/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • XML sitemap found

    Your XML sitemap is reachable at https://drbrowns.lt/sitemap.xml.

AI search readiness

1 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

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

1 checks passed
  • Organization data: 4 of 6 facts

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

Other pages

4 to fix75
  • 15 linked pages hidden from search

    https://drbrowns.lt/dr-browns-lt, https://drbrowns.lt/awards-lt, https://drbrowns.lt/faqs-lt, https://drbrowns.lt/instructions-lt, https://drbrowns.lt/dr-browns-instructional-videos-lt and https://drbrowns.lt/where-to-buy-lt and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://drbrowns.lt/en all use the title “Dr. Brown's Baby”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://drbrowns.lt/dr-browns-lt, https://drbrowns.lt/awards-lt, https://drbrowns.lt/where-to-buy-lt, https://drbrowns.lt/contact-lt, https://drbrowns.lt/pacifiers-teethers-landing-page-lt and https://drbrowns.lt/cups-solid-feeding-landing-page-lt and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://drbrowns.lt/contact-lt and https://drbrowns.lt/options-landing-page-lt 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 21 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7387
  • 6 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://drbrowns.lt/' was loaded over HTTPS, but requested an insecure stylesheet 'http://f…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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.

  • No social proof

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

  • No analytics detected

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

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

  • Only about 93 words

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

1 checks passed
  • 1 short form

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
UAB "Interneto vizija"

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on drbrowns.lt, including 11 speed issues, 7 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