Website review, no card needed
urbanarmorgear.com website review
Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 78 checks
This review found 34 issues worth fixing on urbanarmorgear.com, 15 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72C- #94,865 of 122,407 reviewed websitesbeats 19%
- #58,723 of 69,144 online storesbeats 12%
- #54,764 of 62,990 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 191 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 278 ms |
| Oct 31, 2026 | 275 ms |
| Nov 7, 2026 | 272 ms |
| Nov 14, 2026 | 271 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
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.7 s
7.8 s
8.9 s
Speed
Reduce unused JavaScript
1.6 s · 751 KiBAbout 751 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,093 HTML elements
The page has 3,093 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and maestra-static.io and others), adding 1.6 MB and 576 ms of main-thread time.
Use efficient cache lifetimes
718 KiB17 files are served with short cache lifetimes, so returning visitors download them again (718 KiB).
Improve image delivery
385 KiB23 images could be 385 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 150 ms
150 msGoogle Tag Manager costs a phone 150 ms of main-thread work and 357 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.
maestra-static.io adds 114 ms
114 msmaestra-static.io costs a phone 114 ms of main-thread work and 491 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 17.4 s
17.4 sYour largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 15.9 s
15.9 sVisually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Real-user INP: 384 ms
384 msReal visitors wait 384 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 196 ms to 271 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 553 ms
553 msScripts block taps and scrolling for 553 ms in total while the page loads. Good is under 200 ms.
6 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 247 requests
5.4 MBYour homepage downloads 5.4 MB in 247 requests on a phone: scripts 2.6 MB (68), images 1.5 MB (57) and other files 1.1 MB (112). Under 2 MB keeps phones on slow connections fast.
About 1.5 g of CO₂ per visit
1.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (2 elements).
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Rugged Cases & Mobile Accessories Built for You To Go Further | UAG”.
2 H1 headlines
There are 2 <h1> headlines (“EARLY BLACK FRIDAY DEALS” and “EARLY BLACK FRIDAY DEALS”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
38 internal links, 5 external
The homepage links to 38 pages on urbanarmorgear.com and 5 external pages.
6 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Urban Armor Gear produces the most rugged, lightweight, cases that are drop tested to US Military Specs. Made for iPhon…”.
Canonical URL set
The canonical URL is https://www.urbanarmorgear.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://www.urbanarmorgear.com/sitemap.xml.
AI search readiness
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (412 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.urbanarmorgear.com/llms.txt (1 KiB, 13 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://www.urbanarmorgear.com/collections/urban-armor-gear-power-and-cables, https://www.urbanarmorgear.com/collections/virtual-reality-headset, https://www.urbanarmorgear.com/collections/urban-armor-gear-bags-and-sleeves, https://www.urbanarmorgear.com/collections/apple-watches, https://www.urbanarmorgear.com/collections/apple-headphones and https://www.urbanarmorgear.com/collections/airtag have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.urbanarmorgear.com/magnetic-ring-stand has 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 23 found) and read each the way a search engine does.
5 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.
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
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”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
19 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 326 words of copy
The homepage carries about 326 words of visible text.
1 checks passed
7 calls to action
The homepage has 7 calls to action, for example “SHOP IPHONE 18”, “SHOP NOW” and “SHOP”.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Tag Manager, Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) loads with the page.
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 urbanarmorgear.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Vercel
Company
- Employees
- 51
- Headquarters
- Irvine
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 urbanarmorgear.com, including 17 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.