Website review, no card needed

abpartners.co logo

abpartners.co website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 67 checks

This review found 26 issues worth fixing on abpartners.co, 6 of them high impact, across 67 checks. The most urgent: page weight: 34.6 MB in 33 requests. 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 abpartners.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix76
  • Use efficient cache lifetimes

    20.2 MB

    7 files are served with short cache lifetimes, so returning visitors download them again (20.2 MB).

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, flodesk.com and Google Analytics and others), adding 32.9 MB and 348 ms of main-thread time.

  • onrender.com adds 0 ms

    0 ms

    onrender.com costs a phone 0 ms of main-thread work and 32.4 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.

  • Reduce unused JavaScript

    960 ms · 414 KiB

    About 414 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 960 ms faster on a phone.

  • Mobile performance score: 76

    76/100

    Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 324 ms

    324 ms

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

    150 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • 6 long tasks on the main thread

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

  • Improve image delivery

    100 KiB

    1 image could be 100 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • Reduce unused CSS

    43 KiB

    About 43 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

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

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

  • Server response: 19 ms

    19 ms

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

Core Web Vitals

4 to fix86
  • Speed Index: 7.0 s

    7.0 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Time to Interactive: 8.9 s

    8.9 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A—B is now”. Most of its time is element render delay (2.4 s).

  • 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: 142 ms

    142 ms

    Scripts block the page for only 142 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 34.6 MB in 33 requests

    34.6 MB

    Your homepage downloads 34.6 MB in 33 requests on a phone: media 33.2 MB (6), scripts 939 KiB (14) and images 272 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (272 KiB) is 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 9.8 g of CO₂ per visit

    9.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.81 g of CO₂e: 1177.1 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

2 to fixGoogle 9296
  • Positive tabindex

    4 elements have a tabindex above 0, which scrambles the keyboard order.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • No structured data

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

  • 9 H1 headlines

    There are 9 <h1> headlines (“Speak yourmind.”, “A—B is nowNewWorld” and “The agency forIdentity-Powered Design™”). One clear main headline is easier for people and search engines.

  • Meta description is long (467 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.abpartners.co/sitemap.xml, so Google discovers your pages only by following links.

  • 16 internal links, 8 external

    The homepage links to 16 pages on abpartners.co and 8 external pages.

4 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “A—B is now NewWorld | A—B — Identity-Powered Design™ Agency”.

  • Canonical URL set

    The canonical URL is https://abpartners.co/.

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

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.abpartners.co/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 (281 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.abpartners.co/connect, whose canonical is https://www.abpartners.co/[...slug]. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.abpartners.co/privacy-terms and https://www.abpartners.co/method have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • 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 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

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

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

  • Only about 193 words

    The homepage has only about 193 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Talk to us”.

  • 2 calls to action

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 abpartners.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Analytics
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on abpartners.co, including 10 speed issues, 4 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