Website review, no card needed

hibob.com logo

hibob.com website review

Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 80 checks

This review found 30 issues worth fixing on hibob.com, 13 of them high impact, across 80 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.1 s2.3 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.8 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.5 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
325 ms192 msMay 30Nov 14310 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026226 ms
Jun 6, 2026224 ms
Jun 13, 2026222 ms
Jun 20, 2026218 ms
Jun 27, 2026217 ms
Jul 4, 2026213 ms
Jul 11, 2026210 ms
Jul 18, 2026207 ms
Jul 25, 2026210 ms
Aug 1, 2026212 ms
Aug 8, 2026212 ms
Aug 15, 2026214 ms
Aug 22, 2026222 ms
Aug 29, 2026220 ms
Sep 5, 2026217 ms
Sep 12, 2026224 ms
Sep 19, 2026222 ms
Sep 26, 2026239 ms
Oct 3, 2026263 ms
Oct 10, 2026260 ms
Oct 17, 2026267 ms
Oct 24, 2026278 ms
Oct 31, 2026276 ms
Nov 7, 2026295 ms
Nov 14, 2026310 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 hibob.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hibob.com at 1.3 s1.3 s
  2. hibob.com at 2.5 s2.5 s
  3. hibob.com at 3.8 s3.8 s
  4. hibob.com at 5.0 s5.0 s
  5. hibob.com at 6.3 s6.3 s
  6. hibob.com at 7.5 s7.5 s
  7. hibob.com at 8.8 s8.8 s
  8. hibob.com at 10.0 s10.0 s

Speed

8 to fix43
  • Use efficient cache lifetimes

    1.4 s · 380 KiB

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

  • Main-thread work: 16.4 s

    A phone's processor spends 16.4 s on main-thread work while loading, 4.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 43

    43/100

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

  • 5,527 HTML elements

    The page has 5,527 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

  • 5 third-party services on the page

    5 third-party services load with your homepage (VWO, Optanon and Hubspot and others), adding 673 KiB and 786 ms of main-thread time.

  • Reduce unused JavaScript

    450 ms · 352 KiB

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

  • VWO adds 418 ms

    418 ms

    VWO costs a phone 418 ms of main-thread work and 273 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.

  • Improve image delivery

    208 KiB

    4 images could be 208 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    23 KiB

    About 23 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 205 ms

    205 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 533 ms

    533 ms

    Real visitors wait 533 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Speed Index: 12.7 s

    12.7 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

    Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One platform for your people, payroll, and finance The firs…”.

  • Tap response (INP) got 34% slower for real visitors

    +34%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

6 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.038

    0.038

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 181 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 181 requests on a phone: other files 1.4 MB (69), scripts 1.1 MB (59) and images 641 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8992
  • Elements must only use permitted ARIA attributes (7 elements)

    Elements must only use permitted ARIA attributes: 7 elements on the page fail this check, rated serious by axe-core.

  • [role="img"] and [role="image"] elements must have alternative text (6 elements)

    [role="img"] and [role="image"] elements must have alternative text: 6 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 text elements with low contrast

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), 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).

2 checks passed
  • Every image has alt text

    All 278 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 8590
  • Structured data has 1 problem

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

  • No XML sitemap

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

  • 12 links with vague text

    12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 128 internal links, 17 external

    The homepage links to 128 pages on hibob.com and 17 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Streamline HR, Payroll & Finance with HiBob. Automate processes with Bob to cut the noise. Just Enough Thinking, just t…”.

  • One H1 headline

    Your main headline reads: “One platform for your people, payroll, and finance”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “All-in-one HR software for people, payroll & finance | HiBob”.

  • Canonical URL set

    The canonical URL is https://www.hibob.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 and points crawlers to your sitemap.

AI search readiness

100
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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 5 pages slow to respond

    https://www.hibob.com/platform/core, https://www.hibob.com/platform/core/self-service, https://www.hibob.com/platform/core/analytics, https://www.hibob.com/platform/core/automation and https://www.hibob.com/integrations took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • 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 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://mapi.www.hibob.com/batch-event/' from origin 'https://www.hibob.com' has been blocked by CO…”.

2 checks passed
  • Tap targets are thumb-sized

    26 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No analytics detected

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

  • A 21-field form

    Your longest form asks for 21 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 998 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET A FREE DEMO” and “WATCH A DEMO”.

  • 35 calls to action

    The homepage has 35 calls to action, for example “Pricing”, “Get A Free Demo” and “GET A FREE DEMO”.

  • Social proof on the page

    Social proof on the homepage: 113 testimonial or review blocks, 106 customer or partner logos, 11 trust badges and “Join 5,500+ companies”.

Privacy and tracking

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

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

2 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Hiring

Hiring
1 open role
Job board
smartrecruiters

Company

Founded
2015
Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on hibob.com, including 16 speed issues, 3 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