Website review, no card needed

maxpedition.com logo

maxpedition.com website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 81 checks

This review found 34 issues worth fixing on maxpedition.com, 12 of them high impact, across 81 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
989 ms800 msMay 16Oct 31822 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026936 ms
May 23, 2026936 ms
May 30, 2026931 ms
Jun 6, 2026946 ms
Jun 13, 2026947 ms
Jun 20, 2026959 ms
Jun 27, 2026967 ms
Jul 4, 2026952 ms
Jul 11, 2026943 ms
Jul 18, 2026930 ms
Jul 25, 2026913 ms
Aug 1, 2026900 ms
Aug 8, 2026889 ms
Aug 15, 2026893 ms
Aug 22, 2026914 ms
Aug 29, 2026933 ms
Sep 5, 2026958 ms
Sep 12, 2026960 ms
Sep 19, 2026957 ms
Sep 26, 2026955 ms
Oct 3, 2026942 ms
Oct 10, 2026914 ms
Oct 17, 2026881 ms
Oct 24, 2026846 ms
Oct 31, 2026822 ms
Real-visitor tap response (INP)75th percentile, phones
98 ms65 msMay 16Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202679 ms
May 30, 202680 ms
Jun 6, 202681 ms
Jun 13, 202680 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202677 ms
Jul 11, 202676 ms
Jul 18, 202673 ms
Jul 25, 202672 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202671 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202669 ms
Sep 26, 202669 ms
Oct 3, 202670 ms
Oct 10, 202671 ms
Oct 17, 202678 ms
Oct 24, 202683 ms
Oct 31, 202694 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 maxpedition.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. maxpedition.com at 0.7 s0.7 s
  2. maxpedition.com at 1.4 s1.4 s
  3. maxpedition.com at 2.2 s2.2 s
  4. maxpedition.com at 2.9 s2.9 s
  5. maxpedition.com at 3.6 s3.6 s
  6. maxpedition.com at 4.3 s4.3 s
  7. maxpedition.com at 5.1 s5.1 s
  8. maxpedition.com at 5.8 s5.8 s

Speed

8 to fix62
  • 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.

  • 4,025 HTML elements

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

  • Improve image delivery

    700 ms · 891 KiB

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

  • Use efficient cache lifetimes

    950 ms · 164 KiB

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

  • Mobile performance score: 62

    62/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (amplifiedcdn.com, Shopify and searchserverapi.com and others), adding 605 KiB and 516 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 54 KiB

    About 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.8 s

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

  • Render-blocking requests

    150 ms

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.1 s

    10.1 s

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

  • Time to Interactive: 10.1 s

    10.1 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Speed Index: 6.6 s

    6.6 s

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

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

    +12%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 94 ms 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.0 s

    1.0 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 342 ms

    342 ms

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

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

    -11%

    Over the last 25 four-week periods to 2026-10-31, 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).

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 33 ms

    33 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.1 MB in 184 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 184 requests on a phone: images 1.6 MB (26), other files 700 KiB (96) and scripts 668 KiB (47). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Slide-JumboNovoPlus-Mob.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.9 g of CO₂ per visit

    0.89 g

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

9 to fixGoogle 7989
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 13 tap targets too small

    13 tap targets are too small or too close together to hit reliably with a finger.

  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • Links must have discernible text (1 element)

    Links must have discernible text: 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • 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 58 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 10081
  • Title is short (11 characters)

    Your title is only 11 characters: “Maxpedition”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (40 characters)

    Your meta description is only 40 characters: “Maxpedition premium tactical nylon bags.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.maxpedition.com/sitemap.xml, so Google discovers your pages only by following links.

  • 165 internal links, 2 external

    The homepage links to 165 pages on maxpedition.com and 2 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “MAXPEDITION”.

  • Canonical URL set

    The canonical URL is https://www.maxpedition.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to /collections/waist-packs, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    /collections/all-bags-packs and /collections/sling-packs-bags have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    /collections/bogo-pocket-organizers and /collections/legacy 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 63 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 14 small tap targets

    14 of 50 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

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

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

    The homepage carries about 781 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: “Buy 1 Get 1 Free Pocket Organizers”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Buy 1 Get 1 Free Pocket Organizers”, “Buy 1 Get 1 FREE” and “Shop Customer Photos”.

  • 9 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 17 other companies contacted

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

Apps your storefront loads

Pandectes Gdpr · Frequently Bought · Gdpr Cookie Consent · Easy Tabs Product Tabs · signifyd.com · zotabox.com · boldapps.net · searchserverapi.com · amplifiedcdn.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
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

Company

Headquarters
Rolling Hills

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on maxpedition.com, including 12 speed issues, 4 SEO 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