Website review, no card needed
cerulli.com website review
Visit site (opens in a new tab)Reviewed 20 October 202636 issues · 91 checks
This review found 36 issues worth fixing on cerulli.com, 14 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 110 ms |
| May 9, 2026 | 112 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 100 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 88 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 98 ms |
| Aug 29, 2026 | 100 ms |
| Sep 5, 2026 | 102 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 83 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 104 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Render-blocking requests
1.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 46
46/100Your mobile performance score is 46 (desktop: 81). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
950 ms · 1.1 MB41 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Reduce unused JavaScript
600 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Vimeo, userpilot.io and Google CDN and others), adding 10.2 MB and 681 ms of main-thread time.
Vimeo adds 172 ms
172 msVimeo costs a phone 172 ms of main-thread work and 9.1 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
userpilot.io adds 172 ms
172 msuserpilot.io costs a phone 172 ms of main-thread work and 415 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 138 ms
138 msGoogle CDN costs a phone 138 ms of main-thread work and 347 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
248 KiB4 images could be 248 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 217 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 81 but mobile only 46. 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 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 22.2 s
22.2 sThe page becomes fully interactive after 22.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 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 improve your site experience, distinguish…”.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 723 ms
723 msScripts block taps and scrolling for 723 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user TTFB: 986 ms
986 msReal visitors wait 986 ms for your server to start answering (75th percentile). Good is under 800 ms.
13 images without width and height
13 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 110 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.055
0.055The layout barely moves while loading (CLS 0.055, good is under 0.1).
Images and page weight
Page weight: 11.5 MB in 115 requests
11.5 MBYour homepage downloads 11.5 MB in 115 requests on a phone: other files 8.2 MB (46), scripts 2.3 MB (31) and images 691 KiB (22). Under 2 MB keeps phones on slow connections fast.
7 images below the first screen load straight away
7 images further down the page (361 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (248 KiB) are 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 3.3 g of CO₂ per visit
3.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.26 g of CO₂e: 391.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
38 text elements with low contrast
38 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Asset and Wealth Management Research, Data, and… | Cerulli Associates”.
6 H1 headlines
There are 6 <h1> headlines (“Cerulli Associates”, “Research, Analytics, Consulting” and “Cerulli Associates”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, LocalBusiness and Organization) but with 1 problem, for example “Organization: missing name”.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
71 internal links, 2 external
The homepage links to 71 pages on cerulli.com and 2 external pages.
5 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Gain market intelligence and strategic business recommendations with Cerulli's research, data, and consulting services”.
Canonical URL set
The canonical URL is https://www.cerulli.com/.
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.cerulli.com/sitemaps-1-sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.cerulli.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.
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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: 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 (680 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
7 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.
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
2 small tap targets
2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 615 words of copy
The homepage carries about 615 words of visible text.
6 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Pricing and Profitability”, “Contact Us” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 2 of them by other companies (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.
27 other companies contacted
Loading the homepage contacts 27 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 cerulli.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
- SEOmatic
- Framework
- Tailwind CSS
- 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 36 issues on cerulli.com, including 17 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.