Website review, no card needed

urbankitsupply.com logo

urbankitsupply.com website review

Visit site (opens in a new tab)Reviewed 11 November 202638 issues · 76 checks

This review found 38 issues worth fixing on urbankitsupply.com, 18 of them high impact, across 76 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
1.9 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
158 ms115 msMay 23Nov 7153 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026122 ms
May 30, 2026121 ms
Jun 6, 2026121 ms
Jun 13, 2026121 ms
Jun 20, 2026122 ms
Jun 27, 2026126 ms
Jul 4, 2026122 ms
Jul 11, 2026124 ms
Jul 18, 2026122 ms
Jul 25, 2026120 ms
Aug 1, 2026127 ms
Aug 8, 2026125 ms
Aug 15, 2026123 ms
Aug 22, 2026128 ms
Aug 29, 2026126 ms
Sep 5, 2026122 ms
Sep 12, 2026121 ms
Sep 19, 2026121 ms
Sep 26, 2026120 ms
Oct 3, 2026129 ms
Oct 10, 2026137 ms
Oct 17, 2026145 ms
Oct 24, 2026150 ms
Oct 31, 2026151 ms
Nov 7, 2026153 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 urbankitsupply.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. urbankitsupply.com at 1.1 s1.1 s
  2. urbankitsupply.com at 2.3 s2.3 s
  3. urbankitsupply.com at 3.4 s3.4 s
  4. urbankitsupply.com at 4.5 s4.5 s
  5. urbankitsupply.com at 5.6 s5.6 s
  6. urbankitsupply.com at 6.8 s6.8 s
  7. urbankitsupply.com at 7.9 s7.9 s
  8. urbankitsupply.com at 9.0 s9.0 s

Speed

10 to fix40
  • Reduce unused JavaScript

    3.1 s · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Render-blocking requests

    3.1 s

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

  • Mobile performance score: 40

    40/100

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

  • 5,378 HTML elements

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and omnisnippet1.com and others), adding 2.1 MB and 1.0 s of main-thread time.

  • Reduce unused CSS

    450 ms · 159 KiB

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

  • Google Tag Manager adds 480 ms

    480 ms

    Google Tag Manager costs a phone 480 ms of main-thread work and 692 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.

  • Shopify adds 421 ms

    421 ms

    Shopify costs a phone 421 ms of main-thread work and 1.1 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.

  • 8 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 58 KiB

    58 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 44 KiB

    44 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    113 KiB

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 12.2 s

    12.2 s

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

  • Speed Index: 12.6 s

    12.6 s

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

  • Time to Interactive: 13.1 s

    13.1 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Total Blocking Time: 706 ms

    706 ms

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

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

    +25%

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

  • 4 images without width and height

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

8 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.5 s

    1.5 s

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

  • Real-user INP: 150 ms

    150 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 683 ms

    683 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 349 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 349 requests on a phone: scripts 2.0 MB (159), images 1.3 MB (36) and other files 1.1 MB (137). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

8 to fixGoogle 8989
  • 7 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Invalid ARIA attributes

    6 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 27 text elements with low contrast

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

  • 1 form field without a label

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

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail 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. (5 elements).

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 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 9282
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 5 links crawlers can't follow

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

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “For the creative pro or modern adventurer. Dedicated to bring you high-quality gear that makes your life simpler and su…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Urban Kit Supply: Bringing Better Gear for Active Lifestyle”.

  • Canonical URL set

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

  • 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.urbankitsupply.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

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.

  • llms.txt published

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 direct contact details

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

  • Only about 59 words

    The homepage has only about 59 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 11 of them by other companies (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.

  • 12 other companies contacted

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

Apps your storefront loads

Blockify Fraud Filter · Pandectes Gdpr · Candy Rack · Judge Me Reviews · Analyzify Ga4 Ads Tracking · Simprosys Google Shopping Feed · Ex Show Variants · Region Restrictions · Gdpr Cookie Consent · Variants As Separate Products · avada.io

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
Hosting
Shopify

Company

Headquarters
Naantali

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on urbankitsupply.com, including 17 speed issues, 4 SEO issues and 5 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

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