Website review, no card needed
purelyelizabeth.com website review
Visit site (opens in a new tab)Reviewed 6 November 202647 issues · 87 checks
This review found 47 issues worth fixing on purelyelizabeth.com, 16 of them high impact, across 87 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
69D- #102,940 of 119,875 reviewed websitesbeats 12%
- #62,368 of 67,952 online storesbeats 7%
- #57,631 of 61,933 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 145 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 138 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 186 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 188 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 203 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 199 ms |
| Oct 31, 2026 | 196 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.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Reduce unused JavaScript
1.8 s · 1.7 MBAbout 1.7 MB 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.
Use efficient cache lifetimes
1.6 s · 1.2 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).
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: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,203 HTML elements
The page has 3,203 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Yotpo and PayPal and others), adding 4.2 MB and 1.6 s of main-thread time.
Reduce unused CSS
750 ms · 210 KiBAbout 210 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 364 ms
364 msGoogle Tag Manager costs a phone 364 ms of main-thread work and 484 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.
Improve image delivery
350 ms · 42 KiB2 images could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Legacy JavaScript
300 ms · 84 KiBPolyfills for old browsers add 84 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 192 ms
192 msShopify costs a phone 192 ms of main-thread work and 1.4 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.
rebuyengine.com adds 189 ms
189 msrebuyengine.com costs a phone 189 ms of main-thread work and 873 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.
Yotpo adds 218 ms
218 msYotpo costs a phone 218 ms of main-thread work and 450 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.
PayPal adds 202 ms
202 msPayPal costs a phone 202 ms of main-thread work and 395 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 49 KiB49 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Render-blocking requests
100 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
Minify CSS
6 KiB6 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: 16 ms
16 msYour server sent the HTML in 16 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: 15.7 s
15.7 sYour largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 41.5 s
41.5 sThe page becomes fully interactive after 41.5 s. Good is under 3.8 s.
Speed Index: 13.1 s
13.1 sVisually, the page fills in at 13.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 965 ms
965 msScripts block taps and scrolling for 965 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 230 ms
230 msReal visitors wait 230 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 145 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
4 checks passed
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user TTFB: 398 ms
398 msReal visitors wait 398 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.067
0.067The layout barely moves while loading (CLS 0.067, good is under 0.1).
Images and page weight
Page weight: 22.6 MB in 452 requests
22.6 MBYour homepage downloads 22.6 MB in 452 requests on a phone: media 14.5 MB (8), scripts 3.8 MB (144) and other files 2.5 MB (220). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Nourish_and_Thrive_PreOrder_Assets_Homepage-05.webp 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).
6 images in older formats
6 images (946 KiB) are 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.
3 images far larger than shown
126 KiB3 images are downloaded at several times the size a phone draws them, for example ProteinG_AlmondButterBerries_V1_Hero_400x400.webp at 320 px wide, shown at 100 px. Resized copies would save about 126 KiB.
About 6.4 g of CO₂ per visit
6.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.41 g of CO₂e: 769.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 tap targets too small
25 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), 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. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 5 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 long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “Purely Elizabeth | Live Purely with Granola, Oatmeal & Cereal | purelyelizabeth”.
Meta description is long (177 characters)
Your meta description is 177 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
185 internal links, 13 external
The homepage links to 185 pages on purelyelizabeth.com and 13 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://purelyelizabeth.com/.
Structured data in place
Structured data found: Organization, Product 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://purelyelizabeth.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://purelyelizabeth.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, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,606 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 64 found) and read each the way a search engine does.
1 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
36 small tap targets
36 of 85 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 (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 968 words of copy
The homepage carries about 968 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP NEW RELEASES”.
26 calls to action
The homepage has 26 calls to action, for example “Shop”, “SHOP ALL” and “Cookbook Pre-Order”.
13 short forms
13 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 73 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel, Hotjar and TikTok Pixel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 5 mores (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.
43 cookies set on arrival
43Opening the homepage sets 43 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.
62 other companies contacted
Loading the homepage contacts 62 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 purelyelizabeth.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Yotpo Product Reviews · Attentive · Rebuy Personalization Engine · Forms · Gdpr Backpack · Swym Wishlist Plus · ecocart.tools · rechargecdn.com · attn.tv
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
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Headquarters
- Boulder
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on purelyelizabeth.com, including 24 speed issues, 4 SEO issues and 1 conversion gap. 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.