Website review, no card needed
campbelltickell.com website review
Visit site (opens in a new tab)Reviewed 22 October 202629 issues · 89 checks
This review found 29 issues worth fixing on campbelltickell.com, 12 of them high impact, across 89 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
82B- #32,391 of 114,072 reviewed websitesbeats 66%
- #21,926 of 65,933 online storesbeats 60%
- #384 of 2,592 WooCommerce storesbeats 81%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 83 ms |
| May 9, 2026 | 81 ms |
| May 16, 2026 | 78 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 71 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 84 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 85 ms |
| Sep 12, 2026 | 81 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 93 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 87 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.6 s
3.0 s
Speed
Reduce unused JavaScript
5.1 s · 578 KiBAbout 578 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Render-blocking requests
5.4 s60 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.4 s.
Reduce unused CSS
1.8 s · 357 KiBAbout 357 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Improve image delivery
450 ms · 1.2 MB5 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 73). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Hubspot and others), adding 1.4 MB and 580 ms of main-thread time.
Use efficient cache lifetimes
450 ms · 101 KiB6 files are served with short cache lifetimes, so returning visitors download them again (101 KiB).
Google CDN adds 290 ms
290 msGoogle CDN costs a phone 290 ms of main-thread work and 733 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
280 ms · 36 KiB36 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 15 KiB15 KiB could be saved by minifying CSS.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.2 s
12.2 sThe first text or image appears after 12.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 30.7 s
30.7 sYour largest element takes 30.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 31.7 s
31.7 sThe page becomes fully interactive after 31.7 s. Good is under 3.8 s.
Speed Index: 12.2 s
12.2 sVisually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 83 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 781 ms
781 msReal visitors wait 781 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.09
0.09The layout barely moves while loading (CLS 0.09, good is under 0.1).
Total Blocking Time: 53 ms
53 msScripts block the page for only 53 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.6 MB in 194 requests
7.6 MBYour homepage downloads 7.6 MB in 194 requests on a phone: images 4.8 MB (45), scripts 1.5 MB (84) and stylesheets 473 KiB (51). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
2 images below the first screen load straight away
2 images further down the page (64 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.15 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.15 g of CO₂e: 258.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (37 elements)
All page content should be contained by landmarks: 37 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
100 internal links, 19 external
The homepage links to 100 pages on campbelltickell.com and 19 external pages.
7 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “We are a management & recruitment consultancy providing high quality services and advice to not-for-profit, housing & p…”.
Title: 44 characters
Your title is a healthy 44 characters: “Campbell Tickell | Consultancy & Recruitment”.
Canonical URL set
The canonical URL is https://www.campbelltickell.com/.
Structured data in place
Structured data found: BreadcrumbList, Event, ImageObject, Organization and WebPage.
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.campbelltickell.com/sitemap_index.xml.
AI search readiness
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,070 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.campbelltickell.com/llms.txt (5 KiB, 15 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.campbelltickell.com/jobs-recruitment, https://www.campbelltickell.com/jobs-recruitment/live-jobs and https://www.campbelltickell.com/jobs-recruitment/non-executive have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.campbelltickell.com/our-sectors took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.campbelltickell.com/wp-content/uploads/2024/08/LW-Logo.png.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.
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
14 of 17 tappable elements near the top are at least 24 px.
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.
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 767 words of copy
The homepage carries about 767 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Sign up for CT Updates” and “Learn more about us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 5 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Google Analytics, Hotjar and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (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.
18 other companies contacted
Loading the homepage contacts 18 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 campbelltickell.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Hotjar
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 campbelltickell.com, including 14 speed issues, 2 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.