Website review, no card needed

b4b.hr logo

b4b.hr website review

Visit site (opens in a new tab)Reviewed 23 October 202637 issues · 76 checks

This review found 37 issues worth fixing on b4b.hr, 16 of them high impact, across 76 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 b4b.hr (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. b4b.hr at 1.0 s1.0 s
  2. b4b.hr at 2.0 s2.0 s
  3. b4b.hr at 3.0 s3.0 s
  4. b4b.hr at 3.9 s3.9 s
  5. b4b.hr at 4.9 s4.9 s
  6. b4b.hr at 5.9 s5.9 s
  7. b4b.hr at 6.9 s6.9 s
  8. b4b.hr at 7.9 s7.9 s

Speed

8 to fix40
  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    2.1 s · 651 KiB

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

  • Font display

    1.3 s

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

  • Mobile performance score: 40

    40/100

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

  • Improve image delivery

    2.6 MB

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

  • Minify JavaScript

    540 ms · 121 KiB

    121 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    556 KiB

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

  • Google Tag Manager adds 170 ms

    170 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and Cloudflare CDN and others), adding 498 KiB and 203 ms of main-thread time.

  • Reduce unused CSS

    190 ms · 51 KiB

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

  • 1 long task on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 40. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

  • Server response: 115 ms

    115 ms

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

Core Web Vitals

6 to fix43
  • Speed Index: 15.0 s

    15.0 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “D3036e7a f188 4762 b369 d6a11ce3759f”. Most of its time is resource load delay (4.8 s).

  • Cumulative Layout Shift: 0.426

    0.426

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

  • Time to Interactive: 9.9 s

    9.9 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • 87 images without width and height

    87 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: 15 ms

    15 ms

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

Images and page weight

5 to fix18
  • Page weight: 9.2 MB in 111 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 111 requests on a phone: images 8.0 MB (95), scripts 852 KiB (7) and fonts 281 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 27 images far larger than shown

    5.4 MB

    27 images are downloaded at several times the size a phone draws them, for example 1fe5b376-ba6c-4aec-82ad-85e1afa06e12.jpg at 1,472 px wide, shown at 147 px. Resized copies would save about 5.4 MB.

  • 3 images over 500 KB

    3 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

  • 39 images in older formats

    39 images (7.4 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.

  • 35 images below the first screen load straight away

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

  • About 2.6 g of CO₂ per visit

    2.60 g

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

Accessibility

3 to fixGoogle 8493
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 33 text elements with low contrast

    33 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 (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 95 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 9274
  • Title is short (9 characters)

    Your title is only 9 characters: “B4B | b4b”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“SAP Business ByDesign s hrvatskom lokalizacijom j…”, “Mi smo regionalni SAP konzalting ekspertni centar” and “Ostvarite veće zadovoljstvo korisnika.”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

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

  • 10 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 37 internal links, 86 external

    The homepage links to 37 pages on b4b.hr and 86 external pages.

3 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Implementacija, podrška i edukacija o SAP sustavima su glavna područja našeg djelovanja. Naše prednosti su duboko razum…”.

  • 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

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.

  • No llms.txt

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

2 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 (865 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 5 pages share 2 titles

    /, https://b4b.hr/hr and https://b4b.hr/en all use the title “B4B | b4b”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without an H1

    https://b4b.hr/hr/pravne-stranice/1-gdpr and https://b4b.hr/hr/pravne-stranice/2-polica-privatnosti have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://b4b.hr/hr/kontakt, https://b4b.hr/hr/podrska, https://b4b.hr/hr/pravne-stranice/1-gdpr and https://b4b.hr/hr/pravne-stranice/2-polica-privatnosti 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.

  • 4 pages slow to respond

    https://b4b.hr/hr/podrska, https://b4b.hr/en, https://b4b.hr/hr/solutions/11-sap-business-bydesign and https://b4b.hr/hr/usluge/1-implementacija took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

5 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 meta description

    All 15 pages that loaded have a meta description.

  • 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 10093
  • 6 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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

4 to fix40
  • 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.

  • Thin social proof

    Social proof on the homepage: 77 customer or partner logos. 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 form on the homepage

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

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

    The homepage carries about 849 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 5 cookies set on arrival

    5

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

  • 4 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on b4b.hr, including 14 speed issues, 6 SEO issues and 4 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