Website review, no card needed

weareavidity.com logo

weareavidity.com website review

Visit site (opens in a new tab)Reviewed 21 October 202621 issues · 68 checks

This review found 21 issues worth fixing on weareavidity.com, 5 of them high impact, across 68 checks. The most urgent: certain ARIA roles must be contained by particular parents (1 element). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor tap response (INP)75th percentile, phones
148 ms106 msMay 2Oct 17121 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026130 ms
May 9, 2026139 ms
May 16, 2026143 ms
May 23, 2026137 ms
May 30, 2026139 ms
Jun 6, 2026128 ms
Jun 13, 2026111 ms
Jun 20, 2026121 ms
Jun 27, 2026126 ms
Jul 4, 2026130 ms
Jul 18, 2026140 ms
Aug 8, 2026125 ms
Aug 22, 2026116 ms
Aug 29, 2026113 ms
Sep 12, 2026133 ms
Sep 19, 2026114 ms
Oct 3, 2026114 ms
Oct 10, 2026112 ms
Oct 17, 2026121 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

Full-page screenshot of weareavidity.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. weareavidity.com at 0.6 s0.6 s
  2. weareavidity.com at 1.2 s1.2 s
  3. weareavidity.com at 1.8 s1.8 s
  4. weareavidity.com at 2.4 s2.4 s
  5. weareavidity.com at 3.0 s3.0 s
  6. weareavidity.com at 3.6 s3.6 s
  7. weareavidity.com at 4.2 s4.2 s
  8. weareavidity.com at 4.8 s4.8 s

Speed

3 to fix
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and Civic and others), adding 1.2 MB and 381 ms of main-thread time.

  • Google Tag Manager adds 226 ms

    226 ms

    Google Tag Manager costs a phone 226 ms of main-thread work and 604 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.

  • Adobe TypeKit adds 0 ms

    0 ms

    Adobe TypeKit costs a phone 0 ms of main-thread work and 358 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.

  • Font display

    200 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

  • 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.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 534 ms of it running JavaScript. That is comfortably low.

  • Server response: 107 ms

    107 ms

    Your server sent the HTML in 107 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Speed Index: 8.6 s

    8.6 s

    Visually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 4.1 s

    4.1 s

    The first text or image appears after 4.1 s on a phone. Good is under 1.8 s.

  • 28 images without width and height

    28 images have no width and height attributes, so the layout jumps as each one loads.

5 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 CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Tap response (INP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 130 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 2.0 MB in 92 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 92 requests on a phone: scripts 1.1 MB (27), images 483 KiB (36) and fonts 432 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    12 KiB

    1 image is downloaded at several times the size a phone draws it, for example banner_mobile.png at 1,400 px wide, shown at 440 px. Resized copies would save about 12 KiB.

  • 2 images in older formats

    2 images (262 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 0.6 g of CO₂ per visit

    0.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 8895
  • Certain ARIA roles must be contained by particular parents (1 element)

    Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

  • 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9294
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 23 internal links, 7 external

    The homepage links to 23 pages on weareavidity.com and 7 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Avidity is the parent company of a group that offers a range of specialist sales and marketing services that help brand…”.

  • One H1 headline

    Your main headline reads: “We help brands sell more”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Avidity | Sales & Marketing Services”.

  • Canonical URL set

    The canonical URL is https://www.weareavidity.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.weareavidity.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.weareavidity.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 (430 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 7 pages without a meta description

    https://www.weareavidity.com/tactical, https://www.weareavidity.com/contact, https://www.weareavidity.com/modern-slavery-policy, https://www.weareavidity.com/corporate-social-responsibility, https://www.weareavidity.com/environmental-policy and https://www.weareavidity.com/privacy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.weareavidity.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    26 of 26 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • 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.

  • 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.

  • 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: 5 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 372 words of copy

    The homepage carries about 372 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • 21 other companies contacted

    Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 weareavidity.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on weareavidity.com, including 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25