Website review, no card needed

blackbrookcase.com logo

blackbrookcase.com website review

Visit site (opens in a new tab)Reviewed 6 November 202620 issues · 102 checks

This review found 20 issues worth fixing on blackbrookcase.com, 4 of them high impact, across 102 checks. The most urgent: render-blocking requests. 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
1.4 s687 msMay 16Oct 31816 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.0 s
Sep 26, 2026921 ms
Oct 3, 2026815 ms
Oct 10, 2026765 ms
Oct 17, 2026784 ms
Oct 24, 2026802 ms
Oct 31, 2026816 ms
Real-visitor tap response (INP)75th percentile, phones
125 ms91 msMay 16Oct 31121 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026105 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026111 ms
Jul 11, 2026108 ms
Jul 18, 2026104 ms
Jul 25, 202698 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202697 ms
Aug 22, 2026104 ms
Aug 29, 2026106 ms
Sep 5, 2026109 ms
Sep 12, 2026108 ms
Sep 19, 2026109 ms
Sep 26, 2026112 ms
Oct 3, 2026113 ms
Oct 10, 2026116 ms
Oct 17, 2026118 ms
Oct 24, 2026120 ms
Oct 31, 2026121 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 blackbrookcase.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

blackbrookcase.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix99
  • Render-blocking requests

    1.4 s

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

  • Improve image delivery

    537 KiB

    15 images could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2,781 HTML elements

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

  • Reduce unused CSS

    68 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (rapidlercdn.com, Cloudflare CDN and Shopify and others), adding 219 KiB and 10 ms of main-thread time.

  • Use efficient cache lifetimes

    16 KiB

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

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

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.9 s

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

  • Server response: 23 ms

    23 ms

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

Core Web Vitals

100
  • Tap response (INP) got 16% slower for real visitors

    +16%

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

13 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.0 s

    1.0 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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.0 s

    1.0 s

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

  • Real-user TTFB: 654 ms

    654 ms

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

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

    -36%

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

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.4 s

    1.4 s

    The page is fully interactive after 1.4 s.

Images and page weight

1 to fix90
  • 6 images far larger than shown

    261 KiB

    6 images are downloaded at several times the size a phone draws them, for example carter-detachable-leather-wallet-case-iphone-17-pro-max-sadd at 800 px wide, shown at 174 px. Resized copies would save about 261 KiB.

  • 1 image in older formats

    1 image (71 KiB) is 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.

  • About 0.4 g of CO₂ per visit

    0.43 g

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

2 checks passed
  • Page weight: 1.5 MB in 101 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 101 requests on a phone: images 942 KiB (61), scripts 348 KiB (26) and stylesheets 105 KiB (9). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 8892
  • 48 tap targets too small

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

  • 14 text elements with low contrast

    14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 48 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 8592
  • Structured data has 2 problems

    Structured data found (BreadcrumbList, OnlineStore and WebSite) but with 2 problems, for example “OnlineStore: sameAs is not an absolute URL ("www.pinterest.com/blackbrook_case")”.

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 291 internal links, 4 external

    The homepage links to 291 pages on blackbrookcase.com and 4 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Handcrafted full-grain leather iPhone cases, iPad cases, bags, and accessories. Made by artisans in Istanbul since 2014…”.

  • One H1 headline

    Your main headline reads: “BlackBrook Case”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Full-Grain Leather iPhone Cases & Accessories | BlackBrook Case”.

  • Canonical URL set

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

  • 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://blackbrookcase.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 1 page slow to respond

    /collections/leather-iphone-18-pro-cases took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.

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

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

Best practices

3 to fixGoogle 8185
  • 27 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (blackbrookcase.com).

  • Valid certificate (50 days left)

    The certificate from Google Trust Services · WR1 verifies for blackbrookcase.com and is valid for another 50 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://blackbrookcase.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 44 links work

    All 44 links checked from your homepage (40 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    blackbrookcase.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    blackbrookcase.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 6 years old

    6 years

    blackbrookcase.com was registered in Nov 2019 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Nov 2027

    blackbrookcase.com is registered until Nov 2027.

Content and conversion

3 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 899 words of copy

    The homepage carries about 899 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop all cases →”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Register / Login”, “Shop all cases →” and “Shop Now”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks, a star rating and “125,000+ Customers”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Opening hours shown

    Your opening hours are on the homepage.

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be blackbrookcase.com is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 70/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:amazonses.com include:zohomail.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “selector1” and “selector2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 1 of them by other companies (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.

  • 47 other companies contacted

    Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

  • Selleasy · problem reported Oct 2026attackers planted code in its settings that sent shoppers who pressed Checkout to a fake checkout page taking card details. What to do: update the app, check its settings for code or HTML you didn't add, and test checkout in a private window.

Your store uses an app that was used in an attack. That is not a sign you were hit: check the app as described.

Apps your storefront loads

Tinyseo Ai Seo Speed · Klaviyo Email Marketing Sms · Judge Me Reviews · Zepto Product Personalizer · Zipchat Ai Chatbot · Pb747fb7n Opensend · Redo · Microsoft Clarity · Linkedoption · Selleasy · Restockrocket

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Naples

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on blackbrookcase.com, including 3 speed issues, 3 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