Website review, no card needed

code-wallets.com logo

code-wallets.com website review

Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 80 checks

This review found 34 issues worth fixing on code-wallets.com, 9 of them high impact, across 80 checks. The most urgent: main-thread work: 11.6 s. 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.4 s2.1 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
214 ms127 msMay 30Nov 14140 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026171 ms
Jun 6, 2026178 ms
Jun 13, 2026170 ms
Jun 20, 2026146 ms
Jun 27, 2026137 ms
Jul 4, 2026138 ms
Jul 11, 2026157 ms
Jul 18, 2026187 ms
Jul 25, 2026203 ms
Aug 1, 2026197 ms
Aug 8, 2026179 ms
Aug 15, 2026159 ms
Aug 22, 2026162 ms
Aug 29, 2026154 ms
Sep 5, 2026171 ms
Sep 12, 2026203 ms
Sep 19, 2026199 ms
Sep 26, 2026204 ms
Oct 3, 2026196 ms
Oct 10, 2026167 ms
Oct 17, 2026139 ms
Oct 24, 2026142 ms
Oct 31, 2026140 ms
Nov 7, 2026138 ms
Nov 14, 2026140 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 code-wallets.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. code-wallets.com at 1.1 s1.1 s
  2. code-wallets.com at 2.2 s2.2 s
  3. code-wallets.com at 3.2 s3.2 s
  4. code-wallets.com at 4.3 s4.3 s
  5. code-wallets.com at 5.4 s5.4 s
  6. code-wallets.com at 6.5 s6.5 s
  7. code-wallets.com at 7.5 s7.5 s
  8. code-wallets.com at 8.6 s8.6 s

Speed

11 to fix52
  • Main-thread work: 11.6 s

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

  • 4,235 HTML elements

    The page has 4,235 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 (alia-prod.com, Cloudflare CDN and applovin.com and others), adding 745 KiB and 1.1 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Use efficient cache lifetimes

    350 ms · 485 KiB

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

  • Render-blocking requests

    800 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused JavaScript

    300 ms · 311 KiB

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

  • Improve image delivery

    556 KiB

    28 images could be 556 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • alia-prod.com adds 480 ms

    480 ms

    alia-prod.com costs a phone 480 ms of main-thread work and 312 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.

  • Reduce unused CSS

    450 ms · 54 KiB

    About 54 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.

  • Cloudflare CDN adds 306 ms

    306 ms

    Cloudflare CDN costs a phone 306 ms of main-thread work and 58 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.

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    29 KiB

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

8 to fix100
  • 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: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “CODE 118 wallets in every color, laid out on a dark table”.

  • Time to Interactive: 27.7 s

    27.7 s

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

  • Speed Index: 12.2 s

    12.2 s

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

  • 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: 438 ms

    438 ms

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

  • 35 images without width and height

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

6 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 104 ms

    104 ms

    Real visitors wait 104 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 TTFB: 771 ms

    771 ms

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

  • Tap response (INP) got 20% faster for real visitors

    -20%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 7.5 MB in 546 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 546 requests on a phone: images 4.4 MB (172), other files 1.5 MB (271) and scripts 1.1 MB (81). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    165 KiB

    4 images are downloaded at several times the size a phone draws them, for example 83.jpg at 1,000 px wide, shown at 190 px. Resized copies would save about 165 KiB.

  • 1 image in older formats

    1 image (49 KiB) is 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 below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.11 g

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

Accessibility

4 to fixGoogle 9095
  • 41 tap targets too small

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

  • 37 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

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

  • 8 links without text

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

2 checks passed
  • Every image has alt text

    All 223 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (282 characters)

    Your meta description is 282 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 204 internal links, 10 external

    The homepage links to 204 pages on code-wallets.com and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Gifts they'll actually carry”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “CODE 118 | Advanced Wallets & Premium Lifestyle Essentials”.

  • Canonical URL set

    The canonical URL is https://code-wallets.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://code-wallets.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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://code-wallets.com/collections/all, https://code-wallets.com/collections/wallets, https://code-wallets.com/collections/accessories and https://code-wallets.com/collections/kits-bundles have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://code-wallets.com/collections/all, https://code-wallets.com/collections/wallets, https://code-wallets.com/collections/accessories, https://code-wallets.com/collections/kits-bundles, https://code-wallets.com/products/ultimate-gift-set and https://code-wallets.com/products/ultimate-gift-set-power-bank and 9 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 53 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

3 to fixGoogle 7785
  • 41 small tap targets

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

  • Deprecated browser APIs

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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.

  • About 1,755 words of copy

    The homepage carries about 1,755 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: “CONTACT US” and “SHOP THE SALE”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “SHOP NOW”, “SHOP THE GIFT GUIDE” and “Contact Us”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 130 testimonial or review blocks, 10 customer or partner logos, 1 trust badge and “trusted by 1,000,000+ customers”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 40 cookies set on arrival

    40

    Opening the homepage sets 40 cookies, 1 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.

  • 54 other companies contacted

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

Apps your storefront loads

Klaviyo Email Marketing Sms · Videowise Video Commerce · Postscript Sms Marketing · Gorgias Live Chat Helpdesk · Instafeed · Fondue Cashback Promotions · Triplewhale · Simprosys Google Shopping Feed · Test Sms · Applovin Shop Integration · trafficmanager.net · pwztag.com · amazonaws.com · retention.com · socialsnowball.io · trustpilot.com · shipinsure.io · onetext.com

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

E-commerce
Shopify
Hosting
Shopify

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 code-wallets.com, including 19 speed issues, 1 SEO issue and 2 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