Website review, no card needed
alkalinetrio.store website review
Visit site (opens in a new tab)Reviewed 12 November 202627 issues · 74 checks
This review found 27 issues worth fixing on alkalinetrio.store, 9 of them high impact, across 74 checks. The most urgent: page weight: 11.6 MB in 297 requests. 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
81B- #36,940 of 108,858 reviewed websitesbeats 60%
- #24,671 of 61,765 online storesbeats 54%
- #23,816 of 56,365 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 951 ms |
| May 30, 2026 | 883 ms |
| Jun 6, 2026 | 858 ms |
| Jun 13, 2026 | 861 ms |
| Jun 20, 2026 | 876 ms |
| Jun 27, 2026 | 992 ms |
| Jul 4, 2026 | 975 ms |
| Jul 11, 2026 | 963 ms |
| Jul 18, 2026 | 960 ms |
| Jul 25, 2026 | 859 ms |
| Aug 1, 2026 | 868 ms |
| Aug 8, 2026 | 903 ms |
| Aug 15, 2026 | 875 ms |
| Aug 22, 2026 | 909 ms |
| Aug 29, 2026 | 908 ms |
| Sep 5, 2026 | 873 ms |
| Sep 12, 2026 | 918 ms |
| Sep 19, 2026 | 941 ms |
| Sep 26, 2026 | 914 ms |
| Oct 3, 2026 | 891 ms |
| Oct 10, 2026 | 864 ms |
| Oct 17, 2026 | 799 ms |
| Oct 24, 2026 | 816 ms |
| Oct 31, 2026 | 868 ms |
| Nov 7, 2026 | 906 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 94 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 93 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 91 ms |
| Aug 1, 2026 | 91 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 98 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 100 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 110 ms |
| Oct 31, 2026 | 110 ms |
| Nov 7, 2026 | 106 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
3,491 HTML elements
The page has 3,491 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
450 ms · 1.6 MB3 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 952 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 312 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
305 KiB7 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
7 third-party services on the page
7 third-party services load with your homepage (corso.com, Facebook and Shopify and others), adding 643 KiB and 481 ms of main-thread time.
Reduce unused JavaScript
108 KiBAbout 108 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Total Blocking Time: 534 ms
534 msScripts block taps and scrolling for 534 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 94 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 406 ms
406 msReal visitors wait 406 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Speed Index: 1.9 s
1.9 sVisually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 11.6 MB in 297 requests
11.6 MBYour homepage downloads 11.6 MB in 297 requests on a phone: images 8.5 MB (46), other files 2.2 MB (153) and scripts 649 KiB (67). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
ALK-101M-2412-HeartAttack.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
82 KiB1 image is downloaded at several times the size a phone draws it, for example Logo_Bone-EPIT.png at 4,096 px wide, shown at 204 px. Resized copies would save about 82 KiB.
About 3.3 g of CO₂ per visit
3.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.30 g of CO₂e: 395.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
61 text elements with low contrast
61 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 (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
50 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: 50 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Alkaline Trio Official Store”. Between 30 and 65 characters leaves room to say what you do and for whom.
One H1 headline
Your <h1> is empty.
80 internal links, 15 external
The homepage links to 80 pages on alkalinetrio.store and 15 external pages.
6 checks passed
Meta description: 81 characters
Your meta description is 81 characters: “Official Alkaline Trio Online Store. Shop t-shirts, music, accessories, and more!”.
Canonical URL set
The canonical URL is https://alkalinetrio.store/.
Structured data in place
Structured data found: 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://alkalinetrio.store/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,380 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://alkalinetrio.store/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://alkalinetrio.store/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://alkalinetrio.store/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
11 pages without a meta description
https://alkalinetrio.store/collections/all, https://alkalinetrio.store/customer_authentication/redirect, https://alkalinetrio.store/collections/featured, https://alkalinetrio.store/collections/mens-apparel, https://alkalinetrio.store/collections/womens-apparel and https://alkalinetrio.store/collections/youth-apparel and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://alkalinetrio.store/customer_authentication/redirect 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 43 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
40 of 43 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.
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.
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 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 367 words of copy
The homepage carries about 367 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Order Status & Management” and “Contact Us”.
13 short forms
13 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
10 other companies contacted
Loading the homepage contacts 10 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 alkalinetrio.store, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Corso · Yuri Facebook Multi Pixels
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 27 issues on alkalinetrio.store, including 11 speed issues, 2 SEO issues and 4 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.