Website review, no card needed
clarionpartners.com website review
Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 83 checks
This review found 26 issues worth fixing on clarionpartners.com, 6 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 79 ms |
| May 16, 2026 | 85 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 78 ms |
| Jun 20, 2026 | 77 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 72 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 83 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 83 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 83 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 93 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 85 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 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.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Reduce unused JavaScript
1.6 s · 264 KiBAbout 264 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.8 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 62
62/100Your mobile performance score is 62 (desktop: 89). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 121 KiB7 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
Reduce unused CSS
600 ms · 62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Legacy JavaScript
300 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 258 ms
258 msGoogle Tag Manager costs a phone 258 ms of main-thread work and 293 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Optanon and bc0a.com and others), adding 567 KiB and 384 ms of main-thread time.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 211 ms. During a long task the page ignores taps.
Improve image delivery
150 ms · 53 KiB4 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify CSS
16 KiB16 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 89 but mobile only 62. 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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 580 ms of it running JavaScript. That is comfortably low.
Server response: 57 ms
57 msYour server sent the HTML in 57 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.
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We don't merely acquire value. We create it.”.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.4 s
11.4 sThe page becomes fully interactive after 11.4 s. Good is under 3.8 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 78 ms
78 msReal visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 793 ms
793 msReal visitors wait 793 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 141 ms
141 msScripts block the page for only 141 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 54 requests
1.6 MBYour homepage downloads 1.6 MB in 54 requests on a phone: scripts 659 KiB (19), images 398 KiB (10) and fonts 343 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 links without text
2 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 → h5, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (170 characters)
Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
44 internal links, 6 external
The homepage links to 44 pages on clarionpartners.com and 6 external pages.
6 checks passed
One H1 headline
Your main headline reads: “We don't merely acquire value. We create it.”.
Title: 46 characters
Your title is a healthy 46 characters: “Real Estate Investment Firm | Clarion Partners”.
Canonical URL set
The canonical URL is https://www.clarionpartners.com/.
Structured data in place
Structured data found: WebPage.
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.clarionpartners.com:443/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.clarionpartners.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,037 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 27 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
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 “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 832 words of copy
The homepage carries about 832 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 about us”.
7 calls to action
The homepage has 7 calls to action, for example “Contact us”, “Learn more about us” and “Learn more about careers”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 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 clarionpartners.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Navisite East
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on clarionpartners.com, including 14 speed issues, 2 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.