Website review, no card needed

persistent.com logo

persistent.com website review

Visit site (opens in a new tab)Reviewed 14 November 202648 issues · 93 checks

This review found 48 issues worth fixing on persistent.com, 24 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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.9 s4.0 sMay 23Nov 74.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20265.0 s
May 30, 20265.1 s
Jun 6, 20265.1 s
Jun 13, 20265.4 s
Jun 20, 20265.5 s
Jun 27, 20265.2 s
Jul 4, 20264.9 s
Jul 11, 20264.8 s
Jul 18, 20264.9 s
Jul 25, 20265.4 s
Aug 1, 20265.7 s
Aug 8, 20265.5 s
Aug 15, 20265.3 s
Aug 22, 20264.9 s
Aug 29, 20264.8 s
Sep 5, 20264.8 s
Sep 12, 20264.7 s
Sep 19, 20264.9 s
Sep 26, 20264.9 s
Oct 3, 20264.9 s
Oct 10, 20264.8 s
Oct 17, 20264.6 s
Oct 24, 20264.4 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
292 ms207 msMay 23Nov 7282 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026235 ms
May 30, 2026237 ms
Jun 6, 2026236 ms
Jun 13, 2026239 ms
Jun 20, 2026238 ms
Jun 27, 2026227 ms
Jul 4, 2026218 ms
Jul 11, 2026218 ms
Jul 18, 2026217 ms
Jul 25, 2026224 ms
Aug 1, 2026233 ms
Aug 8, 2026238 ms
Aug 15, 2026244 ms
Aug 22, 2026254 ms
Aug 29, 2026256 ms
Sep 5, 2026258 ms
Sep 12, 2026261 ms
Sep 19, 2026262 ms
Sep 26, 2026266 ms
Oct 3, 2026269 ms
Oct 10, 2026272 ms
Oct 17, 2026273 ms
Oct 24, 2026279 ms
Oct 31, 2026279 ms
Nov 7, 2026282 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 persistent.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. persistent.com at 1.0 s1.0 s
  2. persistent.com at 1.9 s1.9 s
  3. persistent.com at 2.9 s2.9 s
  4. persistent.com at 3.9 s3.9 s
  5. persistent.com at 4.8 s4.8 s
  6. persistent.com at 5.8 s5.8 s
  7. persistent.com at 6.8 s6.8 s
  8. persistent.com at 7.8 s7.8 s

Speed

16 to fix26
  • Reduce unused JavaScript

    9.3 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.

  • Use efficient cache lifetimes

    4.5 s · 795 KiB

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

  • Render-blocking requests

    5.0 s

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

  • Improve image delivery

    2.6 s · 334 KiB

    1 image could be 334 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Google Tag Manager adds 1.5 s

    1.5 s

    Google Tag Manager costs a phone 1.5 s of main-thread work and 891 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 10.1 s

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

  • Mobile performance score: 26

    26/100

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

  • 3,002 HTML elements

    The page has 3,002 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 (Google Tag Manager, Google CDN and Facebook and others), adding 5.5 MB and 3.3 s of main-thread time.

  • Reduce unused CSS

    900 ms · 165 KiB

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

  • Legacy JavaScript

    650 ms · 85 KiB

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

  • Vimeo adds 251 ms

    251 ms

    Vimeo costs a phone 251 ms of main-thread work and 3.4 MB 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 515 ms

    515 ms

    Google CDN costs a phone 515 ms of main-thread work and 742 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 468 ms. During a long task the page ignores taps.

  • Facebook adds 361 ms

    361 ms

    Facebook costs a phone 361 ms of main-thread work and 221 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.

  • cookiepro.com adds 286 ms

    286 ms

    cookiepro.com costs a phone 286 ms of main-thread work and 200 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.

  • 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: 44 ms

    44 ms

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

Core Web Vitals

10 to fix33
  • 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.7 s

    4.7 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Largest Contentful Paint: 33.0 s

    33.0 s

    Your largest element takes 33.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enable website functionality, understand …”.

  • Time to Interactive: 35.3 s

    35.3 s

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

  • Speed Index: 14.7 s

    14.7 s

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

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Total Blocking Time: 2.8 s

    2.8 s

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

  • Real-user INP: 310 ms

    310 ms

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

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

    +19%

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

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

    -15%

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

  • Cumulative Layout Shift: 0.045

    0.045

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

Images and page weight

1 to fix70
  • Page weight: 8.6 MB in 187 requests

    8.6 MB

    Your homepage downloads 8.6 MB in 187 requests on a phone: scripts 3.8 MB (70), other files 3.5 MB (66) and images 464 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (350 KiB) is 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.

  • About 2.4 g of CO₂ per visit

    2.42 g

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

2 checks passed
  • 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

9 to fixGoogle 9089
  • autocomplete attribute must be used correctly (7 elements)

    autocomplete attribute must be used correctly: 7 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 128 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Re(AI)magining the World: AI & Digital Engineering with Persistent”.

  • 3 links crawlers can't follow

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

  • 2 links with vague text

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

  • 371 internal links, 43 external

    The homepage links to 371 pages on persistent.com and 43 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Re(AI)magining the World with Persistent Systems: Transform your AI journey with a trusted partner in digital engineeri…”.

  • One H1 headline

    Your main headline reads: “Persistent Announces$487.6M Revenue in Q2 FY27 with 20.0% Y-o-Y Growth”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.persistent.com/sitemap_index.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix88
  • 14 pages share a title

    https://www.persistent.com/services, https://www.persistent.com/services/agentic-business-automation, https://www.persistent.com/services/application-development-and-management, https://www.persistent.com/services/cloud-and-infrastructure, https://www.persistent.com/services/consulting and https://www.persistent.com/services/cx-transformation and 8 others all use the title “Radware Captcha Page”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.persistent.com/services, https://www.persistent.com/services/agentic-business-automation, https://www.persistent.com/services/application-development-and-management, https://www.persistent.com/services/cloud-and-infrastructure, https://www.persistent.com/services/consulting and https://www.persistent.com/services/cx-transformation and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages with very little text

    https://www.persistent.com/services, https://www.persistent.com/services/agentic-business-automation, https://www.persistent.com/services/application-development-and-management, https://www.persistent.com/services/cloud-and-infrastructure, https://www.persistent.com/services/consulting and https://www.persistent.com/services/cx-transformation and 8 others 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 193 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

5 to fixGoogle 5469
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187234354&tm=gtm002&Ver=2&mid=5027deeb-4a53-47d2-9ae4-a665c69a26cf&bo=1&sid=ec5d2320e05911f195a1eb41cdcfc5f7&vid=ec5d59a0e05911f1bddebbb1c1b7d424&vids=1&msclkid=N&pi=9.

  • 6 small tap targets

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1542067334.1794681221&gtm=45He6bb1v76766501za200zd76766501…”.

  • 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 fix83
  • Thin social proof

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

  • A 12-field form

    Your longest form asks for 12 fields (6 required). Every extra field lowers completion.

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “CX Contact Center Intelligence”, “CX Contact Center Intellegence” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

  • Direct contact links

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

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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.

  • 41 cookies set on arrival

    41

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 persistent.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
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Radware Cloud Services Radware Inc.

Company

Founded
1990
Headquarters
Pune

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on persistent.com, including 26 speed issues, 3 SEO issues 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