Website review, no card needed
cranemere.com website review
Visit site (opens in a new tab)Reviewed 21 October 202618 issues · 65 checks
This review found 18 issues worth fixing on cranemere.com, 6 of them high impact, across 65 checks. The most urgent: use efficient cache lifetimes. 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
81BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Use efficient cache lifetimes
1.4 s · 111 KiB9 files are served with short cache lifetimes, so returning visitors download them again (111 KiB).
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused CSS
300 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 272 ms
272 msGoogle Tag Manager costs a phone 272 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.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, termly.io and userway.org and others), adding 589 KiB and 423 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 693 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Building for the long-term”. Most of its time is resource load delay (2.7 s).
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
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.
Time to Interactive: 7.1 s
7.1 sThe page becomes fully interactive after 7.1 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.076
0.076The layout barely moves while loading (CLS 0.076, good is under 0.1).
Total Blocking Time: 143 ms
143 msScripts block the page for only 143 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
birds-quality-750x750.jpg 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.3 g of CO₂ per visit
0.31 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 37.2 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: 1.1 MB in 49 requests
1.1 MBYour homepage downloads 1.1 MB in 49 requests on a phone: scripts 659 KiB (17), fonts 266 KiB (6) and images 120 KiB (12). 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
Headings skip levels
Headings skip levels (h2 → h4), 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.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
2 H1 headlines
There are 2 <h1> headlines (“The Cranemere Group” and “Building for the long-term”). One clear main headline is easier for people and search engines.
41 internal links, 4 external
The homepage links to 41 pages on cranemere.com and 4 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Partner with Cranemere, a premier holding company with private capital, for sustained long-term growth, for founders an…”.
Title: 60 characters
Your title is a healthy 60 characters: “Cranemere | Private Capital for Founders & Family Businesses”.
Canonical URL set
The canonical URL is https://www.cranemere.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.cranemere.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.cranemere.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.
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: 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 (434 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without an H1
https://www.cranemere.com/contact, https://www.cranemere.com/cranemere-is-long-term-values-aligned-partner, https://www.cranemere.com/creating-long-term-shareholder-value, https://www.cranemere.com/team-of-dedicated-professionals, https://www.cranemere.com/cranemere-partner-operating-companies and https://www.cranemere.com/cranemere-partner-operating-companies/exemplis and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
6 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.
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 small tap targets
5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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: 12 testimonial or review blocks. 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 440 words of copy
The homepage carries about 440 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact” and “Newsletter Signup”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies, 1 of them by other companies (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: Termly
A consent management tool (Termly) 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 cranemere.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 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 18 issues on cranemere.com, including 11 speed issues, 1 SEO issue and 3 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.