Website review, no card needed

fireequipmentdirect.com logo

fireequipmentdirect.com website review

Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 71 checks

This review found 28 issues worth fixing on fireequipmentdirect.com, 8 of them high impact, across 71 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of fireequipmentdirect.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix64
  • Reduce unused JavaScript

    1.5 s · 418 KiB

    About 418 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 64

    64/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (accessify.app, Shopify and Google CDN and others), adding 1.0 MB and 339 ms of main-thread time.

  • Improve image delivery

    318 KiB

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

  • 2,812 HTML elements

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

  • Main-thread work: 2.4 s

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

  • accessify.app adds 208 ms

    208 ms

    accessify.app costs a phone 208 ms of main-thread work and 317 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.

  • Shopify adds 99 ms

    99 ms

    Shopify costs a phone 99 ms of main-thread work and 631 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 long task on the main thread

    1 long task block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    44 KiB

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

  • Minify JavaScript

    30 ms · 12 KiB

    12 KiB could be saved by minifying JavaScript.

  • Minify CSS

    30 ms · 2 KiB

    2 KiB could be saved by minifying CSS.

  • Reduce unused CSS

    12 KiB

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “banner-video”.

  • Time to Interactive: 10.4 s

    10.4 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.1 s

    6.1 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

2 to fix60
  • Page weight: 5.9 MB in 269 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 269 requests on a phone: media 3.3 MB (2), scripts 1.0 MB (118) and images 697 KiB (37). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    292 KiB

    4 images are downloaded at several times the size a phone draws them, for example Monarch_Cylinders.jpg at 1,688 px wide, shown at 127 px. Resized copies would save about 292 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (241 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.7 g of CO₂ per visit

    1.67 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9797
  • 11 text elements with low contrast

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 56 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Fire Equipment Direct - Trusted Partner in Fire Protection Equipment”.

  • Structured data has 4 problems

    Structured data found (Organization and WebSite) but with 4 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

  • One H1 headline

    Your <h1> is empty.

  • 449 internal links, 9 external

    The homepage links to 449 pages on fireequipmentdirect.com and 9 external pages.

5 checks passed
  • Meta description: 101 characters

    Your meta description is 101 characters: “Specializes in providing a wide range of fire equipment products, sourced from trusted manufacturers.”.

  • Canonical URL set

    The canonical URL is https://fireequipmentdirect.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://fireequipmentdirect.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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 (1,743 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix68
  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 3 pages without a meta description

    https://fireequipmentdirect.com/customer_authentication/redirect, https://fireequipmentdirect.com/policies/shipping-policy and https://fireequipmentdirect.com/pages/wholesale_registration have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://fireequipmentdirect.com/customer_authentication/redirect and https://fireequipmentdirect.com/pages/wholesale_registration have 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.

3 checks passed
  • Linked pages load

    9 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 8891
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 12 distorted images

    12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    27 of 28 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 3 trust badges. 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 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 389 words of copy

    The homepage carries about 389 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register now for wholesale access!”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Register now for wholesale access!”, “Register Now” and “Contact Us”.

  • 19 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 fireequipmentdirect.com, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Ai Accessibility · Forms · Appstle Loyalty

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on fireequipmentdirect.com, including 12 speed issues, 3 SEO issues and 2 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