Website review, no card needed

thebernardgroup.com logo

thebernardgroup.com website review

Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 76 checks

This review found 33 issues worth fixing on thebernardgroup.com, 17 of them high impact, across 76 checks. The most urgent: improve image delivery. 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

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.7 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
100 ms76 msMay 9Oct 2497 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202688 ms
May 23, 202685 ms
May 30, 202688 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202684 ms
Jun 27, 202685 ms
Jul 4, 202685 ms
Jul 11, 202685 ms
Jul 18, 202683 ms
Jul 25, 202679 ms
Aug 1, 202681 ms
Aug 8, 202682 ms
Aug 15, 202684 ms
Aug 22, 202685 ms
Aug 29, 202682 ms
Sep 5, 202684 ms
Sep 12, 202687 ms
Sep 19, 202684 ms
Sep 26, 202683 ms
Oct 3, 202686 ms
Oct 10, 202689 ms
Oct 17, 202693 ms
Oct 24, 202697 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 thebernardgroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thebernardgroup.com at 0.4 s0.4 s
  2. thebernardgroup.com at 0.9 s0.9 s
  3. thebernardgroup.com at 1.3 s1.3 s
  4. thebernardgroup.com at 1.7 s1.7 s
  5. thebernardgroup.com at 2.1 s2.1 s
  6. thebernardgroup.com at 2.6 s2.6 s
  7. thebernardgroup.com at 3.0 s3.0 s
  8. thebernardgroup.com at 3.4 s3.4 s

Speed

8 to fix48
  • Improve image delivery

    1.6 s · 3.4 MB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.2 s · 249 KiB

    About 249 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 48

    48/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google Analytics and zi-scripts.com and others), adding 523 KiB and 691 ms of main-thread time.

  • Google Tag Manager adds 636 ms

    636 ms

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

  • Reduce unused CSS

    300 ms · 53 KiB

    About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 7 long tasks on the main thread

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

  • Minify CSS

    23 KiB

    23 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    22 KiB

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user FCP: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We build brand statements. One captivating experience at a …”.

  • Time to Interactive: 10.2 s

    10.2 s

    The page becomes fully interactive after 10.2 s. Good is under 3.8 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.

  • Speed Index: 6.7 s

    6.7 s

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

  • Total Blocking Time: 565 ms

    565 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

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

  • Real-user TTFB: 716 ms

    716 ms

    Real visitors wait 716 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s 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

5 to fix18
  • Page weight: 4.3 MB in 51 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 51 requests on a phone: images 3.5 MB (17), scripts 643 KiB (13) and fonts 117 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 14 images far larger than shown

    2.5 MB

    14 images are downloaded at several times the size a phone draws them, for example 2026-Shop-Awards-14-1024x1024.png at 1,024 px wide, shown at 171 px. Resized copies would save about 2.5 MB.

  • 1 image over 500 KB

    2026-Shop-Awards-14-1024x1024.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 13 images in older formats

    13 images (3.3 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.

  • 6 images below the first screen load straight away

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

  • About 1.2 g of CO₂ per visit

    1.22 g

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

Accessibility

2 to fixGoogle 8594
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

2 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (24 characters)

    Your title is only 24 characters: “Home - The Bernard Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 51 internal links, 1 external

    The homepage links to 51 pages on thebernardgroup.com and 1 external page.

6 checks passed
  • One H1 headline

    Your main headline reads: “Welcome”.

  • Canonical URL set

    The canonical URL is https://thebernardgroup.com/.

  • Structured data in place

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

  • 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://thebernardgroup.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://thebernardgroup.com/llms.txt (4 KiB, 37 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://thebernardgroup.com/what-we-do, https://thebernardgroup.com/what-we-do/prototype-lab, https://thebernardgroup.com/what-we-do/fixture-production, https://thebernardgroup.com/what-we-do/print-production, https://thebernardgroup.com/what-we-do/branded-solutions and https://thebernardgroup.com/what-we-do/logistics and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://thebernardgroup.com/projects/building-big-ideas, https://thebernardgroup.com/projects/remedy-launch-endcap, https://thebernardgroup.com/projects/tbg-adidas-brought-the-world-cup-to-the-neighborhood and https://thebernardgroup.com/projects/world-cup-gumball-drop have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://thebernardgroup.com/sustainability 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 31 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

1 to fixGoogle 10093
  • 7 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 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 164 words

    The homepage has only about 164 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
  • 3 calls to action

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

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 thebernardgroup.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
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on thebernardgroup.com, including 16 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

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