Website review, no card needed
relixmarketplace.com website review
Visit site (opens in a new tab)Reviewed 10 November 202641 issues · 90 checks
This review found 41 issues worth fixing on relixmarketplace.com, 16 of them high impact, across 90 checks. The most urgent: main-thread work: 29.4 s. 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
69D- #100,225 of 116,487 reviewed websitesbeats 12%
- #61,329 of 66,776 online storesbeats 7%
- #56,734 of 60,929 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
| Nov 7, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 142 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 138 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 158 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 155 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 150 ms |
| Oct 31, 2026 | 147 ms |
| Nov 7, 2026 | 146 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
Speed
Main-thread work: 29.4 s
A phone's processor spends 29.4 s on main-thread work while loading, 15.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
alia-prod.com adds 1.6 s
1.6 salia-prod.com costs a phone 1.6 s of main-thread work and 711 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.
Google Tag Manager adds 1.3 s
1.3 sGoogle Tag Manager costs a phone 1.3 s of main-thread work and 696 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: 10
10/100Your mobile performance score is 10. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,843 HTML elements
The page has 5,843 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 (alia-prod.com, Google Tag Manager and reddit and others), adding 3.4 MB and 5.8 s of main-thread time.
Improve image delivery
600 ms · 1.0 MB36 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Reduce unused JavaScript
550 ms · 1,018 KiBAbout 1,018 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 550 ms faster on a phone.
Render-blocking requests
700 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
rebuyengine.com adds 586 ms
586 msrebuyengine.com costs a phone 586 ms of main-thread work and 563 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.
reddit adds 634 ms
634 msreddit costs a phone 634 ms of main-thread work and 28 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.
Clarity adds 521 ms
521 msClarity costs a phone 521 ms of main-thread work and 29 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 464 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
50 ms · 246 KiB14 files are served with short cache lifetimes, so returning visitors download them again (246 KiB).
Legacy JavaScript
69 KiBPolyfills for old browsers add 69 KiB JavaScript that modern phones do not need.
Reduce unused CSS
58 KiBAbout 58 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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: 26 ms
26 msYour server sent the HTML in 26 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 26.8 s
26.8 sVisually, the page fills in at 26.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 6.4 s
6.4 sScripts block taps and scrolling for 6.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 37.8 s
37.8 sThe page becomes fully interactive after 37.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 1
1The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 142 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 167 ms
167 msReal visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 715 ms
715 msReal visitors wait 715 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 9.5 MB in 640 requests
9.5 MBYour homepage downloads 9.5 MB in 640 requests on a phone: images 4.4 MB (131), scripts 2.7 MB (161) and other files 1.7 MB (307). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
media-generation-holiday-guide-no-logo-0-a5e807a3-775b-4fd4- 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 (96 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.
1 image below the first screen load straight away
1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.69 g of CO₂e: 322.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
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
70 links without text
70 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (32 elements).
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 156 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (199 characters)
Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:title and 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.
669 internal links, 15 external
The homepage links to 669 pages on relixmarketplace.com and 15 external pages.
4 checks passed
Title: 62 characters
Your title is a healthy 62 characters: “relix.shop | Grateful Dead Vinyl, Posters, Apparel | Est. 1974”.
Canonical URL set
The canonical URL is https://relix.shop/.
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://relix.shop/sitemap.xml.
AI search readiness
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 (3,632 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://relix.shop/llms.txt (6 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://relix.shop/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://relix.shop/customer_authentication/redirect 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://relix.shop/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://relix.shop/customer_authentication/redirect, https://relix.shop/collections/grateful-dead-vinyl-records-box-sets-and-cds, https://relix.shop/collections/grateful-dead-books, https://relix.shop/collections/jerry-garcia, https://relix.shop/collections/grateful-dead-t-shirts-1 and https://relix.shop/collections/grateful-dead-x-relix-collection-officially-licensed-long-sleeve-t-shirts and 9 others 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 193 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
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_CONNECTION_RESET”.
2 checks passed
Tap targets are thumb-sized
71 of 74 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 28 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 957 words of copy
The homepage carries about 957 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop by Design”, “Shop by Genre” and “Shop by Pressing”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
44 other companies contacted
Loading the homepage contacts 44 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 relixmarketplace.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gorgias Live Chat Helpdesk · Sledge · Kx Ai Collections · Rebuy Personalization Engine · Microsoft Clarity · Klaviyo Email Marketing Sms · Kimonix · Restockrocket · printful.com · bysimpli.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 41 issues on relixmarketplace.com, including 21 speed issues, 3 SEO issues and 2 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.