Website review, no card needed
firebooks.com website review
Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 94 checks
This review found 41 issues worth fixing on firebooks.com, 10 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
79C- #54,913 of 122,656 reviewed websitesbeats 50%
- #36,202 of 69,234 online storesbeats 42%
- #276 of 893 BigCommerce storesbeats 63%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 110 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 118 ms |
| Oct 24, 2026 | 116 ms |
| Oct 31, 2026 | 113 ms |
| Nov 7, 2026 | 112 ms |
| Nov 14, 2026 | 111 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
Speed
Reduce unused JavaScript
1.9 s · 603 KiBAbout 603 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.1 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
3,265 HTML elements
The page has 3,265 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Bigcommerce, Google Tag Manager and Klaviyo and others), adding 2.2 MB and 1.1 s of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 269 KiB53 files are served with short cache lifetimes, so returning visitors download them again (269 KiB).
Legacy JavaScript
400 ms · 65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Bigcommerce adds 382 ms
382 msBigcommerce costs a phone 382 ms of main-thread work and 770 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.
Google Tag Manager adds 343 ms
343 msGoogle Tag Manager costs a phone 343 ms of main-thread work and 532 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 121 ms
121 msKlaviyo costs a phone 121 ms of main-thread work and 313 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.
userway.org adds 68 ms
68 msuserway.org costs a phone 68 ms of main-thread work and 295 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 · 59 KiBAbout 59 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 148 ms. During a long task the page ignores taps.
Improve image delivery
51 KiB2 images could be 51 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Essentials of Fire Fighting, 7th Edition 36777 IFSTA at Cur…”.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 789 ms
789 msReal visitors wait 789 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 137 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 198 ms
198 msScripts block the page for only 198 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 2.7 MB in 215 requests
2.7 MBYour homepage downloads 2.7 MB in 215 requests on a phone: scripts 1.7 MB (75), images 329 KiB (65) and other files 295 KiB (60). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
25 text elements with low contrast
25 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail 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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 56 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
452 internal links, 5 external
The homepage links to 452 pages on firebooks.com and 5 external pages.
7 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “Shop Books, Guides & Manuals designed for firefighters and professionals for performance and safety at Curtis - Tools f…”.
One H1 headline
Your main headline reads: “Books, Guides & Manuals”.
Title: 54 characters
Your title is a healthy 54 characters: “Books, Guides & Manuals | LN Curtis - Tools for Heroes”.
Canonical URL set
The canonical URL is https://lncurtis.com/firefighter-books-guides/.
Structured data in place
Structured data found: BreadcrumbList.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://lncurtis.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,906 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://lncurtis.com/llms.txt (6 KiB, 24 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://lncurtis.com/gift-card, https://lncurtis.com/ppe-care-maintenance, https://lncurtis.com/wildland-clothing, https://lncurtis.com/wildland-jumpsuits, https://lncurtis.com/wildland-multifunction and https://lncurtis.com/wildland-base-layers and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lncurtis.com/wildland, whose canonical is https://lncurtis.com/wildland-firefighter. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://lncurtis.com/shop-brands 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 197 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=149017752&Ver=2&mid=9729c604-5d94-453f-a886-f1d9065c047e&bo=1&sid=b2574070e53611f1b4df6f8842e42fb9&vid=b2577620e53611f1988ea1d02213b0c9&vids=1&msclkid=N&pi=918639831&l.
11 small tap targets
11 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'storefront_api')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
A 12-field form
Your longest form asks for 12 fields (0 required). Every extra field lowers completion.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 522 words of copy
The homepage carries about 522 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP DEALS”.
9 calls to action
The homepage has 9 calls to action, for example “CONTACT US”, “Register” and “Agency Sign Up”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 2 of them by other companies (measured from a US location before any click).
29 other companies contacted
Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 firebooks.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- BigCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Network Solutions, LLC
Hiring
- Hiring
- 9 open roles
- Teams
- Service (2), Accounting (1), CBL Gilbert (1), Customer Service - Fire (1)
- Job board
- paylocity
- Careers page
- lncurtis.com/job-shirts (opens in a new tab)
Company
- Headquarters
- La Mirada
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on firebooks.com, including 17 speed issues, 3 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.