Website review, no card needed
sechey.com website review
Visit site (opens in a new tab)Reviewed 17 November 202633 issues · 72 checks
This review found 33 issues worth fixing on sechey.com, 9 of them high impact, across 72 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
79C- #54,606 of 121,790 reviewed websitesbeats 50%
- #36,059 of 68,886 online storesbeats 42%
- #34,575 of 62,769 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.5 s |
| Jul 25, 2026 | 1.2 s |
| Aug 8, 2026 | 1.1 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 95 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 112 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
Speed
Reduce unused JavaScript
1.8 s · 435 KiBAbout 435 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58. 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 (Klaviyo, Google CDN and Shopify and others), adding 1.3 MB and 464 ms of main-thread time.
Render-blocking requests
600 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Use efficient cache lifetimes
450 ms · 97 KiB11 files are served with short cache lifetimes, so returning visitors download them again (97 KiB).
Reduce unused CSS
450 ms · 73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Klaviyo adds 213 ms
213 msKlaviyo costs a phone 213 ms of main-thread work and 642 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 112 ms
112 msGoogle CDN costs a phone 112 ms of main-thread work and 298 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 100 ms
100 msShopify costs a phone 100 ms of main-thread work and 322 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.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 123 ms. During a long task the page ignores taps.
Minify CSS
20 ms · 6 KiB6 KiB could be saved by minifying CSS.
Improve image delivery
24 KiB2 images could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.3 s
12.3 sYour largest element takes 12.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sèchey”.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 15.3 s
15.3 sThe page becomes fully interactive after 15.3 s. Good is under 3.8 s.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 78 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 54% slower for real visitors
+54%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 117 ms
117 msScripts block the page for only 117 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 356 requests
3.1 MBYour homepage downloads 3.1 MB in 356 requests on a phone: scripts 1.5 MB (151), other files 992 KiB (169) and images 258 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 103.9 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
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
25 internal links, 16 external
The homepage links to 25 pages on sechey.com and 16 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Shop Sèchey non-alcoholic wines: 88-point Sauvignon Blanc from Bordeaux, plus Rosé, Pinot Noir & Sparkling Cuvée. Drink…”.
Title: 54 characters
Your title is a healthy 54 characters: “Sèchey | Premium Non-Alcoholic Wine, Still & Sparkling”.
Canonical URL set
The canonical URL is https://www.sechey.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.sechey.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.sechey.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
1 page without a title
https://www.sechey.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.sechey.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.sechey.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.sechey.com/collections/shop-all-sechey-wines and https://www.sechey.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
2 pages of 14 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.
Best practices
17 small tap targets
17 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 147 words
The homepage has only about 147 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
4 calls to action
The homepage has 4 calls to action, for example “Shop now” and “Contact Us”.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Pinterest Tag (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
25 other companies contacted
Loading the homepage contacts 25 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 sechey.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Savedby Package Protection · Klaviyo Email Marketing Sms · Inbox · Google Youtube · Indexgpt · nfcube.com · shareasale.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
- Hosting
- Shopify
Company
- Headquarters
- Charleston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on sechey.com, including 16 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.