Website review, no card needed

ekster.com logo

ekster.com website review

Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 92 checks

This review found 40 issues worth fixing on ekster.com, 17 of them high impact, across 92 checks. The most urgent: riseridge.io adds 4.4 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
3.0 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.7 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.4 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
208 ms175 msMay 30Nov 14195 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026185 ms
Jun 6, 2026188 ms
Jun 13, 2026190 ms
Jun 20, 2026191 ms
Jun 27, 2026188 ms
Jul 4, 2026186 ms
Jul 11, 2026182 ms
Jul 18, 2026179 ms
Jul 25, 2026179 ms
Aug 1, 2026182 ms
Aug 8, 2026187 ms
Aug 15, 2026195 ms
Aug 22, 2026202 ms
Aug 29, 2026203 ms
Sep 5, 2026204 ms
Sep 12, 2026204 ms
Sep 19, 2026203 ms
Sep 26, 2026203 ms
Oct 3, 2026196 ms
Oct 10, 2026196 ms
Oct 17, 2026196 ms
Oct 24, 2026196 ms
Oct 31, 2026202 ms
Nov 7, 2026196 ms
Nov 14, 2026195 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 ekster.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ekster.com at 1.2 s1.2 s
  2. ekster.com at 2.3 s2.3 s
  3. ekster.com at 3.5 s3.5 s
  4. ekster.com at 4.6 s4.6 s
  5. ekster.com at 5.8 s5.8 s
  6. ekster.com at 6.9 s6.9 s
  7. ekster.com at 8.1 s8.1 s
  8. ekster.com at 9.3 s9.3 s

Speed

14 to fix31
  • riseridge.io adds 4.4 s

    4.4 s

    riseridge.io costs a phone 4.4 s of main-thread work and 43 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 35.1 s

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

  • Use efficient cache lifetimes

    2.6 s · 709 KiB

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

  • Reduce unused JavaScript

    1.9 s · 938 KiB

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

  • Clarity adds 1.2 s

    1.2 s

    Clarity costs a phone 1.2 s of main-thread work and 29 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 31

    31/100

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

  • 4,838 HTML elements

    The page has 4,838 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 (riseridge.io, Clarity and Shopify and others), adding 2.7 MB and 8.5 s of main-thread time.

  • Shopify adds 925 ms

    925 ms

    Shopify costs a phone 925 ms of main-thread work and 1.4 MB 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.

  • Google Tag Manager adds 811 ms

    811 ms

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

  • Improve image delivery

    300 ms · 505 KiB

    20 images could be 505 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • loox.io adds 552 ms

    552 ms

    loox.io costs a phone 552 ms of main-thread work and 27 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.

  • Legacy JavaScript

    400 ms · 104 KiB

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 48 KiB

    About 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 18 KiB

    18 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    100 ms

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

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

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

7 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: 18.1 s

    18.1 s

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

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 37.3 s

    37.3 s

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

  • Total Blocking Time: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 146 ms

    146 ms

    Real visitors wait 146 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: 736 ms

    736 ms

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

  • Cumulative Layout Shift: 0.023

    0.023

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

Images and page weight

1 to fix70
  • Page weight: 6.9 MB in 818 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 818 requests on a phone: scripts 3.0 MB (227), images 1.9 MB (226) and other files 1.6 MB (336). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    1.96 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • 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 8793
  • Certain ARIA roles must be contained by particular parents (2 elements)

    Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

  • 7 text elements with low contrast

    7 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 (12 elements)

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

  • 4 form fields without a label

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

  • 2 tap targets too small

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 272 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 2 problems

    Structured data found (BreadcrumbList and Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.ekster.com/cdn/shop/files/Logo_3.png?crop=center&…”.

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

  • 140 internal links, 16 external

    The homepage links to 140 pages on ekster.com and 16 external pages.

7 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Our trackable wallets, card holders, bags and tech accessories provide function and style at your fingertips. Shop Ekst…”.

  • One H1 headline

    Your main headline reads: “Ekster® | Smart Trackable Wallets,Travel Bags and EDC Gear”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Ekster® | Smart Trackable Wallets,Travel Bags and EDC Gear”.

  • Canonical URL set

    The canonical URL is https://www.ekster.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://www.ekster.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://www.ekster.com/collections has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.ekster.com/products/trackable-travelpack-bundle is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.ekster.com/collections has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.ekster.com/collections, https://www.ekster.com/products/ekster-wallet-pro, https://www.ekster.com/products/ekster-cardholder-pro, https://www.ekster.com/products/cardholder-pro-magsafe, https://www.ekster.com/collections/new-releases and https://www.ekster.com/collections/trackers 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 56 found) and read each the way a search engine does.

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

Best practices

4 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://match.adsrvr.org/track/cmf/generic?ttd_pid=8ir678l&ttd_tpi=1&gdpr=0&ttd_passthrough=shop_domain%3Dekster.myshopify.com%26cid%3D968fde0f-adf9-4ad0-8823-318f63e26592%26hash%3Dnull.

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unable to process event: initializeKlaviyoBackInStock,,function(e){l&&l(e);c(e)}”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,881 words of copy

    The homepage carries about 1,881 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 Black Friday” and “Shop Travel”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop Black Friday”, “Shop Travel” and “Shop Wallets”.

  • 7 short forms

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

  • Social proof on the page

    Social proof on the homepage: 127 testimonial or review blocks, a star rating, 9 trust badges and “2M+ happy customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager 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

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 52 cookies set on arrival

    52

    Opening the homepage sets 52 cookies, 1 of them by other companies (measured from a US location before any click).

  • 62 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 ekster.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
10 Shopify Products;Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
Amsterdam

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 ekster.com, including 21 speed issues, 2 SEO issues and 3 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