Website review, no card needed

inkdstores.com logo

inkdstores.com website review

Visit site (opens in a new tab)Reviewed 5 November 202618 issues · 70 checks

This review found 18 issues worth fixing on inkdstores.com, 4 of them high impact, across 70 checks. The most urgent: page weight: 17.4 MB in 194 requests. 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 inkdstores.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix88
  • Mobile performance score: 88

    88/100

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

  • Improve image delivery

    908 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and IPONWEB and others), adding 481 KiB and 350 ms of main-thread time.

  • Render-blocking requests

    250 ms

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

  • 3 long tasks on the main thread

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

  • Reduce unused JavaScript

    90 KiB

    About 90 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    29 KiB

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

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    19 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix88
  • Time to Interactive: 8.0 s

    8.0 s

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

  • Cumulative Layout Shift: 0.175

    0.175

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

  • Speed Index: 4.3 s

    4.3 s

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

  • 22 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 118 ms

    118 ms

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

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Custom apparel, branded goods, company stores, kitting, and…”.

Images and page weight

3 to fix50
  • Page weight: 17.4 MB in 194 requests

    17.4 MB

    Your homepage downloads 17.4 MB in 194 requests on a phone: media 14.6 MB (1), images 1.3 MB (33) and other files 826 KiB (114). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.2 MB) 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.

  • 3 images far larger than shown

    336 KiB

    3 images are downloaded at several times the size a phone draws them, for example quote-logo-patriots.webp at 1,600 px wide, shown at 114 px. Resized copies would save about 336 KiB.

  • About 4.9 g of CO₂ per visit

    4.93 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9694
  • 11 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 9 links without text

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

2 checks passed
  • Every image has alt text

    All 110 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 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 10096
  • No structured data

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

  • 108 internal links, 13 external

    The homepage links to 108 pages on inkdstores.com and 13 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Premium custom apparel, branded merchandise, company stores, kits, bulk orders, and fulfillment, managed by a real team…”.

  • One H1 headline

    Your main headline reads: “Custom merch, from people who care.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Custom merch, from people who care. | Ink'd”.

  • Canonical URL set

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

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://inkdstores.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 (802 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://inkdstores.com/pages/products 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 20 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 3 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 3 pages that loaded have a <title>.

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_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 429 words of copy

    The homepage carries about 429 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START A PROJECT”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Start a project” and “Jay's Blog Notes from the shop.”.

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and “1,000+ Companies”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 inkdstores.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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

Company

Headquarters
Mansfield

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on inkdstores.com, including 6 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