Website review, no card needed
brandirectory.com website review
Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 65 checks
This review found 40 issues worth fixing on brandirectory.com, 17 of them high impact, across 65 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.2 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 352 ms |
| May 16, 2026 | 384 ms |
| May 23, 2026 | 387 ms |
| May 30, 2026 | 394 ms |
| Jun 6, 2026 | 374 ms |
| Jun 13, 2026 | 366 ms |
| Jun 20, 2026 | 406 ms |
| Jun 27, 2026 | 428 ms |
| Jul 4, 2026 | 413 ms |
| Jul 11, 2026 | 356 ms |
| Jul 18, 2026 | 296 ms |
| Jul 25, 2026 | 252 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 208 ms |
| Aug 22, 2026 | 210 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 218 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 207 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 186 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 203 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
10.8 s · 3.2 MB24 files are served with short cache lifetimes, so returning visitors download them again (3.2 MB).
Render-blocking requests
6.9 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.9 s.
Reduce unused JavaScript
2.4 s · 475 KiBAbout 475 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Improve image delivery
1.2 MB15 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 278 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and Sentry), adding 83 KiB and 0 ms of main-thread time.
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, 698 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 11.8 s
11.8 sThe first text or image appears after 11.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 14.8 s
14.8 sYour largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content, to provide social me…”.
Time to Interactive: 25.3 s
25.3 sThe page becomes fully interactive after 25.3 s. Good is under 3.8 s.
Speed Index: 11.8 s
11.8 sVisually, the page fills in at 11.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Tap response (INP) got 45% faster for real visitors
-45%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 352 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 11 ms
11 msScripts block the page for only 11 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.9 MB in 42 requests
4.9 MBYour homepage downloads 4.9 MB in 42 requests on a phone: other files 1.5 MB (14), images 1.3 MB (20) and fonts 881 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
1 checks passed
33 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: 33 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at brandirectory.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
XML sitemap found
Your XML sitemap is reachable at https://brandirectory.com/sitemap.xml.
AI search readiness
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://brandirectory.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 136 words
The homepage has only about 136 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.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us”.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 brandirectory.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on brandirectory.com, including 17 speed issues, 9 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.