Website review, no card needed

citygear.com logo

citygear.com website review

Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 87 checks

This review found 40 issues worth fixing on citygear.com, 17 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
2.1 s1.6 sMay 9Oct 242.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
403 ms175 msMay 9Oct 24328 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026201 ms
May 16, 2026208 ms
May 23, 2026213 ms
May 30, 2026220 ms
Jun 6, 2026228 ms
Jun 13, 2026233 ms
Jun 20, 2026254 ms
Jun 27, 2026284 ms
Jul 4, 2026318 ms
Jul 11, 2026346 ms
Jul 18, 2026352 ms
Jul 25, 2026355 ms
Aug 1, 2026360 ms
Aug 8, 2026369 ms
Aug 15, 2026373 ms
Aug 22, 2026377 ms
Aug 29, 2026375 ms
Sep 5, 2026365 ms
Sep 12, 2026356 ms
Sep 19, 2026342 ms
Sep 26, 2026331 ms
Oct 3, 2026321 ms
Oct 10, 2026321 ms
Oct 17, 2026324 ms
Oct 24, 2026328 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 citygear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. citygear.com at 1.2 s1.2 s
  2. citygear.com at 2.5 s2.5 s
  3. citygear.com at 3.7 s3.7 s
  4. citygear.com at 4.9 s4.9 s
  5. citygear.com at 6.1 s6.1 s
  6. citygear.com at 7.4 s7.4 s
  7. citygear.com at 8.6 s8.6 s
  8. citygear.com at 9.8 s9.8 s

Speed

15 to fix39
  • Use efficient cache lifetimes

    5.3 s · 1.2 MB

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

  • Reduce unused JavaScript

    5.0 s · 955 KiB

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

  • Render-blocking requests

    3.2 s

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

  • Reduce unused CSS

    1.4 s · 201 KiB

    About 201 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 7.2 s

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

  • 3,537 HTML elements

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

  • Improve image delivery

    250 ms · 2.8 MB

    54 images could be 2.8 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, stylitics.com and Clarity and others), adding 2.0 MB and 1.8 s of main-thread time.

  • Signyfyd adds 970 ms

    970 ms

    Signyfyd costs a phone 970 ms of main-thread work and 259 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.

  • 15 long tasks on the main thread

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

  • Minify JavaScript

    470 ms · 65 KiB

    65 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    400 ms · 95 KiB

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

  • stylitics.com adds 194 ms

    194 ms

    stylitics.com costs a phone 194 ms of main-thread work and 610 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.

  • Klaviyo adds 102 ms

    102 ms

    Klaviyo costs a phone 102 ms of main-thread work and 316 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.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

12 to fix33
  • 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: 26.7 s

    26.7 s

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

  • Time to Interactive: 32.1 s

    32.1 s

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

  • Speed Index: 15.0 s

    15.0 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 402 ms

    402 ms

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

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

    +59%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Total Blocking Time: 587 ms

    587 ms

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

  • Cumulative Layout Shift: 0.108

    0.108

    The layout shifts by 0.108 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 9 images without width and height

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

  • Largest content (LCP) got 12% slower for real visitors

    +12%

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

2 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Real-user TTFB: 715 ms

    715 ms

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

Images and page weight

1 to fix70
  • Page weight: 24.3 MB in 554 requests

    24.3 MB

    Your homepage downloads 24.3 MB in 554 requests on a phone: media 14.2 MB (3), images 5.0 MB (107) and scripts 2.7 MB (127). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • About 6.9 g of CO₂ per visit

    6.88 g

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

5 to fixGoogle 9393
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • 15 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 392 internal links, 10 external

    The homepage links to 392 pages on citygear.com and 10 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “The destination for new footwear, apparel, releases and more. Shop the latest trends from top brands like Nike, Jordan,…”.

  • One H1 headline

    Your main headline reads: “DTLR”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “DTLR | Your Fashion. Your Lifestyle | Free Shipping”.

  • Canonical URL set

    The canonical URL is https://www.dtlr.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.dtlr.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,048 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.dtlr.com/pages/shipping, whose canonical is https://www.dtlr.com/pages/customer-service-order-questions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://www.dtlr.com/pages/shipping, https://www.dtlr.com/collections/sale, https://www.dtlr.com/collections/men, https://www.dtlr.com/collections/mens-new-arrivals, https://www.dtlr.com/collections/recent-releases and https://www.dtlr.com/collections/exclusive-hat-heat and 5 others 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 147 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9271
  • 10 broken images

    10 images failed to load on a phone, for example https://content.stylitics.com/images/companion/c/20467011/135b3eaffa9cf03c6c77013af4f8a3b9.

  • 23 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “fast-simon-serp-app not found”.

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 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 532 words of copy

    The homepage carries about 532 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “FALL SAVINGS UP TO 60% OFF | SHOP NOW” and “Shop Jordan Retro , Gorge Green”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “FALL SAVINGS UP TO 60% OFF | SHOP NOW”, “Shop New Arrivals” and “Track Order”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 16 cookies set on arrival

    16

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

  • 59 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 citygear.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
jQuery
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Cloudflare

Company

Employees
1,457
Founded
1945
Headquarters
Birmingham

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on citygear.com, including 27 speed issues, 1 SEO issue 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