Website review, no card needed

mysterytacklebox.com logo

mysterytacklebox.com website review

Visit site (opens in a new tab)Reviewed 8 November 202636 issues · 87 checks

This review found 36 issues worth fixing on mysterytacklebox.com, 12 of them high impact, across 87 checks. The most urgent: main-thread work: 12.1 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.5 s2.0 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
174 ms142 msMay 16Oct 31146 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026163 ms
May 23, 2026162 ms
May 30, 2026166 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026167 ms
Jun 27, 2026163 ms
Jul 4, 2026168 ms
Jul 11, 2026163 ms
Jul 18, 2026163 ms
Jul 25, 2026163 ms
Aug 1, 2026162 ms
Aug 8, 2026166 ms
Aug 15, 2026159 ms
Aug 22, 2026161 ms
Aug 29, 2026162 ms
Sep 5, 2026162 ms
Sep 12, 2026170 ms
Sep 19, 2026170 ms
Sep 26, 2026168 ms
Oct 3, 2026163 ms
Oct 10, 2026160 ms
Oct 17, 2026153 ms
Oct 24, 2026147 ms
Oct 31, 2026146 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 mysterytacklebox.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mysterytacklebox.com at 1.1 s1.1 s
  2. mysterytacklebox.com at 2.3 s2.3 s
  3. mysterytacklebox.com at 3.4 s3.4 s
  4. mysterytacklebox.com at 4.6 s4.6 s
  5. mysterytacklebox.com at 5.7 s5.7 s
  6. mysterytacklebox.com at 6.9 s6.9 s
  7. mysterytacklebox.com at 8.0 s8.0 s
  8. mysterytacklebox.com at 9.1 s9.1 s

Speed

14 to fix36
  • Main-thread work: 12.1 s

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,163 HTML elements

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

  • Improve image delivery

    750 ms · 2.1 MB

    36 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, rebuyengine.com and Google Tag Manager and others), adding 5.5 MB and 1.6 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.

  • Reduce unused JavaScript

    781 KiB

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

  • Render-blocking requests

    750 ms

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

  • alia-prod.com adds 488 ms

    488 ms

    alia-prod.com costs a phone 488 ms of main-thread work and 930 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

    569 KiB

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

  • Builder adds 94 ms

    94 ms

    Builder costs a phone 94 ms of main-thread work and 3.3 MB 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.

  • rebuyengine.com adds 235 ms

    235 ms

    rebuyengine.com costs a phone 235 ms of main-thread work and 418 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 174 ms

    174 ms

    Klaviyo costs a phone 174 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.

  • rechargecdn.com adds 142 ms

    142 ms

    rechargecdn.com costs a phone 142 ms of main-thread work and 296 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.

  • Legacy JavaScript

    66 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    39 KiB

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • 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

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 29 ms

    29 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 18.8 s

    18.8 s

    Your largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 15.8 s

    15.8 s

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

  • Time to Interactive: 45.2 s

    45.2 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • 73 images without width and height

    73 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    2.3 s

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

  • Real-user INP: 128 ms

    128 ms

    Real visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 484 ms

    484 ms

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

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

    -10%

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

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

    -13%

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

  • Cumulative Layout Shift: 0.021

    0.021

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

Images and page weight

2 to fix60
  • Page weight: 9.3 MB in 374 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 374 requests on a phone: images 3.1 MB (67), fonts 2.9 MB (22) and scripts 2.1 MB (113). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    46 KiB

    2 images are downloaded at several times the size a phone draws them, for example feat-img-ultimate-urchin-kit-w1.jpg at 600 px wide, shown at 158 px. Resized copies would save about 46 KiB.

  • About 2.6 g of CO₂ per visit

    2.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.64 g of CO₂e: 316.2 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 load when needed

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

Accessibility

3 to fixGoogle 9496
  • 3 text elements with low contrast

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 188 images in the HTML carry an alt attribute.

  • 52 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: 52 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “CATCH MORE FISH”). One clear main headline is easier for people and search engines.

  • Meta description is long (250 characters)

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

  • 116 internal links, 7 external

    The homepage links to 116 pages on mysterytacklebox.com and 7 external pages.

6 checks passed
  • Title: 53 characters

    Your title is a healthy 53 characters: “Mystery Tackle Box | Your Fishing Tackle Subscription”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

6 to fix48
  • 2 linked pages are broken

    Your homepage links to https://mysterytacklebox.com/regular-plan and https://mysterytacklebox.com/elite-plan, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://mysterytacklebox.com/products/mtb-scale-series-soft-cooler declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 4 pages share 2 titles

    / and https://mysterytacklebox.com/products/mtb-scale-series-soft-cooler all use the title “Mystery Tackle Box | Your Fishing Tackle Subscription”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://mysterytacklebox.com/pages/gift-plans-v2, https://mysterytacklebox.com/collections/0-50, https://mysterytacklebox.com/collections/50-150, https://mysterytacklebox.com/collections/150 and https://mysterytacklebox.com/collections/one-time-kits have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://mysterytacklebox.com/pro-plan and https://mysterytacklebox.com/pages/pro-plan use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://mysterytacklebox.com/plans, https://mysterytacklebox.com/pro-plan, https://mysterytacklebox.com/pages/regular-plan, https://mysterytacklebox.com/pages/pro-plan and https://mysterytacklebox.com/pages/elite-plan 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 50 found) and read each the way a search engine does.

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 5 broken images

    5 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17223145&tm=gtm002&Ver=2&mid=2a613e20-91be-488d-9d42-31a1bb25321c&bo=1&sid=117f5260db7a11f1be0b230784f138ef&vid=117f7f10db7a11f1b49cab4a4325f16f&vids=1&msclkid=N&pi=91.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 2 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    29 of 34 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 744 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 PLANS”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All Plans →”, “Shop All →” and “Get started”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 123 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

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.

  • 47 cookies set on arrival

    47

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

  • 57 other companies contacted

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

Apps your storefront loads

Sp Hide Price B2b Lock · Intelligems A B Testing · Klaviyo Email Marketing Sms · Addingwell · Yotpo Loyalty Rewards · Microsoft Clarity · Judge Me Reviews · Userway Website Accessibility · builder.io · cart-bot.net · nice-team.net · rechargecdn.com · cloudfront.net · superfiliate-cdn.com · rebuyengine.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

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on mysterytacklebox.com, including 20 speed issues and 2 SEO issues. 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