Website review, no card needed

cognizant.com logo

cognizant.com website review

Visit site (opens in a new tab)Reviewed 14 November 202620 issues · 75 checks

This review found 20 issues worth fixing on cognizant.com, 5 of them high impact, across 75 checks. The most urgent: 1 linked page is broken. 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.2 s2.6 sMay 23Nov 72.9 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Nov 7, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
190 ms179 msMay 23Nov 7183 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026182 ms
May 30, 2026182 ms
Jun 6, 2026181 ms
Jun 13, 2026180 ms
Jun 20, 2026182 ms
Jun 27, 2026182 ms
Jul 4, 2026185 ms
Jul 11, 2026185 ms
Jul 18, 2026188 ms
Jul 25, 2026189 ms
Aug 1, 2026186 ms
Aug 8, 2026189 ms
Aug 15, 2026186 ms
Aug 22, 2026186 ms
Aug 29, 2026186 ms
Sep 5, 2026185 ms
Sep 12, 2026184 ms
Sep 19, 2026181 ms
Sep 26, 2026184 ms
Oct 3, 2026185 ms
Oct 10, 2026185 ms
Oct 17, 2026187 ms
Oct 24, 2026185 ms
Oct 31, 2026184 ms
Nov 7, 2026183 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 cognizant.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix91
  • 3,074 HTML elements

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

  • Render-blocking requests

    900 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused CSS

    150 ms · 54 KiB

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

  • Reduce unused JavaScript

    173 KiB

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

  • Improve image delivery

    116 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 91

    91/100

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

  • Main-thread work: 0.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

1 to fix100
  • Cumulative Layout Shift: 0.196

    0.196

    The layout shifts by 0.196 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

11 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 179 ms

    179 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 789 ms

    789 ms

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

  • Time to Interactive: 2.7 s

    2.7 s

    The page is fully interactive after 2.7 s.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • 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 image.

  • Speed Index: 1.3 s

    1.3 s

    Visually, the page fills in at 1.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    media_16ab1842af7bccc892919b14a1616a0587b419ba5.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.2 g of CO₂ per visit

    0.21 g

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

3 checks passed
  • Page weight: 746 KiB in 74 requests

    746 KiB

    Your homepage downloads 746 KiB in 74 requests on a phone: images 326 KiB (11), fonts 159 KiB (4) and scripts 140 KiB (29). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9497
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Skip links are not focusable.

    Skip links are not focusable. (1 element).

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 25 links with vague text

    25 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("https://www.cognizant.com/content/cognizant-dot-com/us/en/home")”.

  • 22 internal links, 7 external

    The homepage links to 22 pages on cognizant.com and 7 external pages.

6 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “The most impactful AI isn’t bought—it’s built. We bridge the gap between the AI that’s out there, and the AI your busin…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “AI Builders Bridging the Gap from AI to Impact | Cognizant”.

  • Canonical URL set

    The canonical URL is https://www.cognizant.com/us/en.

  • 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.cognizant.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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://www.cognizant.com/fragments/us/en/site/contactus_widget_form/sticky_contact_us, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages share a title

    https://www.cognizant.com/us/en/orphan/intuition-engineered/modernize-technology, https://www.cognizant.com/us/en/orphan/intuition-engineered/intelligent-processes and https://www.cognizant.com/us/en/orphan/intuition-engineered/experience-transformation all use the title “AI Builder for Enterprise | Cognizant”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.cognizant.com/us/en/orphan/intuition-engineered/modernize-technology, https://www.cognizant.com/us/en/orphan/intuition-engineered/intelligent-processes and https://www.cognizant.com/us/en/orphan/intuition-engineered/experience-transformation use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.cognizant.com/us/en/services/enterprise-physical-ai-autonomy, whose canonical is https://www.cognizant.com/us/en/services/ai/enterprise-physical-ai-autonomy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 8 pages without an H1

    https://www.cognizant.com/us/en/enterprise-ai-builder, https://www.cognizant.com/us/en/services/enterprise-physical-ai-autonomy, https://www.cognizant.com/us/en/case-studies/veidekke-accelerates-cloud-transformation-and-ai-adoption, https://www.cognizant.com/us/en/case-studies/kantar-transforms-its-digital-user-experiences-to-unlock-new-business-value, https://www.cognizant.com/us/en/case-studies/barry-callebaut-leads-the-way-in-cocoa-sustainability-and-compliance and https://www.cognizant.com/us/en/case-studies and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Every page has a meta description

    All 13 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 4 small tap targets

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

  • 1 JavaScript error while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 273 words of visible text.

1 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn more” and “Contact us”.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Hosting
Fastly

Company

Employees
266,200
Founded
1994
Headquarters
Teaneck

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on cognizant.com, including 3 speed issues, 3 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

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