Website review, no card needed

inkedbrands.com logo

inkedbrands.com website review

Visit site (opens in a new tab)Reviewed 22 October 202634 issues · 72 checks

This review found 34 issues worth fixing on inkedbrands.com, 15 of them high impact, across 72 checks. The most urgent: improve image delivery. 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

Full-page screenshot of inkedbrands.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. inkedbrands.com at 0.4 s0.4 s
  2. inkedbrands.com at 0.8 s0.8 s
  3. inkedbrands.com at 1.1 s1.1 s
  4. inkedbrands.com at 1.5 s1.5 s
  5. inkedbrands.com at 1.9 s1.9 s
  6. inkedbrands.com at 2.3 s2.3 s
  7. inkedbrands.com at 2.6 s2.6 s
  8. inkedbrands.com at 3.0 s3.0 s

Speed

6 to fix45
  • Improve image delivery

    7.3 s · 1.5 MB

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

  • Use efficient cache lifetimes

    4.4 s · 903 KiB

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

  • Reduce unused JavaScript

    2.1 s · 371 KiB

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

  • Mobile performance score: 45

    45/100

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

  • Render-blocking requests

    850 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

  • Google Tag Manager adds 220 ms

    220 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Analytics), adding 308 KiB and 228 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 75 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    10 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 397 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

8 to fix67
  • 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: 13.7 s

    13.7 s

    Your largest element takes 13.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: 13.7 s

    13.7 s

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

  • Cumulative Layout Shift: 0.489

    0.489

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user CLS: 0.21

    0.21

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

  • 31 images without width and height

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

  • Speed Index: 4.4 s

    4.4 s

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

5 checks passed
  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 125 ms

    125 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 656 ms

    656 ms

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

  • Total Blocking Time: 131 ms

    131 ms

    Scripts block the page for only 131 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix31
  • 8 images far larger than shown

    1.2 MB

    8 images are downloaded at several times the size a phone draws them, for example e91093741810cfd4594f3e333f9e97f0.webp at 2,976 px wide, shown at 175 px. Resized copies would save about 1.2 MB.

  • 1 image over 500 KB

    e91093741810cfd4594f3e333f9e97f0.webp weighs 504 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.4 MB in 28 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 28 requests on a phone: images 1.7 MB (17), scripts 578 KiB (4) and fonts 80 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    https://cdn.inkedbrands.com/pictures/images/000/022/481/orig is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 7 images in older formats

    7 images (970 KiB) 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.

  • About 0.7 g of CO₂ per visit

    0.68 g

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

Accessibility

2 to fixGoogle 9095
  • 4 tap targets too small

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

  • 18 images without alt text

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 8575
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (12 characters)

    Your title is only 12 characters: “Inked Brands”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No XML sitemap

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 17 internal links, 6 external

    The homepage links to 17 pages on inkedbrands.com and 6 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “A design-led brand house”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

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.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 3 pages share a title

    https://www.inkedbrands.com/privacy-policy, https://www.inkedbrands.com/terms-of-use and https://www.inkedbrands.com/accessibility-statement all use the title “Inked Brands - Inked Brands”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.inkedbrands.com/privacy-policy, https://www.inkedbrands.com/brands, https://www.inkedbrands.com/wholesale, https://www.inkedbrands.com/careers, https://www.inkedbrands.com/terms-of-use and https://www.inkedbrands.com/accessibility-statement have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 174 words

    The homepage has only about 174 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.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 inkedbrands.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
Tailwind CSS
Analytics
Google Tag Manager

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 inkedbrands.com, including 14 speed issues, 4 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

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