Website review, no card needed
shepherdsfashions.com website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 84 checks
This review found 32 issues worth fixing on shepherdsfashions.com, 8 of them high impact, across 84 checks. The most urgent: render-blocking 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
81B- #35,980 of 105,961 reviewed websitesbeats 60%
- #23,860 of 59,660 online storesbeats 54%
- #23,018 of 54,382 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 204 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 210 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 205 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 225 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 222 ms |
| Aug 15, 2026 | 223 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 230 ms |
| Sep 12, 2026 | 233 ms |
| Sep 19, 2026 | 230 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 226 ms |
| Oct 10, 2026 | 230 ms |
| Oct 17, 2026 | 238 ms |
| Oct 24, 2026 | 245 ms |
| Oct 31, 2026 | 251 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
Render-blocking requests
1.8 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 138 KiB6 images could be 138 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
2,121 HTML elements
The page has 2,121 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 15 ms
15 msShopify costs a phone 15 ms of main-thread work and 377 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.
Reduce unused JavaScript
150 ms · 25 KiBAbout 25 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 20 KiB20 KiB could be saved by minifying JavaScript.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, useamp.com and nfcube.com and others), adding 599 KiB and 48 ms of main-thread time.
Reduce unused CSS
72 KiBAbout 72 KiB of CSS is downloaded but never applied on this page.
Use efficient cache lifetimes
25 KiB7 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 306 ms of it running JavaScript. That is comfortably low.
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 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.7 s
9.7 sThe page becomes fully interactive after 9.7 s. Good is under 3.8 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 204 ms to 251 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 374 ms
374 msReal visitors wait 374 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 263 requests
2.8 MBYour homepage downloads 2.8 MB in 263 requests on a phone: images 985 KiB (39), other files 844 KiB (123) and scripts 662 KiB (64). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
One H1 headline
Your <h1> is empty.
378 internal links, 11 external
The homepage links to 378 pages on shepherdsfashions.com and 11 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Fashion that fits your life, your shape, and your story. Shepherd's Fashions brings ageless, effortless style to women …”.
Title: 52 characters
Your title is a healthy 52 characters: “Shepherd's Fashions - Every Outfit - One Destination”.
Canonical URL set
The canonical URL is https://www.shepherdsfashions.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.shepherdsfashions.com/sitemap.xml.
AI search readiness
4 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, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,054 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.shepherdsfashions.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.shepherdsfashions.com/collections/sweater-shop and https://www.shepherdsfashions.com/collections/cardigans use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.shepherdsfashions.com/pages/shipping-information, whose canonical is https://www.shepherdsfashions.com/pages/shipping-information-2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages without an H1
https://www.shepherdsfashions.com/collections/new-arrivals, https://www.shepherdsfashions.com/collections/tops, https://www.shepherdsfashions.com/collections/bottoms-1, https://www.shepherdsfashions.com/collections/accessories, https://www.shepherdsfashions.com/collections/the-denim-shop and https://www.shepherdsfashions.com/products/yest-ulina-jersey-cowl-neck-top and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://www.shepherdsfashions.com/collections/bottoms-1, https://www.shepherdsfashions.com/collections/the-denim-shop, https://www.shepherdsfashions.com/collections/tees-and-tanks and https://www.shepherdsfashions.com/collections/sweater-shop have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 161 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 84 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 32 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 592 words of copy
The homepage carries about 592 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “WE SHIP INTERNATIONALLY Learn More” and “SHOP NOW”.
18 calls to action
The homepage has 18 calls to action, for example “We ship Internationally Learn More”, “The Denim Shop” and “Shop All Products”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
41 other companies contacted
Loading the homepage contacts 41 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 shepherdsfashions.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Instafeed · Triplewhale · Inbox · Klaviyo Email Marketing Sms · Judge Me Reviews · Simprosys Google Shopping Feed · Returngo Returns Exchanges · Sc Easy Redirects · Rocket Google Reviews · Digital Appointments · Accessibly App · Upsell Koala Discount · Google Review Plus By Entangle · Back In Stock · Boo Eu Withdrawal Button · trafficmanager.net · cloudfront.net · 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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Ottawa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on shepherdsfashions.com, including 12 speed issues, 2 SEO issues and 4 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.