Website review, no card needed
washingtonspiritshop.com website review
Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 84 checks
This review found 36 issues worth fixing on washingtonspiritshop.com, 13 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
80B- #49,116 of 126,458 reviewed websitesbeats 55%
- #32,191 of 70,479 online storesbeats 48%
- #30,904 of 63,972 Shopify storesbeats 45%
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 | 1.1 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 999 ms |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 79 ms |
| May 23, 2026 | 79 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 85 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 90 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 89 ms |
| Sep 12, 2026 | 90 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 96 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 89 ms |
| Oct 24, 2026 | 87 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.2 s
1.6 s
2.1 s
2.5 s
2.9 s
3.3 s
Speed
Render-blocking requests
1.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,982 HTML elements
The page has 4,982 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (accessibilityassistant.com, Hubspot and Facebook and others), adding 1.9 MB and 2.1 s of main-thread time.
Improve image delivery
650 ms · 427 KiB10 images could be 427 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Use efficient cache lifetimes
1.0 MB22 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
accessibilityassistant.com adds 952 ms
952 msaccessibilityassistant.com costs a phone 952 ms of main-thread work and 373 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 646 ms. During a long task the page ignores taps.
Hubspot adds 418 ms
418 msHubspot costs a phone 418 ms of main-thread work and 349 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 206 ms
206 msShopify costs a phone 206 ms of main-thread work and 438 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.
cartcoders.com adds 136 ms
136 mscartcoders.com costs a phone 136 ms of main-thread work and 402 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 CSS
150 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
203 KiBAbout 203 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 30.4 s
30.4 sThe page becomes fully interactive after 30.4 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 79 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.3 s
1.3 sReal visitors wait 1.3 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 288 ms
288 msReal visitors wait 288 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 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
Page weight: 7.5 MB in 388 requests
7.5 MBYour homepage downloads 7.5 MB in 388 requests on a phone: images 4.3 MB (82), scripts 1.9 MB (168) and other files 797 KiB (115). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
WebBanner_800x1200_9757afd8-d322-4ed0-955c-839565c2fd86.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
23 images below the first screen load straight away
23 images further down the page (951 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.4 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
Hidden but focusable
44 elements hidden from screen readers can still receive keyboard focus.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5 and h2 → h4), 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Washington Spirit Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (177 characters)
Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
220 internal links, 13 external
The homepage links to 220 pages on washingtonspiritshop.com and 13 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Washington Spirit Shop”.
Canonical URL set
The canonical URL is https://www.washingtonspiritshop.com/.
Structured data in place
Structured data found: Organization.
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.washingtonspiritshop.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description 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://www.washingtonspiritshop.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.
1 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.
Other pages
9 pages without a meta description
https://www.washingtonspiritshop.com/collections/stadium-collection, https://www.washingtonspiritshop.com/collections/2026-jerseys, https://www.washingtonspiritshop.com/collections/2026-playoffs, https://www.washingtonspiritshop.com/collections/youth-new-arrivals, https://www.washingtonspiritshop.com/collections/new-arrivals and https://www.washingtonspiritshop.com/collections/capital-queens and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.washingtonspiritshop.com/collections/stadium-collection, https://www.washingtonspiritshop.com/collections/2026-jerseys, https://www.washingtonspiritshop.com/collections/2026-playoffs, https://www.washingtonspiritshop.com/collections/youth-new-arrivals, https://www.washingtonspiritshop.com/collections/new-arrivals and https://www.washingtonspiritshop.com/collections/capital-queens and 3 others 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 73 found) and read each the way a search engine does.
5 checks passed
Linked pages load
9 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 9 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 “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
35 of 40 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 76 words
The homepage has only about 76 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 “Trin's Collection SHOP COLLECTION”.
10 calls to action
The homepage has 10 calls to action, for example “Shop All”, “SHOP NOW” and “Shop Collection”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 washingtonspiritshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on washingtonspiritshop.com, including 16 speed issues, 3 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.