Website review, no card needed

charliesflyboxinc.com logo

charliesflyboxinc.com website review

Visit site (opens in a new tab)Reviewed 21 November 202624 issues · 77 checks

This review found 24 issues worth fixing on charliesflyboxinc.com, 7 of them high impact, across 77 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

Real-visitor load time (LCP)75th percentile, phones
938 ms818 msMay 30Nov 14832 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026924 ms
Jun 6, 2026872 ms
Jun 13, 2026846 ms
Jun 20, 2026836 ms
Jun 27, 2026849 ms
Jul 4, 2026869 ms
Jul 11, 2026887 ms
Jul 18, 2026884 ms
Jul 25, 2026873 ms
Aug 1, 2026868 ms
Aug 8, 2026874 ms
Aug 15, 2026866 ms
Aug 22, 2026867 ms
Aug 29, 2026861 ms
Sep 5, 2026878 ms
Sep 12, 2026892 ms
Sep 19, 2026883 ms
Sep 26, 2026886 ms
Oct 3, 2026866 ms
Oct 10, 2026868 ms
Oct 17, 2026887 ms
Oct 24, 2026891 ms
Oct 31, 2026899 ms
Nov 7, 2026869 ms
Nov 14, 2026832 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms61 msMay 30Nov 1463 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202667 ms
Jun 6, 202666 ms
Jun 13, 202663 ms
Jun 20, 202665 ms
Jun 27, 202665 ms
Jul 4, 202666 ms
Jul 11, 202665 ms
Jul 18, 202664 ms
Jul 25, 202663 ms
Aug 1, 202663 ms
Aug 8, 202664 ms
Aug 15, 202663 ms
Aug 22, 202663 ms
Aug 29, 202663 ms
Sep 5, 202662 ms
Sep 12, 202663 ms
Sep 19, 202663 ms
Sep 26, 202664 ms
Oct 3, 202665 ms
Oct 10, 202668 ms
Oct 17, 202671 ms
Oct 24, 202671 ms
Oct 31, 202670 ms
Nov 7, 202669 ms
Nov 14, 202663 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 charliesflyboxinc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix68
  • Reduce unused JavaScript

    1.1 s · 212 KiB

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

  • Improve image delivery

    300 ms · 856 KiB

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

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    900 ms

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

  • 2,210 HTML elements

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

  • Shopify adds 42 ms

    42 ms

    Shopify costs a phone 42 ms of main-thread work and 294 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.

  • Use efficient cache lifetimes

    150 ms · 19 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, cloudfront.net and avada.io and others), adding 333 KiB and 73 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 8.9 s

    8.9 s

    Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop All Fly Tying”.

  • Time to Interactive: 9.2 s

    9.2 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 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: 1.4 s

    1.4 s

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

  • Real-user INP: 65 ms

    65 ms

    Real visitors wait 65 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: 665 ms

    665 ms

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

  • Speed Index: 3.3 s

    3.3 s

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

  • Cumulative Layout Shift: 0.08

    0.08

    The layout barely moves while loading (CLS 0.08, 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

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

    2.7 MB

    Your homepage downloads 2.7 MB in 196 requests on a phone: images 1.4 MB (16), other files 807 KiB (109) and scripts 457 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    fly-tying_550x.jpg 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).

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9795
  • 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.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious 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.

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

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

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “Fly Tying Materials & Fly Fishing Gear - Fly Tying Tutorials & Videos – Charlie’s Fly Box”.

  • Meta description is long (305 characters)

    Your meta description is 305 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 231 internal links, 8 external

    The homepage links to 231 pages on charliesflyboxinc.com and 8 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://charliesflybox.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: 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,470 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 12 pages without a meta description

    https://charliesflybox.com/collections/all, https://charliesflybox.com/collections/accessories, https://charliesflybox.com/collections/forceps-pliers, https://charliesflybox.com/collections/fly-boxes, https://charliesflybox.com/collections/nippers and https://charliesflybox.com/collections/floatant and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 96 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.

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    19 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 399 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 4 short forms

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 8 other companies contacted

    Loading the homepage contacts 8 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 charliesflyboxinc.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Doc 404 Broken Links Repair · Forms · cloudfront.net

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

Company

Headquarters
Arvada

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on charliesflyboxinc.com, including 9 speed issues, 4 SEO issues and 4 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