Website review, no card needed
getbob.io website review
Visit site (opens in a new tab)Reviewed 8 November 202629 issues · 78 checks
This review found 29 issues worth fixing on getbob.io, 3 of them high impact, across 78 checks. The most urgent: 20 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (website-files.com, Google Tag Manager and Hubspot and others), adding 1.6 MB and 252 ms of main-thread time.
Reduce unused JavaScript
326 KiBAbout 326 KiB of JavaScript is downloaded but never used on this page.
website-files.com adds 96 ms
96 mswebsite-files.com costs a phone 96 ms of main-thread work and 1.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
50 ms · 102 KiB10 files are served with short cache lifetimes, so returning visitors download them again (102 KiB).
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Reduce unused CSS
48 KiBAbout 48 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
43 KiB2 images could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 445 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Accompagnez sereinement vos clients vers la facture électro…”. Most of its time is element render delay (2.5 s).
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.
2 checks passed
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Total Blocking Time: 19 ms
19 msScripts block the page for only 19 ms while loading. Good is under 200 ms.
Images and page weight
17 images below the first screen load straight away
17 images further down the page (788 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
7 images far larger than shown
367 KiB7 images are downloaded at several times the size a phone draws them, for example 6a2050cfb0eac1b7ac35c066_Logo_cogesten.svg at 1,327 px wide, shown at 145 px. Resized copies would save about 367 KiB.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.8 MB in 62 requests
1.8 MBYour homepage downloads 1.8 MB in 62 requests on a phone: images 931 KiB (36), scripts 590 KiB (16) and fonts 216 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
20 text elements with low contrast
20 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 (53 elements)
All page content should be contained by landmarks: 53 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 47 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (FAQPage, Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.
13 internal links, 7 external
The homepage links to 13 pages on getbob.io and 7 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “La plateforme qui permet aux cabinets comptables de sécuriser la conformité Facture électronique de leurs clients. 150 …”.
One H1 headline
Your main headline reads: “Accompagnez sereinement vos clients vers la facture électronique”.
Title: 61 characters
Your title is a healthy 61 characters: “getBob — Accompagnez vos clients vers la Facture électronique”.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.getbob.io/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.getbob.io/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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,183 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.getbob.io/contacts and https://www.getbob.io/mentions-legales are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without a meta description
https://www.getbob.io/mentions-legales has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.getbob.io/contacts has no <h1> headline, so visitors and search engines get no clear main topic.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
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.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "currentWidth".”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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 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 1,086 words of copy
The homepage carries about 1,086 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 54 testimonial or review blocks and 26 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 5 of them by other companies (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.
15 other companies contacted
Loading the homepage contacts 15 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 getbob.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Analytics
- Google Analytics
- Hosting
- Webflow
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on getbob.io, including 9 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.