Website review, no card needed

crabi.com logo

crabi.com website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 84 checks

This review found 32 issues worth fixing on crabi.com, 14 of them high impact, across 84 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.6 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
155 ms126 msMay 2Oct 17135 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026150 ms
May 9, 2026151 ms
May 16, 2026144 ms
May 23, 2026141 ms
May 30, 2026135 ms
Jun 6, 2026131 ms
Jun 13, 2026129 ms
Jun 20, 2026132 ms
Jun 27, 2026135 ms
Jul 4, 2026135 ms
Jul 11, 2026137 ms
Jul 18, 2026132 ms
Jul 25, 2026133 ms
Aug 1, 2026138 ms
Aug 8, 2026133 ms
Aug 15, 2026144 ms
Aug 22, 2026148 ms
Aug 29, 2026147 ms
Sep 5, 2026152 ms
Sep 12, 2026150 ms
Sep 19, 2026144 ms
Sep 26, 2026144 ms
Oct 3, 2026140 ms
Oct 10, 2026133 ms
Oct 17, 2026135 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 crabi.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix37
  • Render-blocking requests

    5.7 s

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

  • Reduce unused JavaScript

    2.1 s · 603 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 241 KiB

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

  • Mobile performance score: 37

    37/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, posthog.com and website-files.com and others), adding 2.0 MB and 1.9 s of main-thread time.

  • Google Tag Manager adds 945 ms

    945 ms

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

  • posthog.com adds 394 ms

    394 ms

    posthog.com costs a phone 394 ms of main-thread work and 216 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.

  • Main-thread work: 3.0 s

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

  • website-files.com adds 161 ms

    161 ms

    website-files.com costs a phone 161 ms of main-thread work and 596 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.

  • 18 long tasks on the main thread

    18 long tasks block the main thread while loading, the longest for 234 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    100 ms · 91 KiB

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

  • Legacy JavaScript

    150 ms · 40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Duplicated JavaScript

    150 ms · 7 KiB

    7 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    26 KiB

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

  • Minify CSS

    18 KiB

    18 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 74 but mobile only 37. 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.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 13.3 s

    13.3 s

    Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cuidamos lo que te mueve 🚙”.

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Time to Interactive: 17.0 s

    17.0 s

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

  • Total Blocking Time: 1.0 s

    1.0 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 14 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 126 ms

    126 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 586 ms

    586 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.3 MB in 75 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 75 requests on a phone: scripts 1.6 MB (25), fonts 521 KiB (11) and images 140 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.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

5 to fixGoogle 8792
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 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 (18 elements)

    All page content should be contained by landmarks: 18 elements on the page fail 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.

  • 7 links without text

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

  • 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 36 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 7 H1 headlines

    There are 7 <h1> headlines (“Cuidamos lo que te mueve 🚙”, “Daños materiales” and “Robo total del auto”). One clear main headline is easier for people and search engines.

  • 28 internal links, 15 external

    The homepage links to 28 pages on crabi.com and 15 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “En Crabi Seguros estamos transformando los seguros de autos en México. Te ofrecemos planes de protección a la medida y …”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Crabi Autoseguros | Cuidamos lo que te mueve 🚙”.

  • Canonical URL set

    The canonical URL is https://www.crabi.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.crabi.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.crabi.com/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 contact details; description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix88
  • 4 pages without a meta description

    https://www.crabi.com/servicios, https://www.crabi.com/crabi-pass, https://www.crabi.com/preguntas-frecuentes and https://www.crabi.com/support/solicitudes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.crabi.com/legal/referencias-legales and https://www.crabi.com/legal/condiciones-generales use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.crabi.com/support/solicitudes and https://www.crabi.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.crabi.com/support/solicitudes and https://www.crabi.com/legal/referencias-legales 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 20 found) 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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 9693
  • 2 small tap targets

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

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

3 to fix50
  • 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: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 748 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 14 cookies set on arrival

    14

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 crabi.com, 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
Framework
Bootstrap
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 32 issues on crabi.com, including 17 speed issues, 1 SEO issue 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