Website review, no card needed
anthemiq.com website review
Visit site (opens in a new tab)Reviewed 23 October 202634 issues · 75 checks
This review found 34 issues worth fixing on anthemiq.com, 8 of them high impact, across 75 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.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
8.1 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.
Render-blocking requests
2.6 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
8 third-party services on the page
8 third-party services load with your homepage (Squarespace, Google CDN and Intercom and others), adding 2.8 MB and 1.1 s of main-thread time.
Reduce unused CSS
910 ms · 161 KiBAbout 161 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.
Improve image delivery
150 ms · 873 KiB10 images could be 873 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.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 68). Pages that score under 90 lose visitors before the first paint.
Squarespace adds 495 ms
495 msSquarespace costs a phone 495 ms of main-thread work and 1.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.
Legacy JavaScript
300 ms · 157 KiBPolyfills for old browsers add 157 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 302 ms
302 msGoogle CDN costs a phone 302 ms of main-thread work and 772 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.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 261 ms. During a long task the page ignores taps.
sqspcdn.com adds 66 ms
66 mssqspcdn.com costs a phone 66 ms of main-thread work and 500 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.
Minify JavaScript
40 KiB40 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
9 KiB6 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
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: 76 ms
76 msYour server sent the HTML in 76 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 15.1 s
15.1 sThe first text or image appears after 15.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.4 s
26.4 sYour largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.7 s
26.7 sThe page becomes fully interactive after 26.7 s. Good is under 3.8 s.
Speed Index: 15.1 s
15.1 sVisually, the page fills in at 15.1 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images 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
Total Blocking Time: 85 ms
85 msScripts block the page for only 85 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 134 requests
4.9 MBYour homepage downloads 4.9 MB in 134 requests on a phone: scripts 2.5 MB (84), images 1.5 MB (16) and other files 475 KiB (6). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (539 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
112 KiB1 image is downloaded at several times the size a phone draws it, for example Best+Project+Deal+Management+CRE+App-2.png at 1,500 px wide, shown at 343 px. Resized copies would save about 112 KiB.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 166.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
47 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: 47 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Site selection decisions, faster.”, ““A valuable must-have in any tech stack…” and “Deals, Tasks & Data Designed For The Way You Work.”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/60870639f318143cc6c…”.
81 internal links, 6 external
The homepage links to 81 pages on anthemiq.com and 6 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Commercial Real Estate Deal & Project Management App for Tenant Rep Brokers. A Collaborative Approach to Client Relatio…”.
Title: 63 characters
Your title is a healthy 63 characters: “AnthemIQ - The Best Commercial Real Estate Transaction Platform”.
Canonical URL set
The canonical URL is https://www.anthemiq.com/.
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.anthemiq.com/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.anthemiq.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 (679 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.anthemiq.com/transactiq-occupiers and https://www.anthemiq.com/Products all use the title “Commercial Real Estate Site Selection & Portfolio Management App — An…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.anthemiq.com/deal-management and https://www.anthemiq.com/plans-pricing have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.anthemiq.com/transactiq-occupiers and https://www.anthemiq.com/Products use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.anthemiq.com/Products, whose canonical is https://www.anthemiq.com/transactiq-occupiers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.anthemiq.com/transactiq-occupiers and https://www.anthemiq.com/Products 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 31 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'click')”.
2 checks passed
Tap targets are thumb-sized
8 of 8 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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 550 words of copy
The homepage carries about 550 words of visible text.
6 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Pricing”, “Start Free Trial” and “Try Now”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
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.
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 anthemiq.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- Squarespace
- Framework
- jQuery
- 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 34 issues on anthemiq.com, including 17 speed issues, 2 SEO issues 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.