Website review, no card needed

bravebooks.us logo

bravebooks.us website review

Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 79 checks

This review found 26 issues worth fixing on bravebooks.us, 6 of them high impact, across 79 checks. The most urgent: main-thread work: 5.8 s. 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.0 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
165 ms133 msMay 23Nov 7137 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026158 ms
May 30, 2026161 ms
Jun 6, 2026160 ms
Jun 13, 2026160 ms
Jun 20, 2026154 ms
Jun 27, 2026153 ms
Jul 4, 2026146 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026139 ms
Aug 1, 2026140 ms
Aug 8, 2026139 ms
Aug 15, 2026139 ms
Aug 22, 2026145 ms
Aug 29, 2026138 ms
Sep 5, 2026141 ms
Sep 12, 2026138 ms
Sep 19, 2026138 ms
Sep 26, 2026138 ms
Oct 3, 2026137 ms
Oct 10, 2026138 ms
Oct 17, 2026138 ms
Oct 24, 2026143 ms
Oct 31, 2026144 ms
Nov 7, 2026137 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 bravebooks.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bravebooks.us at 0.8 s0.8 s
  2. bravebooks.us at 1.6 s1.6 s
  3. bravebooks.us at 2.4 s2.4 s
  4. bravebooks.us at 3.1 s3.1 s
  5. bravebooks.us at 3.9 s3.9 s
  6. bravebooks.us at 4.7 s4.7 s
  7. bravebooks.us at 5.5 s5.5 s
  8. bravebooks.us at 6.3 s6.3 s

Speed

9 to fix73
  • Main-thread work: 5.8 s

    A phone's processor spends 5.8 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Yotpo, Klaviyo and Clarity and others), adding 1.2 MB and 965 ms of main-thread time.

  • Mobile performance score: 73

    73/100

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

  • Render-blocking requests

    600 ms

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

  • Use efficient cache lifetimes

    150 ms · 393 KiB

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

  • Reduce unused JavaScript

    469 KiB

    About 469 KiB of JavaScript is downloaded but never used on this page.

  • Yotpo adds 348 ms

    348 ms

    Yotpo costs a phone 348 ms of main-thread work and 383 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.

  • Klaviyo adds 189 ms

    189 ms

    Klaviyo costs a phone 189 ms of main-thread work and 318 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.

  • 1,610 HTML elements

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

  • Improve image delivery

    150 ms · 62 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    68 KiB

    Polyfills for old browsers add 68 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    16 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 15.0 s

    15.0 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A child reading Team BRAVE: Rise of the Shadows”.

  • Total Blocking Time: 419 ms

    419 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

10 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: 118 ms

    118 ms

    Real visitors wait 118 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 FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 623 ms

    623 ms

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

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

    -12%

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

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

    -17%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 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).

Images and page weight

2 to fix81
  • Page weight: 2.7 MB in 246 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 246 requests on a phone: scripts 1.3 MB (107), other files 721 KiB (80) and images 434 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    America_Wins_250_Bundle_Product_Final.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 4 images in older formats

    4 images (296 KiB) 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.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • 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 9496
  • 4 text elements with low contrast

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

  • Hidden but focusable

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

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

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

Google 100100
  • 76 internal links, 7 external

    The homepage links to 76 pages on bravebooks.us and 7 external pages.

8 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Discover our monthly children’s book subscription teaching biblical values through engaging stories, activities & famil…”.

  • One H1 headline

    Your main headline reads: “American HistoryIs Being Erased”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Children's Books You Can Trust – Brave Books”.

  • Canonical URL set

    The canonical URL is https://bravebooks.us/.

  • Structured data in place

    Structured data found: Organization 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://bravebooks.us/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://bravebooks.us/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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix68
  • 1 page without a title

    https://bravebooks.us/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://bravebooks.us/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://bravebooks.us/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://bravebooks.us/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “[object ProgressEvent]”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • About 773 words of copy

    The homepage carries about 773 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop” and “Book Club”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop”, “Book Club” and “By Age The right book for every age”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 10 trackers load before any consent

    10

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

  • 48 cookies set on arrival

    48

    Opening the homepage sets 48 cookies, 4 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.

  • 69 other companies contacted

    Loading the homepage contacts 69 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 bravebooks.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Wingify · Yotpo Loyalty Rewards · Postscript Sms Marketing · Yotpo Product Reviews · Eg Auto Add To Cart · Triplewhale · Globo Product Options · Test Sms · rechargecdn.com · w3apps.co · wickedreports.com · cloudfront.net · amazonaws.com · retention.com · trustpilot.com

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

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
21 open roles
Job board
careers page

Company

Headquarters
Conroe

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on bravebooks.us, including 13 speed issues and 1 conversion gap. 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