Website review, no card needed
trythirdlove.com website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 84 checks
This review found 39 issues worth fixing on trythirdlove.com, 12 of them high impact, across 84 checks. The most urgent: page weight: 4.2 MB in 374 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
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Osano CMP and POWr and others), adding 2.2 MB and 807 ms of main-thread time.
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
862 KiBAbout 862 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
700 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Use efficient cache lifetimes
504 KiB15 files are served with short cache lifetimes, so returning visitors download them again (504 KiB).
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,522 HTML elements
The page has 2,522 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Yotpo adds 199 ms
199 msYotpo costs a phone 199 ms of main-thread work and 416 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.
Shopify adds 93 ms
93 msShopify costs a phone 93 ms of main-thread work and 572 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.
sierra.chat adds 57 ms
57 mssierra.chat costs a phone 57 ms of main-thread work and 893 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.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 98 ms. During a long task the page ignores taps.
Improve image delivery
50 ms · 27 KiB2 images could be 27 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Reduce unused CSS
49 KiBAbout 49 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Slide 1”.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 40 ms
40 msScripts block the page for only 40 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.2 MB in 374 requests
4.2 MBYour homepage downloads 4.2 MB in 374 requests on a phone: scripts 2.0 MB (123), other files 1,011 KiB (172) and images 757 KiB (34). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (315 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.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 143.6 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
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
Links must have discernible text (23 elements)
Links must have discernible text: 23 elements on the page fail this check, rated serious by axe-core.
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (13 characters)
Your title is only 13 characters: “ThirdLove UAT”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://thirdlove-uat.myshopify.com)”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
81 internal links, 3 external
The homepage links to 81 pages on trythirdlove.com and 3 external pages.
5 checks passed
One H1 headline
Your main headline reads: “10+ years of bra innovation.”.
Canonical URL set
The canonical URL is https://www.trythirdlove.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://www.trythirdlove.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.trythirdlove.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (428 words), so crawlers that don't run JavaScript still read it.
Other pages
6 linked pages hidden from search
https://www.trythirdlove.com/pages/fitting-room, https://www.trythirdlove.com/collections/bras, https://www.trythirdlove.com/collections/wireless-1, https://www.trythirdlove.com/products/24-7-classic-t-shirt-bra-taupe, https://www.trythirdlove.com/products/24-7-classic-wireless-bra-bluebird and https://www.trythirdlove.com/products/comfortstretch-front-close-t-shirt-bra-dreamy-lilac are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.trythirdlove.com/products/24-7-classic-wireless-bra-bluebird all use the title “ThirdLove UAT”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.trythirdlove.com/pages/fitting-room, https://www.trythirdlove.com/collections/bras, https://www.trythirdlove.com/collections/wireless-1 and https://www.trythirdlove.com/products/24-7-classic-wireless-bra-bluebird have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.trythirdlove.com/collections/bras 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 32 found) and read each the way a search engine does.
3 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
23 small tap targets
23 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 265 words of copy
The homepage carries about 265 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Sale” and “SHOP #1 BRA NOW”.
19 calls to action
The homepage has 19 calls to action, for example “Shop now”, “Shop Sale” and “Shop T-Shirt Bra”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 trythirdlove.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Loyalty Rewards · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Loop Returns · Discount Kit · cloudfront.net · powr.io
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
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on trythirdlove.com, including 14 speed issues, 7 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.