Website review, no card needed
addison-group.com website review
Visit site (opens in a new tab)Reviewed 2 November 202630 issues · 72 checks
This review found 30 issues worth fixing on addison-group.com, 11 of them high impact, across 72 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
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Reduce unused JavaScript
2.6 s · 460 KiBAbout 460 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
1.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5 third-party services on the page
5 third-party services load with your homepage (Squarespace, velt.dev and sqspcdn.com and others), adding 2.2 MB and 952 ms of main-thread time.
Reduce unused CSS
910 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 910 ms faster on a phone.
Squarespace adds 792 ms
792 msSquarespace costs a phone 792 ms of main-thread work and 1,015 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
450 ms · 176 KiB6 images could be 176 KiB 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.
Use efficient cache lifetimes
350 ms · 41 KiB3 files are served with short cache lifetimes, so returning visitors download them again (41 KiB).
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 356 ms. During a long task the page ignores taps.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 911 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 927 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.
Legacy JavaScript
150 ms · 95 KiBPolyfills for old browsers add 95 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 39 ms
39 msYour server sent the HTML in 39 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Outdoor spaces designed around the way you live”.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 562 ms
562 msScripts block taps and scrolling for 562 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.3 MB in 80 requests
2.3 MBYour homepage downloads 2.3 MB in 80 requests on a phone: scripts 1.1 MB (43), images 689 KiB (9) and fonts 238 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (164 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.0 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6a3be9089b9dfc1ad1b…”.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
25 internal links, 13 external
The homepage links to 25 pages on addison-group.com and 13 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Outdoor spaces designed around the way you live”.
Title: 39 characters
Your title is a healthy 39 characters: “The Addison Group | Landscape Architect”.
Canonical URL set
The canonical URL is https://www.addison-group.com/.
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.addison-group.com/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.addison-group.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 (833 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.addison-group.com/services, https://www.addison-group.com/portfolio, https://www.addison-group.com/articles, https://www.addison-group.com/about, https://www.addison-group.com/discuss-your-project and https://www.addison-group.com/faqs have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.addison-group.com/faqs has no <h1> headline, so visitors and search engines get no clear main topic.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 6 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6a3be9089b9dfc1ad1bf5f5d/66/5c5a…”.
2 checks passed
Tap targets are thumb-sized
5 of 5 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 805 words of copy
The homepage carries about 805 words of visible text.
1 checks passed
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 addison-group.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
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on addison-group.com, including 17 speed issues, 2 SEO issues and 5 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.