Website review, no card needed
burrowsclothiers.com website review
Visit site (opens in a new tab)Reviewed 7 November 202622 issues · 72 checks
This review found 22 issues worth fixing on burrowsclothiers.com, 6 of them high impact, across 72 checks. The most urgent: reduce unused JavaScript. 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- #40,715 of 121,360 reviewed websitesbeats 61%
- #27,116 of 68,666 online storesbeats 54%
- #26,146 of 62,577 Shopify storesbeats 52%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 6, 2026 | 854 ms |
| Jul 4, 2026 | 827 ms |
| Jul 11, 2026 | 752 ms |
| Jul 18, 2026 | 732 ms |
| Jul 25, 2026 | 750 ms |
| Aug 1, 2026 | 756 ms |
| Aug 8, 2026 | 912 ms |
| Aug 15, 2026 | 916 ms |
| Aug 22, 2026 | 691 ms |
| Aug 29, 2026 | 693 ms |
| Sep 5, 2026 | 620 ms |
| Sep 12, 2026 | 632 ms |
| Sep 19, 2026 | 707 ms |
| Sep 26, 2026 | 634 ms |
| Oct 3, 2026 | 568 ms |
| Oct 10, 2026 | 541 ms |
| Oct 17, 2026 | 526 ms |
| Oct 24, 2026 | 559 ms |
| Oct 31, 2026 | 725 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 6, 2026 | 70 ms |
| Jul 11, 2026 | 74 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 78 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 81 ms |
| Aug 22, 2026 | 63 ms |
| Aug 29, 2026 | 63 ms |
| Sep 5, 2026 | 62 ms |
| Sep 12, 2026 | 63 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 70 ms |
| Oct 3, 2026 | 63 ms |
| Oct 10, 2026 | 62 ms |
| Oct 17, 2026 | 62 ms |
| Oct 24, 2026 | 62 ms |
| Oct 31, 2026 | 75 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
Reduce unused JavaScript
1.8 s · 376 KiBAbout 376 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 830 KiB and 591 ms of main-thread time.
Google Tag Manager adds 495 ms
495 msGoogle Tag Manager costs a phone 495 ms of main-thread work and 650 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.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
24 KiB5 files are served with short cache lifetimes, so returning visitors download them again (24 KiB).
Reduce unused CSS
24 KiBAbout 24 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 694 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Burrows Clothiers”.
Time to Interactive: 10.3 s
10.3 sThe page becomes fully interactive after 10.3 s. Good is under 3.8 s.
Total Blocking Time: 357 ms
357 msScripts block taps and scrolling for 357 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
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) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 70 ms to 75 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 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.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 452 ms
452 msReal visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.7 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.031
0.031The layout barely moves while loading (CLS 0.031, good is under 0.1).
Images and page weight
About 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 63.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.9 MB in 153 requests
1.9 MBYour homepage downloads 1.9 MB in 153 requests on a phone: scripts 986 KiB (48), other files 691 KiB (89) and images 121 KiB (8). That is a lean page.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
42 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: 42 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Burrows Clothiers”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (27 characters)
Your meta description is only 27 characters: “Men's Luxury Clothing Store”. 70 to 160 characters is enough to sell the click.
210 internal links, 4 external
The homepage links to 210 pages on burrowsclothiers.com and 4 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Burrows Clothiers”.
Canonical URL set
The canonical URL is https://burrowsclothiers.com/.
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://burrowsclothiers.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://burrowsclothiers.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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Other pages
7 pages without a meta description
https://burrowsclothiers.com/pages/burrows-clothiers-landing, https://burrowsclothiers.com/collections/albert-thurston, https://burrowsclothiers.com/collections/alto-milano, https://burrowsclothiers.com/collections/berwich, https://burrowsclothiers.com/collections/billy-reid and https://burrowsclothiers.com/collections/boss and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://burrowsclothiers.com/pages/burrows-clothiers-landing and https://burrowsclothiers.com/collections 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 101 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
2 checks passed
Tap targets are thumb-sized
13 of 16 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 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 45 words
The homepage has only about 45 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now” and “SHOP NOW”.
9 calls to action
The homepage has 9 calls to action, for example “Shop”, “Shop Now” and “Subscribe”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
16 other companies contacted
Loading the homepage contacts 16 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 burrowsclothiers.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms
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
- Hosting
- Shopify
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 burrowsclothiers.com, including 10 speed issues, 2 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.