Website review, no card needed
velvet-tees.com website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 88 checks
This review found 39 issues worth fixing on velvet-tees.com, 11 of them high impact, across 88 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
82B- #35,087 of 125,845 reviewed websitesbeats 67%
- #23,062 of 70,280 online storesbeats 61%
- #22,260 of 63,839 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 180 ms |
| May 23, 2026 | 183 ms |
| May 30, 2026 | 191 ms |
| Jun 6, 2026 | 192 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 205 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 214 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 237 ms |
| Sep 5, 2026 | 247 ms |
| Sep 12, 2026 | 255 ms |
| Sep 19, 2026 | 254 ms |
| Sep 26, 2026 | 253 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 252 ms |
| Oct 24, 2026 | 252 ms |
| Oct 31, 2026 | 262 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
1.0 s
2.0 s
3.1 s
4.1 s
5.1 s
6.1 s
7.1 s
8.2 s
Speed
Render-blocking requests
1.6 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,524 HTML elements
The page has 3,524 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
1.9 MB18 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Google Tag Manager and Klaviyo and others), adding 1.8 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
150 ms · 497 KiB32 files are served with short cache lifetimes, so returning visitors download them again (497 KiB).
Hotjar adds 442 ms
442 msHotjar costs a phone 442 ms of main-thread work and 272 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.
Google Tag Manager adds 378 ms
378 msGoogle Tag Manager costs a phone 378 ms of main-thread work and 483 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
300 ms · 77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 279 ms. During a long task the page ignores taps.
Klaviyo adds 129 ms
129 msKlaviyo costs a phone 129 ms of main-thread work and 405 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.
Optanon adds 93 ms
93 msOptanon costs a phone 93 ms of main-thread work and 308 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
88 KiBPolyfills for old browsers add 88 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 15 ms
15 msYour server sent the HTML in 15 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.0 s
15.0 sYour largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mobile All Wrapped Up”.
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 41.3 s
41.3 sThe page becomes fully interactive after 41.3 s. Good is under 3.8 s.
Tap response (INP) got 42% slower for real visitors
+42%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 180 ms to 262 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 376 ms
376 msScripts block taps and scrolling for 376 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 630 ms
630 msReal visitors wait 630 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.037
0.037The layout barely moves while loading (CLS 0.037, good is under 0.1).
Images and page weight
Page weight: 10.2 MB in 487 requests
10.2 MBYour homepage downloads 10.2 MB in 487 requests on a phone: images 5.8 MB (88), scripts 2.8 MB (162) and other files 1.1 MB (190). Under 2 MB keeps phones on slow connections fast.
12 images far larger than shown
954 KiB12 images are downloaded at several times the size a phone draws them, for example feather-jersey-valerie08-multi_021.jpg at 1,200 px wide, shown at 260 px. Resized copies would save about 954 KiB.
6 images below the first screen load straight away
6 images further down the page (600 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (31 KiB) is 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 2.9 g of CO₂ per visit
2.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.89 g of CO₂e: 346.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 links without text
4 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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h3), 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. (7 elements).
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (226 characters)
Your meta description is 226 characters; Google truncates after about 160, so the end of your pitch is cut.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
129 internal links, 6 external
The homepage links to 129 pages on velvet-tees.com and 6 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Velvet by Graham & Spencer”.
Title: 57 characters
Your title is a healthy 57 characters: “Velvet By Graham And Spencer – Velvet by Graham & Spencer”.
Canonical URL set
The canonical URL is https://velvet-tees.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://velvet-tees.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
3 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 (922 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://velvet-tees.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://velvet-tees.com/collections/new-arrivals and https://velvet-tees.com/collections/new-arrivals-men all use the title “New Arrivals – Velvet by Graham & Spencer”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://velvet-tees.com/collections/new-arrivals, https://velvet-tees.com/collections/new-arrivals-men, https://velvet-tees.com/collections/womens-tops, https://velvet-tees.com/collections/womens-sweaters, https://velvet-tees.com/collections/jumpsuits and https://velvet-tees.com/collections/hoodies-sweatshirts have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187210214&Ver=2&mid=94d60baf-d48d-4fef-b652-80407ead6714&bo=3&sid=b11f88e0d8b611f1a4e8dbaa7c0a5859&vid=b11f86b0d8b611f189b165a20f1b02ad&vids=1&msclkid=N&pi=918639831&l.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
56 of 58 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.
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 538 words of copy
The homepage carries about 538 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: “SHOP HOLIDAY 2026”.
28 calls to action
The homepage has 28 calls to action, for example “Shop All”, “The Linen Shop” and “SHOP ALL”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
54 other companies contacted
Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 velvet-tees.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Onetrust Consent Management · Geo Pro Geolocation · Patrol · Okendo · Eg Auto Add To Cart · Pfcbdcc83 Opensend · Easylocation · Event Promotion Bar · jsdelivr.net · zonos.com · pepperjam.com · getredo.com · nosto.com · hextom.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Culver City
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 velvet-tees.com, including 20 speed issues, 2 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.