Website review, no card needed

ezink.co logo

ezink.co website review

Visit site (opens in a new tab)Reviewed 7 November 202625 issues · 76 checks

This review found 25 issues worth fixing on ezink.co, 6 of them high impact, across 76 checks. The most urgent: page weight: 15.5 MB in 232 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

Real-visitor load time (LCP)75th percentile, phones
930 ms685 msMay 16Oct 31859 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026895 ms
May 23, 2026873 ms
May 30, 2026841 ms
Jun 6, 2026813 ms
Jun 13, 2026796 ms
Jun 20, 2026786 ms
Jun 27, 2026794 ms
Jul 4, 2026798 ms
Jul 11, 2026797 ms
Jul 18, 2026799 ms
Jul 25, 2026797 ms
Aug 1, 2026810 ms
Aug 8, 2026829 ms
Aug 15, 2026843 ms
Aug 22, 2026872 ms
Aug 29, 2026888 ms
Sep 5, 2026896 ms
Sep 12, 2026902 ms
Sep 19, 2026835 ms
Sep 26, 2026752 ms
Oct 3, 2026713 ms
Oct 10, 2026721 ms
Oct 17, 2026778 ms
Oct 24, 2026835 ms
Oct 31, 2026859 ms
Real-visitor tap response (INP)75th percentile, phones
152 ms89 msMay 16Oct 31145 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202698 ms
May 30, 2026103 ms
Jun 6, 2026104 ms
Jun 13, 2026104 ms
Jun 20, 2026106 ms
Jun 27, 2026112 ms
Jul 4, 2026118 ms
Jul 11, 2026120 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026123 ms
Aug 15, 2026128 ms
Aug 22, 2026131 ms
Aug 29, 2026135 ms
Sep 5, 2026137 ms
Sep 12, 2026139 ms
Sep 19, 2026137 ms
Sep 26, 2026133 ms
Oct 3, 2026130 ms
Oct 10, 2026133 ms
Oct 17, 2026139 ms
Oct 24, 2026145 ms
Oct 31, 2026145 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 ezink.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ezink.co at 0.7 s0.7 s
  2. ezink.co at 1.3 s1.3 s
  3. ezink.co at 2.0 s2.0 s
  4. ezink.co at 2.6 s2.6 s
  5. ezink.co at 3.3 s3.3 s
  6. ezink.co at 3.9 s3.9 s
  7. ezink.co at 4.6 s4.6 s
  8. ezink.co at 5.2 s5.2 s

Speed

4 to fix99
  • 3,271 HTML elements

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

  • Render-blocking requests

    700 ms

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

  • Improve image delivery

    540 KiB

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

  • Main-thread work: 2.4 s

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

  • 2 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, 9gtb.com and Amazon Web Services and others), adding 268 KiB and 31 ms of main-thread time.

  • Use efficient cache lifetimes

    30 KiB

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

  • 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
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Server response: 18 ms

    18 ms

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

Core Web Vitals

2 to fix100
  • Tap response (INP) got 49% slower for real visitors

    +49%

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

  • Time to Interactive: 6.8 s

    6.8 s

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

11 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.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: 162 ms

    162 ms

    Real visitors wait 162 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.1 s

    1.1 s

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

  • Real-user TTFB: 529 ms

    529 ms

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

  • Speed Index: 2.7 s

    2.7 s

    Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 115 ms

    115 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

Images and page weight

2 to fix64
  • Page weight: 15.5 MB in 232 requests

    15.5 MB

    Your homepage downloads 15.5 MB in 232 requests on a phone: media 12.6 MB (4), images 1.4 MB (43) and other files 838 KiB (100). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    CartPromoBanners_AU_Landscape_360x.jpg 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).

  • 2 images in older formats

    2 images (79 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 4.4 g of CO₂ per visit

    4.40 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8991
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 32 text elements with low contrast

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • 3 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 8377
  • No meta description

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

  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Realistic Temporary Tattoos | Semi-Permanent Tattoos | Lasts 1-2 Weeks – EZINK™”.

  • No structured data

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

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

  • 303 internal links, 15 external

    The homepage links to 303 pages on ezink.co and 15 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “SPOOKY SEASONBUY 1 GET 1 FREE”.

  • Canonical URL set

    The canonical URL is https://ezink.co/.

  • 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://ezink.co/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.

3 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 (2,598 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://ezink.co/collections/all-tattoos, https://ezink.co/collections/custom-tattoos, https://ezink.co/collections/on-sale, https://ezink.co/pages/artists, https://ezink.co/products/ezink-gift-card and https://ezink.co/pages/faqs and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://ezink.co/collections/custom-tattoos and https://ezink.co/pages/how-it-works 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 124 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

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught RangeError: Maximum call stack size exceeded”.

2 checks passed
  • Tap targets are thumb-sized

    162 of 166 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
  • 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 2,136 words of copy

    The homepage carries about 2,136 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: “Shop All” and “Buy 1 Get 1 Free Best Seller”.

  • 41 calls to action

    The homepage has 41 calls to action, for example “Shop All Tattoos”, “LOG IN | SIGN UP” and “Shop All”.

  • 26 short forms

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

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, a star rating, 3 trust badges and “JOIN 200,000+ HAPPY CUSTOMERS”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • 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
  • 2 trackers load before any consent

    2

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

  • 11 cookies set on arrival

    11

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 ezink.co, 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 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Judge Me Reviews · Parkour Tiktok Pixel · Gorgias Live Chat Helpdesk · Triplewhale · Klaviyo Email Marketing Sms · Gempages Builder · Trackbee Connect · Orbe Geolocation · File Uploads By Uploadkit · snapchat.com · rechargecdn.com · rebuyengine.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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on ezink.co, including 6 speed issues, 4 SEO issues 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