Website review, no card needed
jenniferadams.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 75 checks
This review found 30 issues worth fixing on jenniferadams.com, 13 of them high impact, across 75 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
80B- #48,834 of 125,664 reviewed websitesbeats 55%
- #32,103 of 70,232 online storesbeats 48%
- #30,832 of 63,802 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 145 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 153 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 151 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 137 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.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.4 s · 609 KiBAbout 609 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 378 KiB17 files are served with short cache lifetimes, so returning visitors download them again (378 KiB).
Render-blocking requests
1.9 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Signyfyd adds 1.1 s
1.1 sSignyfyd costs a phone 1.1 s of main-thread work and 281 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.4 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 (Signyfyd, Klaviyo and Yotpo and others), adding 1.8 MB and 2.1 s of main-thread time.
Improve image delivery
300 ms · 239 KiB7 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 472 ms. During a long task the page ignores taps.
Klaviyo adds 373 ms
373 msKlaviyo costs a phone 373 ms of main-thread work and 627 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 · 48 KiBAbout 48 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.
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
Minify CSS
120 ms · 15 KiB15 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: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.1 s
16.1 sYour largest element takes 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Comfort, Wrapped with Love”.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 977 ms
977 msScripts block taps and scrolling for 977 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 137 ms 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (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: 447 ms
447 msReal visitors wait 447 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 254 requests
3.9 MBYour homepage downloads 3.9 MB in 254 requests on a phone: scripts 1.8 MB (113), images 793 KiB (20) and other files 661 KiB (72). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
lux-4pc-sheet-set_main-image_heather-gray_2025-12-17_180x.jp 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 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 133.0 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
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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
Title is long (93 characters)
Your title is 93 characters, so Google will cut it off around 60: “Luxury Bedding - Premium Collection of Sheet Sets,Shams and Home Decor – Jennifer Adams® …”.
2 H1 headlines
There are 2 <h1> headlines (“Jennifer Adams® Home” and “Comfort, Wrapped with Love”). One clear main headline is easier for people and search engines.
Meta description is long (196 characters)
Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
143 internal links, 9 external
The homepage links to 143 pages on jenniferadams.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.jenniferadams.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://www.jenniferadams.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.jenniferadams.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (927 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
1 checks passed
Linked pages load
2 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
13 small tap targets
13 of 32 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 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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 382 words of copy
The homepage carries about 382 words of visible text.
5 checks passed
16 calls to action
The homepage has 16 calls to action, for example “Love Coming Home Book”, “Shop All Bedding” and “Shop All Bath”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
39 other companies contacted
Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Termly
A consent management tool (Termly) 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 jenniferadams.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Product Reviews · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · signifyd.com · pepperjam.com · cloudfront.net
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 Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 2 open roles
- Job board
- careers page
Company
- Headquarters
- Scottsdale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on jenniferadams.com, including 17 speed issues, 5 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.