Website review, no card needed

a-g.com logo

a-g.com website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 85 checks

This review found 43 issues worth fixing on a-g.com, 16 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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

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

How it loaded on a phone

  1. a-g.com at 0.8 s0.8 s
  2. a-g.com at 1.6 s1.6 s
  3. a-g.com at 2.3 s2.3 s
  4. a-g.com at 3.1 s3.1 s
  5. a-g.com at 3.9 s3.9 s
  6. a-g.com at 4.7 s4.7 s
  7. a-g.com at 5.4 s5.4 s
  8. a-g.com at 6.2 s6.2 s

Speed

11 to fix46
  • Reduce unused JavaScript

    10.0 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.0 s faster on a phone.

  • Render-blocking requests

    3.8 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.

  • Use efficient cache lifetimes

    1.8 s · 409 KiB

    27 files are served with short cache lifetimes, so returning visitors download them again (409 KiB).

  • Reduce unused CSS

    1.4 s · 155 KiB

    About 155 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and Amazon Web Services and others), adding 15.1 MB and 846 ms of main-thread time.

  • Vimeo adds 331 ms

    331 ms

    Vimeo costs a phone 331 ms of main-thread work and 14.3 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.

  • Improve image delivery

    1.1 MB

    9 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    750 ms · 113 KiB

    113 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 366 ms

    366 ms

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

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 238 ms. During a long task the page ignores taps.

  • Minify CSS

    150 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix57
  • First Contentful Paint: 13.9 s

    13.9 s

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

  • Largest Contentful Paint: 26.0 s

    26.0 s

    Your largest element takes 26.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At A&G, we drive dramatic growth by igniting dramatic shift…”.

  • Time to Interactive: 29.5 s

    29.5 s

    The page becomes fully interactive after 29.5 s. Good is under 3.8 s.

  • Speed Index: 13.9 s

    13.9 s

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

  • Total Blocking Time: 373 ms

    373 ms

    Scripts block taps and scrolling for 373 ms in total while the page loads. Good is under 200 ms.

  • 8 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix28
  • Page weight: 17.3 MB in 166 requests

    17.3 MB

    Your homepage downloads 17.3 MB in 166 requests on a phone: other files 12.4 MB (46), scripts 2.9 MB (59) and images 1.4 MB (26). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Meet-Boston-Scotland-TheCrown-2000186706-POP-9-1.jpg weighs 594 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (958 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.

  • 4 images below the first screen load straight away

    4 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    467 KiB

    2 images are downloaded at several times the size a phone draws them, for example Meet-Boston-Scotland-TheCrown-2000186706-POP-9-1.jpg at 2,289 px wide, shown at 358 px. Resized copies would save about 467 KiB.

  • About 4.9 g of CO₂ per visit

    4.90 g

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

Accessibility

4 to fixGoogle 8894
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Frames without titles

    4 frames have no title, so screen-reader users cannot tell what they contain.

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8581
  • Title is short (24 characters)

    Your title is only 24 characters: “Home | Allen & Gerritsen”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 27 internal links, 12 external

    The homepage links to 27 pages on a-g.com and 12 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “We Make Brands Unignorable”.

  • Canonical URL set

    The canonical URL is https://www.a-g.com/.

  • Structured data in place

    Structured data found: Article, Organization, WebPage and WebSite.

  • 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.a-g.com/sitemap_index.xml.

AI search readiness

100
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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (361 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.a-g.com/llms.txt (11 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 2 pages without a meta description

    https://www.a-g.com/careers and https://www.a-g.com/third-space-studios have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.a-g.com/news/ag-life-share-index and https://www.a-g.com/news/marketing-to-the-ageless-generation-shift-from-old-to-ageless use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://www.a-g.com/our-work, https://www.a-g.com/news, https://www.a-g.com/contact, https://www.a-g.com/news/allen-gerritsen-helps-boston-logan-find-a-new-voice-of-logan, https://www.a-g.com/news/allen-gerritsen-and-giant-shift-price-perception and https://www.a-g.com/news/ag-puts-dunkin-on-the-literal-map and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.a-g.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 (of 16 found) and read each the way a search engine does.

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

  • 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

5 to fixGoogle 5081
  • 8 small tap targets

    8 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Error: <feTurbulence> attribute baseFrequency: Expected number, "-\u003E13".”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

    The homepage carries about 300 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “contact” and “Allen & Gerritsen's contact page”.

  • 1 short form

    A short form (4 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: 2 phone links and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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

    6

    Opening the homepage sets 6 cookies, 2 of them by other companies (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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 a-g.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 Tag Manager

Hiring

Hiring
3 open roles
Teams
Engineering (1), Finance (1), Sales (1)
Job board
greenhouse

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on a-g.com, including 17 speed issues, 5 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

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