Website review, no card needed

brainrider.com logo

brainrider.com website review

Visit site (opens in a new tab)Reviewed 24 October 202622 issues · 71 checks

This review found 22 issues worth fixing on brainrider.com, 8 of them high impact, across 71 checks. The most urgent: use efficient cache lifetimes. 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 brainrider.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brainrider.com at 0.4 s0.4 s
  2. brainrider.com at 0.8 s0.8 s
  3. brainrider.com at 1.1 s1.1 s
  4. brainrider.com at 1.5 s1.5 s
  5. brainrider.com at 1.9 s1.9 s
  6. brainrider.com at 2.3 s2.3 s
  7. brainrider.com at 2.6 s2.6 s
  8. brainrider.com at 3.0 s3.0 s

Speed

7 to fix62
  • Use efficient cache lifetimes

    1.5 s · 265 KiB

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

  • Reduce unused JavaScript

    1.2 s · 322 KiB

    About 322 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: 62

    62/100

    Your mobile performance score is 62 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    750 ms · 176 KiB

    4 images could be 176 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Adroll and others), adding 1.0 MB and 649 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Google Tag Manager adds 303 ms

    303 ms

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

    150 ms · 42 KiB

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

  • Legacy JavaScript

    150 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 10 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 87 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix62
  • Largest Contentful Paint: 14.4 s

    14.4 s

    Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stuck in an in‑house bottleneck? We help you deliver more, …”.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Total Blocking Time: 235 ms

    235 ms

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

  • 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

100
  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.4 g of CO₂ per visit

    0.39 g

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

3 checks passed
  • Page weight: 1.4 MB in 101 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 101 requests on a phone: scripts 872 KiB (19), images 252 KiB (34) and fonts 171 KiB (8). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9094
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“Stuck in an in‑house bottleneck? We help you deli…” and “Marketing moves faster when creative bottlenecks …”). One clear main headline is easier for people and search engines.

  • 26 internal links, 5 external

    The homepage links to 26 pages on brainrider.com and 5 external pages.

7 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “We're a marketing and creative agency helping ambitious marketers do more, through a global network of curated studios.”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Brainrider Global Creative Services”.

  • Canonical URL set

    The canonical URL is https://brainrider.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://brainrider.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.

  • No llms.txt

    There is no https://brainrider.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 (368 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages share 2 titles

    https://brainrider.com/about and https://brainrider.com/about-us all use the title “About Us | A People-first Marketing and Creative Agency”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://brainrider.com/about and https://brainrider.com/about-us use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://brainrider.com/our-resource-hub 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.

  • 8 internal pages checked

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

6 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

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

  • About 352 words of copy

    The homepage carries about 352 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Get Started” and “Get In Touch”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and 12 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, HubSpot and LinkedIn Insight.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, HubSpot, LinkedIn Insight and Meta Pixel and 1 more (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.

  • 11 cookies set on arrival

    11

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 brainrider.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 Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on brainrider.com, including 12 speed issues, 1 SEO issue 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