Website review, no card needed
jennikayne.com website review
Visit site (opens in a new tab)Reviewed 19 November 202624 issues · 67 checks
This review found 24 issues worth fixing on jennikayne.com, 7 of them high impact, across 67 checks. The most urgent: page weight: 6.4 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Jenni Kayne
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 189 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 172 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 166 ms |
| Oct 17, 2026 | 169 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 179 ms |
| Nov 7, 2026 | 183 ms |
| Nov 14, 2026 | 183 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
Not measured in this review.
Core Web Vitals
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 189 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 646 ms
646 msReal visitors wait 646 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 6.4 MB
6.4 MBYour homepage downloads 6.4 MB on a phone, 3.3 MB of it images (51%). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
mobile-nov-denim_540x.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).
1 image in older formats
1 image (104 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 1.8 g of CO₂ per visit
1.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
7 elements use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid names (1 element)
ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (3 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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 links without text
5 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 should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
47 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: 47 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Jenni Kayne | California-Inspired Design for the Wardrobe and Home”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
289 internal links, 2 external
The homepage links to 289 pages on jennikayne.com and 2 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Elevate your wardrobe and home with modern essentials. Explore inspiring stories on interiors, fashion, entertaining, w…”.
One H1 headline
Your main headline reads: “The Holiday Gift Guide Is Here”.
Canonical URL set
The canonical URL is https://www.jennikayne.com/.
Structured data in place
Structured data found: Organization.
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.jennikayne.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (877 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.jennikayne.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without an H1
https://www.jennikayne.com/blogs/ripandtan, https://www.jennikayne.com/collections/clothing-womens-shop-all-sweaters, https://www.jennikayne.com/collections/clothing-womens-cardigans, https://www.jennikayne.com/collections/clothing-womens-pullovers and https://www.jennikayne.com/collections/the-classics 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 125 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.
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
1 broken image
1 image failed to load on a phone, for example https://www.jennikayne.com/.
20 small tap targets
20 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
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: 8 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
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 300 words of copy
The homepage carries about 300 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop In United States” and “Shop New Arrivals”.
57 calls to action
The homepage has 57 calls to action, for example “Shop All New Arrivals”, “Shop The Cashmere Lowe Half Zip” and “Shop The Ember Shearling Flat”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Osano) 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, 2 of them by other companies (measured from a US location before any click).
50 other companies contacted
Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 jennikayne.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
Hiring
- Hiring
- 41 open roles
- Teams
- Sales - Corporate (6), Malibu Retail Store (3), Palo Alto Retail Store (3), Woodbury Common (3)
- Job board
- greenhouse
Company
- Employees
- 180
- Headquarters
- West Hollywood
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on jennikayne.com, including 2 SEO issues and 5 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.