Website review, no card needed

cpaglobal.com logo

cpaglobal.com website review

Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 60 checks

This review found 29 issues worth fixing on cpaglobal.com, 16 of them high impact, across 60 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
5.9 s4.2 sMay 16Oct 315.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.4 s
Jun 13, 20264.6 s
Jun 20, 20264.5 s
Jun 27, 20264.6 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20265.2 s
Jul 25, 20265.2 s
Aug 1, 20265.3 s
Aug 8, 20265.3 s
Aug 15, 20265.4 s
Aug 22, 20265.5 s
Aug 29, 20265.5 s
Sep 5, 20265.5 s
Sep 12, 20265.5 s
Sep 19, 20265.4 s
Sep 26, 20265.5 s
Oct 3, 20265.6 s
Oct 10, 20265.6 s
Oct 17, 20265.7 s
Oct 24, 20265.7 s
Oct 31, 20265.7 s
Real-visitor tap response (INP)75th percentile, phones
354 ms293 msMay 16Oct 31300 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026331 ms
May 23, 2026335 ms
May 30, 2026339 ms
Jun 6, 2026343 ms
Jun 13, 2026347 ms
Jun 20, 2026327 ms
Jun 27, 2026327 ms
Jul 4, 2026325 ms
Jul 11, 2026322 ms
Jul 18, 2026343 ms
Jul 25, 2026343 ms
Aug 1, 2026340 ms
Aug 8, 2026335 ms
Aug 15, 2026328 ms
Aug 22, 2026323 ms
Aug 29, 2026323 ms
Sep 5, 2026319 ms
Sep 12, 2026320 ms
Sep 19, 2026320 ms
Sep 26, 2026320 ms
Oct 3, 2026322 ms
Oct 10, 2026312 ms
Oct 17, 2026305 ms
Oct 24, 2026303 ms
Oct 31, 2026300 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 cpaglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cpaglobal.com at 1.0 s1.0 s
  2. cpaglobal.com at 2.0 s2.0 s
  3. cpaglobal.com at 3.0 s3.0 s
  4. cpaglobal.com at 4.0 s4.0 s
  5. cpaglobal.com at 5.0 s5.0 s
  6. cpaglobal.com at 5.9 s5.9 s
  7. cpaglobal.com at 6.9 s6.9 s
  8. cpaglobal.com at 7.9 s7.9 s

Speed

11 to fix30
  • Render-blocking requests

    2.5 s

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

  • Google Tag Manager adds 2.3 s

    2.3 s

    Google Tag Manager costs a phone 2.3 s of main-thread work and 1.7 MB 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.

  • Reduce unused CSS

    1.4 s · 157 KiB

    About 157 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 6.4 s

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

  • 3,882 HTML elements

    The page has 3,882 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, Optanon and gatedcontent.com and others), adding 2.6 MB and 2.5 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 1.1 MB

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

  • Use efficient cache lifetimes

    700 ms · 286 KiB

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

  • 20 long tasks on the main thread

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

  • Optanon adds 69 ms

    69 ms

    Optanon costs a phone 69 ms of main-thread work and 316 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.

  • Improve image delivery

    193 KiB

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

  • Legacy JavaScript

    150 ms · 24 KiB

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

  • Duplicated JavaScript

    50 ms · 18 KiB

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

  • Minify JavaScript

    15 KiB

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

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

    28 ms

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

Core Web Vitals

11 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: 5.7 s

    5.7 s

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

  • Real-user FCP: 5.3 s

    5.3 s

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

  • Real-user TTFB: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 11.0 s

    11.0 s

    Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (5.2 s).

  • Time to Interactive: 27.4 s

    27.4 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Real-user INP: 300 ms

    300 ms

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

  • Largest content (LCP) got 30% slower for real visitors

    +30%

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

  • Tap response (INP) held steady for real visitors

    -9%

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • Cumulative Layout Shift: 0.051

    0.051

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

Images and page weight

1 to fix0
  • Page weight: 6.9 MB in 126 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 126 requests on a phone: scripts 2.9 MB (47), media 2.4 MB (1) and images 565 KiB (30). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.96 g

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

Accessibility

2 to fix92
  • 2 tap targets too small

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

  • Links do not have a discernible name

    Links do not have a discernible name (1 element).

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 214 internal links, 60 external

    The homepage links to 214 pages on cpaglobal.com and 60 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Create, manage and protect your intellectual property with a range of IP solutions that can help transform your organiz…”.

  • One H1 headline

    Your main headline reads: “Think forward to an IP-powered tomorrow”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Intellectual Property Solutions - IP Solutions | Clarivate”.

  • Canonical URL set

    The canonical URL is https://clarivate.com/intellectual-property/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • 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.clarivate.com/sitemap_index.xml.

AI search readiness

2 to fix60
  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

  • No llms.txt

    There is no https://clarivate.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.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • 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 3,432 words of copy

    The homepage carries about 3,432 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact us”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

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 cpaglobal.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
Rackspace

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on cpaglobal.com, including 22 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