Website review, no card needed
alexandrakaymerch.com website review
Visit site (opens in a new tab)Reviewed 17 November 202631 issues · 79 checks
This review found 31 issues worth fixing on alexandrakaymerch.com, 14 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80B- #46,289 of 117,615 reviewed websitesbeats 55%
- #30,852 of 66,923 online storesbeats 47%
- #29,686 of 61,018 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 852 ms |
| Jun 6, 2026 | 880 ms |
| Jun 13, 2026 | 954 ms |
| Jun 20, 2026 | 909 ms |
| Jun 27, 2026 | 884 ms |
| Jul 4, 2026 | 884 ms |
| Jul 11, 2026 | 912 ms |
| Jul 18, 2026 | 940 ms |
| Jul 25, 2026 | 934 ms |
| Aug 1, 2026 | 974 ms |
| Aug 8, 2026 | 901 ms |
| Aug 15, 2026 | 832 ms |
| Aug 22, 2026 | 667 ms |
| Aug 29, 2026 | 642 ms |
| Sep 5, 2026 | 707 ms |
| Sep 12, 2026 | 706 ms |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 983 ms |
| Oct 3, 2026 | 783 ms |
| Oct 10, 2026 | 821 ms |
| Oct 17, 2026 | 808 ms |
| Oct 24, 2026 | 849 ms |
| Oct 31, 2026 | 751 ms |
| Nov 7, 2026 | 706 ms |
| Nov 14, 2026 | 728 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 70 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 71 ms |
| Jul 18, 2026 | 70 ms |
| Jul 25, 2026 | 70 ms |
| Aug 1, 2026 | 70 ms |
| Aug 8, 2026 | 70 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 63 ms |
| Aug 29, 2026 | 63 ms |
| Sep 5, 2026 | 63 ms |
| Sep 12, 2026 | 63 ms |
| Sep 19, 2026 | 69 ms |
| Sep 26, 2026 | 68 ms |
| Oct 10, 2026 | 70 ms |
| Oct 17, 2026 | 70 ms |
| Oct 24, 2026 | 70 ms |
| Oct 31, 2026 | 70 ms |
| Nov 7, 2026 | 65 ms |
| Nov 14, 2026 | 67 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Reduce unused JavaScript
2.3 s · 467 KiBAbout 467 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Use efficient cache lifetimes
2.2 s · 483 KiB21 files are served with short cache lifetimes, so returning visitors download them again (483 KiB).
3,033 HTML elements
The page has 3,033 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, bandsintown.com and talkshop.live and others), adding 1.1 MB and 539 ms of main-thread time.
bandsintown.com adds 196 ms
196 msbandsintown.com costs a phone 196 ms of main-thread work and 455 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 723 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 147 KiB7 images could be 147 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page.
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
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.7 s
12.7 sThe page becomes fully interactive after 12.7 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 322 ms
322 msScripts block taps and scrolling for 322 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 71 ms to 67 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 70 ms
70 msReal visitors wait 70 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 602 ms
602 msReal visitors wait 602 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 24.3 MB in 173 requests
24.3 MBYour homepage downloads 24.3 MB in 173 requests on a phone: media 21.7 MB (1), scripts 1.2 MB (60) and other files 687 KiB (78). Under 2 MB keeps phones on slow connections fast.
About 6.9 g of CO₂ per visit
6.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.90 g of CO₂e: 828.0 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
212 text elements with low contrast
212 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
81 tap targets too small
81 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
48 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: 48 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
121 internal links, 10 external
The homepage links to 121 pages on alexandrakaymerch.com and 10 external pages.
8 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Shop Alexandra Kay’s official store for exclusive music, apparel, and accessories. Discover limited-edition merch, auto…”.
One H1 headline
Your main headline reads: “Alexandra Kay”.
Title: 35 characters
Your title is a healthy 35 characters: “Alexandra Kay Official Online Store”.
Canonical URL set
The canonical URL is https://alexandrakaymerch.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://alexandrakaymerch.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (654 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://alexandrakaymerch.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://alexandrakaymerch.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://alexandrakaymerch.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://alexandrakaymerch.com/collections/catalog, https://alexandrakaymerch.com/collections/apparel, https://alexandrakaymerch.com/collections/accessories, https://alexandrakaymerch.com/collections/music, https://alexandrakaymerch.com/collections/anniversary-collection and https://alexandrakaymerch.com/collections/home and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://alexandrakaymerch.com/products/the-coffee-girl%C2%AE-fall-blend-medium-roast-1lb, whose canonical is https://alexandrakaymerch.com/products/the-coffee-girl%c2%ae-fall-blend-medium-roast-1lb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://alexandrakaymerch.com/collections/the-coffee-girl and https://alexandrakaymerch.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://alexandrakaymerch.com/collections/home has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
13 small tap targets
13 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 781 words of copy
The homepage carries about 781 words of visible text.
2 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop All”, “Shop By Type” and “Subscribe”.
29 short forms
29 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
17 other companies contacted
Loading the homepage contacts 17 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 alexandrakaymerch.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · chimpstatic.com · talkshop.live
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 31 issues on alexandrakaymerch.com, including 12 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.