Website review, no card needed
tatemcrae.store website review
Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 75 checks
This review found 25 issues worth fixing on tatemcrae.store, 6 of them high impact, across 75 checks. The most urgent: 4 text elements with low contrast. 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- #42,046 of 126,234 reviewed websitesbeats 61%
- #27,639 of 70,403 online storesbeats 54%
- #26,613 of 63,921 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 987 ms |
| Jun 6, 2026 | 954 ms |
| Jun 13, 2026 | 958 ms |
| Jun 20, 2026 | 969 ms |
| Jun 27, 2026 | 955 ms |
| Jul 4, 2026 | 961 ms |
| Jul 11, 2026 | 966 ms |
| Jul 18, 2026 | 976 ms |
| Jul 25, 2026 | 995 ms |
| Aug 1, 2026 | 927 ms |
| Aug 8, 2026 | 814 ms |
| Aug 15, 2026 | 806 ms |
| Aug 22, 2026 | 807 ms |
| Aug 29, 2026 | 812 ms |
| Sep 5, 2026 | 894 ms |
| Sep 12, 2026 | 905 ms |
| Sep 19, 2026 | 898 ms |
| Sep 26, 2026 | 893 ms |
| Oct 3, 2026 | 945 ms |
| Oct 10, 2026 | 989 ms |
| Oct 17, 2026 | 950 ms |
| Oct 24, 2026 | 943 ms |
| Oct 31, 2026 | 933 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 144 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 142 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 128 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 133 ms |
| Oct 3, 2026 | 150 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 138 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.1 s
3.7 s
4.3 s
4.9 s
Speed
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Klaviyo, Shopify and minmaxify.com and others), adding 929 KiB and 543 ms of main-thread time.
Reduce unused JavaScript
300 ms · 136 KiBAbout 136 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 253 ms
253 msShopify costs a phone 253 ms of main-thread work and 523 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.
Klaviyo adds 266 ms
266 msKlaviyo costs a phone 266 ms of main-thread work and 308 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
150 ms · 86 KiB3 images could be 86 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.
Legacy JavaScript
100 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
30 KiB7 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
Reduce unused CSS
12 KiBAbout 12 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.
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: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 9.9 s
9.9 sThe page becomes fully interactive after 9.9 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: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 144 ms to 138 ms 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 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: 462 ms
462 msReal visitors wait 462 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 163 ms
163 msScripts block the page for only 163 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 301 requests
2.1 MBYour homepage downloads 2.1 MB in 301 requests on a phone: scripts 867 KiB (133), other files 803 KiB (123) and images 274 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 72.9 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
58 form fields without a label
58 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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 (10 characters)
Your title is only 10 characters: “Tate McRae”. Between 30 and 65 characters leaves room to say what you do and for whom.
One H1 headline
Your <h1> is empty.
25 internal links, 5 external
The homepage links to 25 pages on tatemcrae.store and 5 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Official online store of Tate McRae. Fans can purchase exclusive merchandise including t-shirts, hoodies, crewnecks, to…”.
Canonical URL set
The canonical URL is https://tatemcrae.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://tatemcrae.store/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://tatemcrae.store/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://tatemcrae.store/collections/digital-albums-1 and https://tatemcrae.store/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://tatemcrae.store/pages/contact 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.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 11 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Only about 66 words
The homepage has only about 66 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Digital Download” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and 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.
13 cookies set on arrival
13Opening the homepage sets 13 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 tatemcrae.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Easylocation · Countdown Timer · Essential Post Purchase Upsell
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 25 issues on tatemcrae.store, including 11 speed issues, 2 SEO issues and 5 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.