Website review, no card needed
stubbsandwootton.com website review
Visit site (opens in a new tab)Reviewed 5 November 202621 issues · 75 checks
This review found 21 issues worth fixing on stubbsandwootton.com, 7 of them high impact, across 75 checks. The most urgent: page weight: 4.0 MB in 224 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
86B- #12,035 of 124,112 reviewed websitesbeats 87%
- #7,291 of 69,786 online storesbeats 85%
- #7,061 of 63,472 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 86 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 81 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 80 ms |
| Aug 22, 2026 | 81 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 91 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 91 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 91 ms |
| Oct 31, 2026 | 87 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.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Reduce unused JavaScript
900 ms · 333 KiBAbout 333 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.3 MB and 454 ms of main-thread time.
Render-blocking requests
400 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Improve image delivery
323 KiB2 images could be 323 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 197 ms
197 msGoogle Tag Manager costs a phone 197 ms of main-thread work and 334 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.
1,803 HTML elements
The page has 1,803 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
250 ms · 54 KiB10 files are served with short cache lifetimes, so returning visitors download them again (54 KiB).
Reduce unused CSS
180 ms · 53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 134 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
42 KiBPolyfills for old browsers add 42 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 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: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 558 ms
558 msReal visitors wait 558 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.079
0.079The layout barely moves while loading (CLS 0.079, good is under 0.1).
Total Blocking Time: 127 ms
127 msScripts block the page for only 127 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 4.0 MB in 224 requests
4.0 MBYour homepage downloads 4.0 MB in 224 requests on a phone: images 1.6 MB (19), scripts 1.2 MB (76) and other files 900 KiB (107). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.8 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
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 58 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. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Stubbs and Wootton”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization, Store and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("stubbsandwootton.com")”.
No XML sitemap
No XML sitemap at https://stubbsandwootton.com/sitemap.xml, so Google discovers your pages only by following links.
197 internal links, 20 external
The homepage links to 197 pages on stubbsandwootton.com and 20 external pages.
5 checks passed
Meta description: 128 characters
Your meta description is 128 characters: “Purveyors of handmade slippers to be worn day into evening, from jeans to dinner clothes. Available in Palm Beach, New …”.
Title: 62 characters
Your title is a healthy 62 characters: “Genuine Handmade Slippers for Men and Women | Stubbs & Wootton”.
Canonical URL set
The canonical URL is https://stubbsandwootton.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.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. 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://stubbsandwootton.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 (843 words), so crawlers that don't run JavaScript still read it.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
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
76 of 92 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 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 690 words of copy
The homepage carries about 690 words of visible text.
7 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
22 other companies contacted
Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 stubbsandwootton.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Userway Website Accessibility · Seo Manager Venntov · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · I Agree To Terms · chimpstatic.com · expivi.com · useamp.com
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 Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- West Palm Beach
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on stubbsandwootton.com, including 12 speed issues, 3 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.