Website review, no card needed
velvetdesert.com website review
Visit site (opens in a new tab)Reviewed 10 November 202645 issues · 88 checks
This review found 45 issues worth fixing on velvetdesert.com, 16 of them high impact, across 88 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
73C- #86,573 of 116,487 reviewed websitesbeats 22%
- #54,795 of 66,776 online storesbeats 15%
- #51,381 of 60,929 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.8 s |
| Aug 8, 2026 | 5.5 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 5.2 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.0 s |
| Nov 7, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 87 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 89 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 88 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 230 ms |
| Aug 1, 2026 | 279 ms |
| Aug 8, 2026 | 251 ms |
| Aug 15, 2026 | 232 ms |
| Aug 22, 2026 | 221 ms |
| Aug 29, 2026 | 235 ms |
| Sep 5, 2026 | 253 ms |
| Sep 12, 2026 | 256 ms |
| Sep 19, 2026 | 210 ms |
| Sep 26, 2026 | 98 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 123 ms |
| Nov 7, 2026 | 120 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.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Reduce unused JavaScript
9.3 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.
Improve image delivery
2.1 s · 2.9 MB17 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.7 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Maps, Facebook and Google Tag Manager and others), adding 2.9 MB and 1.3 s of main-thread time.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Google Maps adds 791 ms
791 msGoogle Maps costs a phone 791 ms of main-thread work and 1.9 MB 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.
Use efficient cache lifetimes
150 ms · 308 KiB16 files are served with short cache lifetimes, so returning visitors download them again (308 KiB).
Minify JavaScript
300 ms · 51 KiB51 KiB could be saved by minifying JavaScript.
Reduce unused CSS
300 ms · 36 KiBAbout 36 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.
Shopify adds 85 ms
85 msShopify costs a phone 85 ms of main-thread work and 335 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 210 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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.
Largest Contentful Paint: 34.1 s
34.1 sYour largest element takes 34.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 35.0 s
35.0 sThe page becomes fully interactive after 35.0 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 214 ms
214 msReal visitors wait 214 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 880 ms
880 msReal visitors wait 880 ms for your server to start answering (75th percentile). Good is under 800 ms.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
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.
Total Blocking Time: 231 ms
231 msScripts block taps and scrolling for 231 ms in total while the page loads. Good is under 200 ms.
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.8 MB in 373 requests
8.8 MBYour homepage downloads 8.8 MB in 373 requests on a phone: images 4.6 MB (74), scripts 2.8 MB (119) and other files 961 KiB (155). Under 2 MB keeps phones on slow connections fast.
14 images far larger than shown
2.5 MB14 images are downloaded at several times the size a phone draws them, for example Diseno_sin_titulo-5.jpg at 4,472 px wide, shown at 293 px. Resized copies would save about 2.5 MB.
2 images over 500 KB
2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.
14 images below the first screen load straight away
14 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
website_format-58.jpg 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).
About 2.5 g of CO₂ per visit
2.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.50 g of CO₂e: 300.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
4 frames have no title, so screen-reader users cannot tell what they contain.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
13 links without text
13 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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (13 characters)
Your title is only 13 characters: “Velvet Desert”. Between 30 and 65 characters leaves room to say what you do and for whom.
109 internal links, 3 external
The homepage links to 109 pages on velvetdesert.com and 3 external pages.
6 checks passed
Meta description: 96 characters
Your meta description is 96 characters: “Classic and trendy waterproof jewelry. VelvetDesert Brand is based in Kuwait, designed in Spain.”.
Canonical URL set
The canonical URL is https://velvetdesert.com/.
Structured data in place
Structured data found: BreadcrumbList, 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://velvetdesert.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, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (514 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://velvetdesert.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages without a meta description
https://velvetdesert.com/collections/frontpage, https://velvetdesert.com/collections/defiant, https://velvetdesert.com/collections/zafir-limited-edition, https://velvetdesert.com/collections/dune-collection, https://velvetdesert.com/collections/desert-tale-collection-2 and https://velvetdesert.com/collections/the-magic-hoops and 2 others 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 54 found) and read each the way a search engine does.
6 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.
Titles are unique
Every page we checked has its own title.
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
18 small tap targets
18 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 395 words of copy
The homepage carries about 395 words of visible text.
5 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop all”, “Shop MENS” and “SHOP NOW”.
21 short forms
21 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Snap Pixel and TikTok 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
26 other companies contacted
Loading the homepage contacts 26 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 velvetdesert.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Bundler Bundles App · Analyzify Ga4 Ads Tracking · Triplewhale · Popsixle · Omnisend · Swym Wishlist Plus · Nova Multi Currency Converter · Restockrocket · nice-team.net · loox.io
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 45 issues on velvetdesert.com, including 24 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.