Website review, no card needed

kaleyra.com logo

kaleyra.com website review

Visit site (opens in a new tab)Reviewed 25 October 202639 issues · 91 checks

This review found 39 issues worth fixing on kaleyra.com, 16 of them high impact, across 91 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
6.3 s3.8 sMay 2Oct 174.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.3 s
May 9, 20265.3 s
May 16, 20265.7 s
May 23, 20265.8 s
May 30, 20265.9 s
Jun 6, 20265.9 s
Jun 13, 20265.9 s
Jun 20, 20266.0 s
Jun 27, 20266.0 s
Jul 4, 20266.0 s
Jul 11, 20265.9 s
Jul 18, 20265.8 s
Jul 25, 20265.7 s
Aug 1, 20265.6 s
Aug 8, 20265.1 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.8 s
Sep 5, 20264.9 s
Sep 12, 20264.9 s
Sep 19, 20264.7 s
Sep 26, 20264.6 s
Oct 3, 20264.4 s
Oct 10, 20264.3 s
Oct 17, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
546 ms275 msMay 2Oct 17318 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026333 ms
May 9, 2026335 ms
May 16, 2026447 ms
May 23, 2026502 ms
May 30, 2026515 ms
Jun 6, 2026514 ms
Jun 13, 2026512 ms
Jun 20, 2026510 ms
Jun 27, 2026505 ms
Jul 4, 2026502 ms
Jul 11, 2026502 ms
Jul 18, 2026489 ms
Jul 25, 2026479 ms
Aug 1, 2026460 ms
Aug 8, 2026367 ms
Aug 15, 2026306 ms
Aug 22, 2026326 ms
Aug 29, 2026380 ms
Sep 5, 2026401 ms
Sep 12, 2026409 ms
Sep 19, 2026410 ms
Sep 26, 2026379 ms
Oct 3, 2026348 ms
Oct 10, 2026339 ms
Oct 17, 2026318 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 kaleyra.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kaleyra.com at 1.0 s1.0 s
  2. kaleyra.com at 2.1 s2.1 s
  3. kaleyra.com at 3.1 s3.1 s
  4. kaleyra.com at 4.2 s4.2 s
  5. kaleyra.com at 5.2 s5.2 s
  6. kaleyra.com at 6.2 s6.2 s
  7. kaleyra.com at 7.3 s7.3 s
  8. kaleyra.com at 8.3 s8.3 s

Speed

13 to fix39
  • Render-blocking requests

    1.7 s

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 7.3 s

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

  • 3,797 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (hsappstatic.net, Google Tag Manager and Hubspot and others), adding 2.9 MB and 2.3 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 1.2 MB

    118 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • hsappstatic.net adds 607 ms

    607 ms

    hsappstatic.net costs a phone 607 ms of main-thread work and 712 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.

  • Google Tag Manager adds 576 ms

    576 ms

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

  • Google CDN adds 333 ms

    333 ms

    Google CDN costs a phone 333 ms of main-thread work and 807 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.

  • 20 long tasks on the main thread

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

  • Hubspot adds 352 ms

    352 ms

    Hubspot costs a phone 352 ms of main-thread work and 373 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.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Reduce unused CSS

    150 ms · 97 KiB

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

  • Minify JavaScript

    150 ms · 16 KiB

    16 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

  • Improve image delivery

    131 KiB

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

  • Legacy JavaScript

    37 KiB

    Polyfills for old browsers add 37 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: 41 ms

    41 ms

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

Core Web Vitals

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

  • Time to Interactive: 37.3 s

    37.3 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Intelligent. Seamless. Scalable Let's connect every convers…”.

  • Speed Index: 9.5 s

    9.5 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 923 ms

    923 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -20%

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

  • Cumulative Layout Shift: 0.073

    0.073

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

Images and page weight

3 to fix35
  • Page weight: 6.2 MB in 267 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 267 requests on a phone: scripts 3.3 MB (71), images 1.8 MB (64) and other files 531 KiB (82). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Gaurav Anand Tata Communications.jpg weighs 963 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    938 KiB

    1 image is downloaded at several times the size a phone draws it, for example Gaurav Anand Tata Communications.jpg at 6,048 px wide, shown at 328 px. Resized copies would save about 938 KiB.

  • 1 image below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.76 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 9294
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 11 tap targets too small

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

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

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

  • 6 links without text

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

  • 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 (h1 → h3, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 78 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 4 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
  • 11 links crawlers can't follow

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

  • 239 internal links, 20 external

    The homepage links to 239 pages on kaleyra.com and 20 external pages.

8 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Enhance total experience with Kaleyra. Use CPaaS for seamless engagement, UCaaS for workforce collaboration, and CCaaS …”.

  • One H1 headline

    Your main headline reads: “Let's connect every conversation, from your teams to your customers”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Tata Communications Kaleyra Transforming Total Experience”.

  • Canonical URL set

    The canonical URL is https://www.tatacommunications.com/kaleyra.

  • Structured data in place

    Structured data found: BreadcrumbList and 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.tatacommunications.com/sitemap.xml.

AI search readiness

100
4 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 (2,196 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.tatacommunications.com/llms.txt (149 KiB, 892 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 pages without an H1

    /, https://www.tatacommunications.com/investors and https://www.tatacommunications.com/contact-us 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 83 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

4 to fixGoogle 6970
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187022623&tm=gtm002&Ver=2&mid=94b0e5f2-f828-4323-abee-6829a7b29891&bo=1&sid=e4fad250d0a811f19b0eddf8da050652&vid=e4fb0da0d0a811f194febdfe795ec76a&vids=1&msclkid=N&pi=9.

  • 15 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 1,094 words of copy

    The homepage carries about 1,094 words of visible text.

4 checks passed
  • 25 calls to action

    The homepage has 25 calls to action, for example “New customer? Start here”, “Sign Up” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, 8 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and HubSpot.

Privacy and tracking

  • 9 trackers load before any consent

    9

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

  • 21 cookies set on arrival

    21

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

  • 57 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 kaleyra.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
HubSpot CMS
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on kaleyra.com, including 23 speed issues, 1 SEO issue and 2 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