Website review, no card needed
bullit.ai website review
Visit site (opens in a new tab)Reviewed 10 November 202637 issues · 71 checks
This review found 37 issues worth fixing on bullit.ai, 13 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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
72CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
9.5 s · 6.9 MB34 files are served with short cache lifetimes, so returning visitors download them again (6.9 MB).
Improve image delivery
6.8 s · 3.2 MB14 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.8 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
460 ms · 96 KiBAbout 96 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Adobe TypeKit and others), adding 410 KiB and 213 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.
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
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 245 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.2 s
25.2 sYour largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “#APP #DATA #IA VOS PERFORMANCES AU CŒUR DE NOS PRÉOCCUPATIO…”.
Time to Interactive: 26.3 s
26.3 sThe page becomes fully interactive after 26.3 s. Good is under 3.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.113
0.113The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 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.
1 checks passed
Total Blocking Time: 119 ms
119 msScripts block the page for only 119 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.3 MB in 48 requests
7.3 MBYour homepage downloads 7.3 MB in 48 requests on a phone: images 6.9 MB (29), scripts 221 KiB (4) and fonts 199 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.3 MB3 images are downloaded at several times the size a phone draws them, for example screens.png at 2,500 px wide, shown at 339 px. Resized copies would save about 1.3 MB.
14 images in older formats
14 images (5.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.
6 images below the first screen load straight away
6 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.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.07 g of CO₂e: 248.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
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.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “BULLIT | Logiciels assistés par l'IA pour les investisseurs institutionnels”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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://bullit.ai/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at bullit.ai/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
29 internal links, 8 external
The homepage links to 29 pages on bullit.ai and 8 external pages.
1 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “BULLIT est la solution SaaS embarquant l'IA qui vous accompagne au quotidien pour rester les plus performants dans votr…”.
AI search readiness
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://bullit.ai/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,992 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages share a title
/, https://bullit.ai/fr, https://bullit.ai/fr/blog, https://bullit.ai/fr/contact, https://bullit.ai/fr/blog/la-hierarchie-des-valorisations-en-europe-continentale and https://bullit.ai/fr/blog/l-impact-des-transactions-d-inites-sur-les-cours-de-bourse-des-smallcaps and 8 others all use the title “BULLIT | Logiciels assistés par l'IA pour les investisseurs instituti…”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages share a meta description
https://bullit.ai/fr, https://bullit.ai/fr/blog, https://bullit.ai/fr/contact, https://bullit.ai/fr/blog/la-hierarchie-des-valorisations-en-europe-continentale, https://bullit.ai/fr/blog/l-impact-des-transactions-d-inites-sur-les-cours-de-bourse-des-smallcaps and https://bullit.ai/fr/blog/la-representation-des-femmes-a-la-direction-des-societes-cotees-francaises and 7 others use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://bullit.ai/fr/blog, https://bullit.ai/fr/contact, https://bullit.ai/fr/blog/la-hierarchie-des-valorisations-en-europe-continentale, https://bullit.ai/fr/blog/l-impact-des-transactions-d-inites-sur-les-cours-de-bourse-des-smallcaps, https://bullit.ai/fr/blog/la-representation-des-femmes-a-la-direction-des-societes-cotees-francaises and https://bullit.ai/fr/blog/la-gestion-financiere-des-societes-cotees-en-france-par-rapport-a-celle-des-pays-nordiques and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://bullit.ai/fr/contact has 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.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 14 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 14 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 14 pages that loaded have a <title>.
Best practices
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
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.
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 1,471 words of copy
The homepage carries about 1,471 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “CONTACT”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before 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
5Opening 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.
7 other companies contacted
Loading the homepage contacts 7 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 bullit.ai, 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
- Hosting
- OVHcloud
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 bullit.ai, including 12 speed issues, 8 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.