Programmable

Website review, no card needed

srchbrand.com logo

srchbrand.com website review

Visit site (opens in a new tab)Reviewed 12 November 202637 issues · 78 checks

This review found 37 issues worth fixing on srchbrand.com, 11 of them high impact, across 78 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

Site score

77C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.6 s3.4 sJun 27Nov 75.3 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 29, 20264.9 s
Sep 5, 20265.2 s
Sep 12, 20265.1 s
Sep 19, 20264.8 s
Sep 26, 20264.8 s
Oct 3, 20264.6 s
Oct 10, 20264.7 s
Oct 17, 20264.9 s
Oct 24, 20265.0 s
Oct 31, 20265.1 s
Nov 7, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
154 ms78 msAug 29Nov 7117 ms
Show as table
DateReal-visitor tap response (INP)
Aug 29, 2026145 ms
Sep 5, 2026137 ms
Sep 12, 2026127 ms
Sep 19, 202699 ms
Sep 26, 202693 ms
Oct 3, 202687 ms
Oct 10, 202690 ms
Oct 17, 202696 ms
Oct 24, 2026104 ms
Oct 31, 2026110 ms
Nov 7, 2026117 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

srchbrand.com (opens in a new tab)
Full-page screenshot of srchbrand.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix74

  • Use efficient cache lifetimes

    13.8 s · 5.8 MB

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

  • Improve image delivery

    13.2 s · 5.3 MB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    900 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cloudflare CDN, Google Fonts and iaris.net), adding 5.5 MB and 24 ms of main-thread time.

  • iaris.net adds 0 ms

    0 ms

    iaris.net costs a phone 0 ms of main-thread work and 5.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 CSS

    18 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed

  • Main-thread work: 0.2 s

    A phone's processor spends 0.2 s on main-thread work while loading, 23 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

4 to fix100

  • Largest Contentful Paint: 16.1 s

    16.1 s

    Your largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Compare product prices at srchbrand.com Search”.

  • Time to Interactive: 16.2 s

    16.2 s

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

  • Largest content (LCP) got 41% slower for real visitors

    +41%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.7 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 2 images without width and height

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

11 checks passed

  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 196 ms

    196 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 593 ms

    593 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.007

    0.007

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix18

  • 9 images over 500 KB

    9 images weigh 5.4 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 6.0 MB in 22 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 22 requests on a phone: images 5.9 MB (13), scripts 29 KiB (2) and stylesheets 26 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    2.9 MB

    9 images are downloaded at several times the size a phone draws them, for example srchbrand-gift-shopping-by-brand-reputation-vs-personal-tast at 844 px wide, shown at 220 px. Resized copies would save about 2.9 MB.

  • 9 images in older formats

    9 images (5.4 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.

  • 2 images below the first screen load straight away

    2 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.7 g of CO₂ per visit

    1.69 g

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

Accessibility

3 to fixGoogle 10096

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 16 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 9254

  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (13 characters)

    Your title is only 13 characters: “srchbrand.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is short (13 characters)

    Your meta description is only 13 characters: “srchbrand.com”. 70 to 160 characters is enough to sell the click.

  • 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 XML sitemap

    No XML sitemap at https://srchbrand.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 36 internal links, 0 external

    The homepage links to 36 pages on srchbrand.com and 0 external pages.

AI search readiness

2 to fix53

  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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://srchbrand.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed

  • Text is in the HTML

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

Other pages

2 to fix93

  • 15 pages share a meta description

    https://srchbrand.com/about, https://srchbrand.com/contact, https://srchbrand.com/advertisers, https://srchbrand.com/terms-conditions, https://srchbrand.com/privacy-policy and https://srchbrand.com/cookie-policy and 9 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://srchbrand.com/contact, https://srchbrand.com/advertisers, https://srchbrand.com/terms-conditions, https://srchbrand.com/privacy-policy, https://srchbrand.com/cookie-policy and https://srchbrand.com/articles/reading-product-reviews-without-falling-for-brand-bias and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://srchbrand.com/contact and https://srchbrand.com/advertisers have 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 16 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 8 small tap targets

    8 of 27 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

5 to fix57

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 233 words

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

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

2 checks passed

  • 2 calls to action

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

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

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 srchbrand.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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on srchbrand.com, including 10 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

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