Website review, no card needed
addisongroup.com website review
Visit site (opens in a new tab)Reviewed 28 October 202635 issues · 87 checks
This review found 35 issues worth fixing on addisongroup.com, 13 of them high impact, across 87 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.2 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.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 87 ms |
| May 16, 2026 | 88 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 89 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 120 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
4.3 s · 904 KiBAbout 904 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 1.4 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (sensehq.com, Google CDN and Google Tag Manager and others), adding 3.2 MB and 1.3 s of main-thread time.
sensehq.com adds 643 ms
643 mssensehq.com costs a phone 643 ms of main-thread work and 2.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.
Google CDN adds 421 ms
421 msGoogle CDN costs a phone 421 ms of main-thread work and 736 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.
Render-blocking requests
450 ms23 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
304 KiB10 images could be 304 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 96 ms
96 msGoogle Tag Manager costs a phone 96 ms of main-thread work and 325 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 190 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
23 KiB23 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 43. 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.
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: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 15.2 s
15.2 sYour largest element takes 15.2 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 enhance your browsing experience, serve p…”.
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 87 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 74% slower for real visitors
+74%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.2 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 428 ms
428 msScripts block taps and scrolling for 428 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.107
0.107The layout shifts by 0.107 while loading, so content jumps under the reader's thumb. Good is under 0.1.
6 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 90 ms
90 msReal visitors wait 90 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (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: 726 ms
726 msReal visitors wait 726 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.4 MB in 130 requests
4.4 MBYour homepage downloads 4.4 MB in 130 requests on a phone: scripts 2.2 MB (33), fonts 898 KiB (7) and images 476 KiB (29). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (385 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 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
9 text elements with low contrast
9 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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Orphan list items
Some list items are not inside a list.
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.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
16 links with vague text
16 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
77 internal links, 13 external
The homepage links to 77 pages on addisongroup.com and 13 external pages.
8 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Get insights on effective staffing approaches to ensure your organization achieves its goals and objectives with Addiso…”.
One H1 headline
Your main headline reads: “Addison Group is the talent solutions expert”.
Title: 64 characters
Your title is a healthy 64 characters: “Addison Group | Staffing, Talent Solutions & Consulting Services”.
Canonical URL set
The canonical URL is https://addisongroup.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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://addisongroup.com/sitemap_index.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (997 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://addisongroup.com/llms.txt (11 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://addisongroup.com/who-we-are/leadership-type/addison-group-executive-leadership is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
10 pages without a meta description
https://addisongroup.com/practice-areas, https://addisongroup.com/practice-areas/information-technology, https://addisongroup.com/practice-areas/human-resources, https://addisongroup.com/practice-areas/healthcare, https://addisongroup.com/practice-areas/administrative and https://addisongroup.com/practice-areas/digital-marketing and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://addisongroup.com/locations has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://addisongroup.com/practice-areas/administrative and https://addisongroup.com/locations took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
38 of 42 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: 8 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 883 words of copy
The homepage carries about 883 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”.
18 calls to action
The homepage has 18 calls to action, for example “Contact”, “Learn more” and “Get Your Guide”.
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, HubSpot and LinkedIn Insight.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (CookieYes) 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 (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 addisongroup.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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on addisongroup.com, including 18 speed issues, 1 SEO issue 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.