Website review, no card needed
thirdmanrecords.com website review
Visit site (opens in a new tab)Reviewed 4 November 202622 issues · 78 checks
This review found 22 issues worth fixing on thirdmanrecords.com, 4 of them high impact, across 78 checks. The most urgent: 9 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
85B- #12,305 of 90,860 reviewed websitesbeats 82%
- #7,352 of 47,851 online storesbeats 79%
- #7,127 of 43,064 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 991 ms |
| Jun 6, 2026 | 991 ms |
| Jun 13, 2026 | 933 ms |
| Jun 20, 2026 | 924 ms |
| Jun 27, 2026 | 919 ms |
| Jul 4, 2026 | 904 ms |
| Jul 11, 2026 | 886 ms |
| Jul 18, 2026 | 866 ms |
| Jul 25, 2026 | 851 ms |
| Aug 1, 2026 | 846 ms |
| Aug 8, 2026 | 847 ms |
| Aug 15, 2026 | 845 ms |
| Aug 22, 2026 | 851 ms |
| Aug 29, 2026 | 863 ms |
| Sep 5, 2026 | 868 ms |
| Sep 12, 2026 | 868 ms |
| Sep 19, 2026 | 869 ms |
| Sep 26, 2026 | 853 ms |
| Oct 3, 2026 | 860 ms |
| Oct 10, 2026 | 849 ms |
| Oct 17, 2026 | 846 ms |
| Oct 24, 2026 | 840 ms |
| Oct 31, 2026 | 825 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 78 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 80 ms |
| Jun 27, 2026 | 82 ms |
| Jul 4, 2026 | 82 ms |
| Jul 11, 2026 | 81 ms |
| Jul 18, 2026 | 84 ms |
| Jul 25, 2026 | 84 ms |
| Aug 1, 2026 | 86 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 93 ms |
| Oct 31, 2026 | 88 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
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Improve image delivery
250 ms · 205 KiB12 images could be 205 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and JSDelivr CDN and others), adding 604 KiB and 188 ms of main-thread time.
Legacy JavaScript
200 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 24 KiB15 files are served with short cache lifetimes, so returning visitors download them again (24 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.
Reduce unused CSS
30 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 30 ms faster on a phone.
Reduce unused JavaScript
62 KiBAbout 62 KiB of JavaScript is downloaded but never used 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 407 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 78 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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: 103 ms
103 msReal visitors wait 103 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: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 22 ms
22 msScripts block the page for only 22 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.5 MB in 226 requests
2.5 MBYour homepage downloads 2.5 MB in 226 requests on a phone: images 845 KiB (27), other files 784 KiB (101) and scripts 501 KiB (74). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (113 KiB) is 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.
About 0.7 g of CO₂ per visit
0.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.71 g of CO₂e: 85.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h3 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 1 more 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.
7 H1 headlines
There are 7 <h1> headlines (“Choose your region”, “Third Man Records – Official Store” and “The Flaming Lips”). One clear main headline is easier for people and search engines.
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
182 internal links, 20 external
The homepage links to 182 pages on thirdmanrecords.com and 20 external pages.
5 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Third Man Records – Third Man Records – Official Store”.
Canonical URL set
The canonical URL is https://thirdmanrecords.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://thirdmanrecords.com/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 (776 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
/collections/all-music, /collections/new-releases, /collections/best-sellers, /collections/the-white-stripes, /collections/hardware-pedals and /collections/pedals and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “WebSocket connection to 'wss://thirdmanrecords.com:1234/' failed: Establishing a tunnel via proxy server failed.”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
45 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 431 words of copy
The homepage carries about 431 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “PRE-ORDER NOW”.
11 calls to action
The homepage has 11 calls to action, for example “Subscribe Now”, “Pre-order now” and “PRE-ORDER NOW”.
3 short forms
3 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
21 other companies contacted
Loading the homepage contacts 21 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 thirdmanrecords.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 · Swish Wishlist King · Propel Replays
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
- Hosting
- Shopify
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Company
- Founded
- 2001
- Headquarters
- Nashville
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on thirdmanrecords.com, including 5 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.