Website review, no card needed

blip.ai logo

blip.ai website review

Visit site (opens in a new tab)Reviewed 2 November 202636 issues · 88 checks

This review found 36 issues worth fixing on blip.ai, 9 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. 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
5.4 s3.6 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.2 s
May 23, 20265.1 s
May 30, 20264.9 s
Jun 6, 20264.6 s
Jun 13, 20264.5 s
Jun 20, 20264.4 s
Jun 27, 20264.5 s
Jul 4, 20264.4 s
Jul 11, 20264.3 s
Jul 18, 20264.3 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.9 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
558 ms327 msMay 16Oct 31487 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026380 ms
May 23, 2026369 ms
May 30, 2026360 ms
Jun 6, 2026354 ms
Jun 13, 2026359 ms
Jun 20, 2026372 ms
Jun 27, 2026371 ms
Jul 4, 2026381 ms
Jul 11, 2026390 ms
Jul 18, 2026396 ms
Jul 25, 2026420 ms
Aug 1, 2026424 ms
Aug 8, 2026434 ms
Aug 15, 2026450 ms
Aug 22, 2026460 ms
Aug 29, 2026477 ms
Sep 5, 2026465 ms
Sep 12, 2026476 ms
Sep 19, 2026488 ms
Sep 26, 2026495 ms
Oct 3, 2026531 ms
Oct 10, 2026511 ms
Oct 17, 2026505 ms
Oct 24, 2026502 ms
Oct 31, 2026487 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 blip.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blip.ai at 0.4 s0.4 s
  2. blip.ai at 0.8 s0.8 s
  3. blip.ai at 1.1 s1.1 s
  4. blip.ai at 1.5 s1.5 s
  5. blip.ai at 1.9 s1.9 s
  6. blip.ai at 2.3 s2.3 s
  7. blip.ai at 2.6 s2.6 s
  8. blip.ai at 3.0 s3.0 s

Speed

3 to fix96
  • Use efficient cache lifetimes

    1,021 KiB

    51 files are served with short cache lifetimes, so returning visitors download them again (1,021 KiB).

  • Improve image delivery

    359 KiB

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

  • 1,952 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (hsappstatic.net, Unpkg and Hubspot and others), adding 318 KiB and 164 ms of main-thread time.

  • Reduce unused JavaScript

    137 KiB

    About 137 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    100 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

  • Reduce unused CSS

    32 KiB

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

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

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

  • Server response: 137 ms

    137 ms

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

Core Web Vitals

7 to fix50
  • 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 LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

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

    +32%

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

  • Speed Index: 4.8 s

    4.8 s

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

  • 4 images without width and height

    4 images have no width and height attributes, so the layout jumps as each one loads.

7 checks passed
  • Real-user CLS: 0.02

    0.02

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

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

    -25%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.2 s to 3.8 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.01

    0.01

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Conversations that drive results. Intelligence that never s…”.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

4 to fix58
  • 3 images over 500 KB

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

  • 5 images in older formats

    5 images (2.7 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.

  • 1 image below the first screen load straight away

    1 image further down the page (767 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    282 KiB

    2 images are downloaded at several times the size a phone draws them, for example blip_site_home_demo_catalogo_en.gif at 1,080 px wide, shown at 310 px. Resized copies would save about 282 KiB.

  • About 0.5 g of CO₂ per visit

    0.50 g

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

1 checks passed
  • Page weight: 1.8 MB in 60 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 60 requests on a phone: fonts 721 KiB (3), scripts 496 KiB (42) and images 490 KiB (10). That is a lean page.

Accessibility

12 to fixGoogle 8386
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • lang attribute must have a valid value (3 elements)

    lang attribute must have a valid value: 3 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (2 elements)

    Contentinfo landmark should not be contained in another landmark: 2 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.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo 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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 45 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 6 links crawlers can't follow

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

  • 27 internal links, 4 external

    The homepage links to 27 pages on blip.ai and 4 external pages.

8 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Conversas que geram resultado. Descubra como marcas enterprise transformam cada interação em crescimento com a Blip.”.

  • One H1 headline

    Your main headline reads: “Conversations that drive results. Intelligence that never stops learning.”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Blip: Inteligência Conversacional para resultado de negócio”.

  • Canonical URL set

    The canonical URL is https://www.blip.ai/en/en/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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.blip.ai/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.blip.ai/llms.txt (62 KiB, 371 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

5 to fix76
  • 2 pages share a title

    https://www.blip.ai/plataforma-blip and https://www.blip.ai/en/platform all use the title “Blip Platform: Inteligência conversacional enterprise”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.blip.ai/portal-de-privacidade-e-seguranca-2 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.blip.ai/plataforma-blip and https://www.blip.ai/en/platform use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.blip.ai/en/ns-plataforma-atrair-clientes-en, whose canonical is https://www.blip.ai/en/platform/attract. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://www.blip.ai/contato, https://www.blip.ai/en/contact-us, https://www.blip.ai/en/ns-plataforma-atrair-clientes-en, https://www.blip.ai/en/plataforma-blip-interaja-en, https://www.blip.ai/en/old-platform/converta-en and https://www.blip.ai/en/professional-services and 2 others 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 23 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.

  • 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

2 to fixGoogle 8891
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “form_url is not a valid field name on the form”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    10 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 547 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: “SCHEDULE A CONSULTATION”.

  • 1 call to action

    The homepage has 1 call to action, for example “SCHEDULE A CONSULTATION”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

  • 40 other companies contacted

    Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

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

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 blip.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Vue.js
Analytics
Google Tag Manager
Hosting
Azure

Hiring

Hiring
15 open roles
Teams
PEOPLE & MANAGEMENT (3), SOLUTIONS (2), DATA & ANALYTICS (1), EXPAND (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on blip.ai, including 10 speed issues, 1 SEO issue and 1 conversion gap. 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