Website review, no card needed

boyerassoc.com logo

boyerassoc.com website review

Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 83 checks

This review found 43 issues worth fixing on boyerassoc.com, 20 of them high impact, across 83 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 boyerassoc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boyerassoc.com at 1.0 s1.0 s
  2. boyerassoc.com at 2.0 s2.0 s
  3. boyerassoc.com at 3.1 s3.1 s
  4. boyerassoc.com at 4.1 s4.1 s
  5. boyerassoc.com at 5.1 s5.1 s
  6. boyerassoc.com at 6.1 s6.1 s
  7. boyerassoc.com at 7.2 s7.2 s
  8. boyerassoc.com at 8.2 s8.2 s

Speed

14 to fix28
  • Reduce unused JavaScript

    30.9 s · 3.9 MB

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

  • Use efficient cache lifetimes

    6.8 s · 11.7 MB

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

  • Reduce unused CSS

    13.3 s · 1.4 MB

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

  • Improve image delivery

    3.5 s · 8.3 MB

    15 images could be 8.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

  • Render-blocking requests

    7.7 s

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

  • Calendly adds 1.4 s

    1.4 s

    Calendly costs a phone 1.4 s of main-thread work and 5.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 9.0 s

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

  • 3,829 HTML elements

    The page has 3,829 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Calendly, Google CDN and Google Tag Manager and others), adding 9.5 MB and 3.0 s of main-thread time.

  • Google CDN adds 832 ms

    832 ms

    Google CDN costs a phone 832 ms of main-thread work and 2.6 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.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 361 ms

    361 ms

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

  • Stripe adds 271 ms

    271 ms

    Stripe costs a phone 271 ms of main-thread work and 577 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

    50 ms

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    7 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

    17 ms

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

Core Web Vitals

6 to fix36
  • First Contentful Paint: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 74.3 s

    74.3 s

    Your largest element takes 74.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 22.0 s

    22.0 s

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

  • Time to Interactive: 81.1 s

    81.1 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • 2 images without width and height

    2 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 fix18
  • Page weight: 23.6 MB in 348 requests

    23.6 MB

    Your homepage downloads 23.6 MB in 348 requests on a phone: images 10.9 MB (45), scripts 7.4 MB (140) and stylesheets 3.1 MB (99). Under 2 MB keeps phones on slow connections fast.

  • 7 images over 500 KB

    7 images weigh 8.7 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    4.0 MB

    11 images are downloaded at several times the size a phone draws them, for example Frame-1618872425-5.png at 1,299 px wide, shown at 350 px. Resized copies would save about 4.0 MB.

  • 18 images in older formats

    18 images (10.7 MB) 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.

  • 11 images below the first screen load straight away

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

  • About 6.7 g of CO₂ per visit

    6.68 g

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

Accessibility

7 to fixGoogle 8591
  • 40 tap targets too small

    40 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 14 images without alt text

    14 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (117 elements)

    All page content should be contained by landmarks: 117 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

    14 visible links have no text or label, so screen readers cannot say where they go.

  • 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 (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 8593
  • 3 H1 headlines

    There are 3 <h1> headlines (“Deliver Efficiency - Empower Your Data.”, “Accelerate Your Sales with Microsoft Copilot.” and “Optimize Operations – Your Way”). One clear main headline is easier for people and search engines.

  • 30 links with vague text

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

  • 258 internal links, 13 external

    The homepage links to 258 pages on boyerassoc.com and 13 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Implement ERP, CRM, Business Central, Microsoft Copilot, and Power Virtual Agents with Boyer & Associates. Connect syst…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “ERP, CRM, Microsoft Copilot & Business Central Experts”.

  • Canonical URL set

    The canonical URL is https://www.boyerassoc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Event, ImageObject, Organization and WebPage.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.boyerassoc.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.boyerassoc.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.

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.boyerassoc.com/microsoft-solutions has no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.boyerassoc.com/erp-accounting-consulting-services/support/managed-services-support, whose canonical is https://www.boyerassoc.com/managed-services-support-for-microsoft-dynamics. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.boyerassoc.com/microsoft-solutions, https://www.boyerassoc.com/erp-accounting-consulting-services/support/managed-services-support and https://www.boyerassoc.com/power-platform-consulting-services/support 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 92 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

3 to fixGoogle 7385
  • 12 small tap targets

    12 of 22 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.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdnjs.cloudflare.com/ajax/libs/jquery/…”.

  • 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

2 to fix83
  • Thin social proof

    Social proof on the homepage: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 10-field form

    Your longest form asks for 10 fields (3 required). Every extra field lowers completion.

  • 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 1,913 words of copy

    The homepage carries about 1,913 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Open Contact Us” and “Schedule a call”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Contact Us”, “Close Contact Us Open Contact Us” and “Schedule a call”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 1 email 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 (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 boyerassoc.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

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 boyerassoc.com, including 20 speed issues, 2 SEO issues and 2 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