jansport.com website review

Quantum Metric costs a phone 2.7 s of main-thread work and 113 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

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

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

8 third-party services load with your homepage (Quantum Metric, Dynatrace and Google Tag Manager and others), adding 1.8 MB and 4.5 s of main-thread time.

62 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).

About 1,014 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Dynatrace costs a phone 672 ms of main-thread work and 144 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 costs a phone 619 ms of main-thread work and 368 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.

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

Yotpo costs a phone 108 ms of main-thread work and 735 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.

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

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

11 KiB JavaScript is shipped twice across bundles.

10 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Good Trips Start Here”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 11.2 MB in 671 requests on a phone: media 3.5 MB (1), scripts 3.2 MB (179) and images 2.5 MB (91). Under 2 MB keeps phones on slow connections fast.

JSP_Bundle_LP_Mobile_Hero-V3.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).

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

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

1 element hidden from screen readers can still receive keyboard focus.

1 text element doesn'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 on the page fail this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 22 characters: “JanSport | Jansport US”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Room For Real Life” and “Good Things Come In Sets”). One clear main headline is easier for people and search engines.

Structured data found (Brand, OnlineStore, WebPage and WebSite) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected end of JSON input)”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 123 pages on jansport.com and 2 external pages.

Your homepage links to https://www.jansport.com/en-ushttps://www.jansport.com/pages/faq, https://www.jansport.com/en-ushttps://www.jansport.com/pages/returns and https://www.jansport.com/en-ushttps://www.jansport.com/pages/warranty, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.jansport.com/collections/backpack-bundles-1 and https://www.jansport.com/en-us/collections/backpack-bundles-1 all use the title “Practical Backpack Bundles: Matching Styles | Jansport US”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jansport.com/en-us/pages/rewards and https://www.jansport.com/en-us/pages/select-your-location have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jansport.com/collections/backpack-bundles-1 and https://www.jansport.com/en-us/collections/backpack-bundles-1 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.jansport.com/collections/backpack-bundles-1, whose canonical is https://www.jansport.com/en-us/collections/backpack-bundles-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.jansport.com/en-us/pages/rewards, https://www.jansport.com/en-us/pages/promotion-terms and https://www.jansport.com/en-us/pages/sale have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.

6 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 569 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Tag Manager, Meta Pixel and Microsoft Ads and 4 mores (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.

Opening the homepage sets 37 cookies (measured from a US location before any click).

Loading the homepage contacts 57 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.