wwpshop.org website review

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

10 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.

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

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

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

5 third-party services load with your homepage (Optanon, Google Tag Manager and FullStory and others), adding 637 KiB and 193 ms of main-thread time.

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

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

23 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

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

Your largest element takes 35.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our site uses cookies and other automated technologies that…”.

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

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

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

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

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

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

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

Your homepage downloads 8.8 MB in 107 requests on a phone: images 7.3 MB (27), scripts 795 KiB (39) and fonts 558 KiB (7). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

2 images (1.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your title is only 23 characters: “Wounded Warrior Project”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“New Gear Now Available”, “Remembering 9/11: Honoring Service” and “Shop With Purpose.”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

There is no robots.txt at wwpshop.org/robots.txt, the first file search crawlers ask for.

4 links have no real href, so search engines can't follow them.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 36 pages on wwpshop.org and 20 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.wwpshop.org/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.

Your homepage links to https://www.wwpshop.org/storeitem.html, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.wwpshop.org/woundedwarriorproject, https://www.wwpshop.org/woundedwarriorproject/shop/apparel, https://www.wwpshop.org/woundedwarriorproject/shop/accessories, https://www.wwpshop.org/woundedwarriorproject/shop/accessories/flags, https://www.wwpshop.org/woundedwarriorproject/shop/view-shop and https://www.wwpshop.org/woundedwarriorproject/shop/gift-cards and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.wwpshop.org/woundedwarriorproject all use the title “Wounded Warrior Project”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.wwpshop.org/woundedwarriorproject/shop/veterans-day-collection, https://www.wwpshop.org/shop/veterans-day-collection, https://www.wwpshop.org/woundedwarriorproject/contact-us, https://www.wwpshop.org/woundedwarriorproject/customer-service/faq and https://www.wwpshop.org/woundedwarriorproject/shipping-information have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wwpshop.org/woundedwarriorproject/shop/view-shop and https://www.wwpshop.org/shop/view-shop use the same meta description. A description written for each page earns more clicks.

https://www.wwpshop.org/woundedwarriorproject/shop/veterans-day-collection, https://www.wwpshop.org/shop/veterans-day-collection and https://www.wwpshop.org/shop/view-shop took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

3 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 468 words of visible text.

Before a visitor clicks anything, the page loads FullStory and Google Tag Manager (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 12 cookies (measured from a US location before any click).

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