Website review, no card needed
essanteorganics.com website review
Visit site (opens in a new tab)Reviewed 11 November 202649 issues · 97 checks
This review found 49 issues worth fixing on essanteorganics.com, 18 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 4.3 s |
| Oct 31, 2026 | 4.5 s |
| Nov 7, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 79 ms |
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 83 ms |
| Jun 27, 2026 | 81 ms |
| Jul 4, 2026 | 80 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 80 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 89 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 86 ms |
| Oct 31, 2026 | 89 ms |
| Nov 7, 2026 | 87 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.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Use efficient cache lifetimes
4.4 s · 27.2 MB96 files are served with short cache lifetimes, so returning visitors download them again (27.2 MB).
Reduce unused JavaScript
2.5 s · 522 KiBAbout 522 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
3.0 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, cloudfront.net and Amazon Web Services and others), adding 1.3 MB and 645 ms of main-thread time.
Reduce unused CSS
600 ms · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
cloudfront.net adds 152 ms
152 mscloudfront.net costs a phone 152 ms of main-thread work and 753 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.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 739 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 174 ms
174 msFacebook costs a phone 174 ms of main-thread work and 302 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.
1,865 HTML elements
The page has 1,865 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Minify CSS
150 ms · 46 KiB46 KiB could be saved by minifying CSS.
Document request latency
167 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 98 ms. During a long task the page ignores taps.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
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: 78 ms
78 msYour server sent the HTML in 78 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.
Real-user LCP: 9.0 s
9.0 sReal visitors wait 9.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.3 s
5.3 sReal visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 12.5 s
12.5 sYour largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The USDA Organic® & ToxicFree® Superstore Nothing Else is P…”.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Largest content (LCP) got 113% slower for real visitors
+113%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.248
0.248The layout shifts by 0.248 while loading, so content jumps under the reader's thumb. Good is under 0.1.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 79 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 89 ms
89 msScripts block the page for only 89 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 28.5 MB in 144 requests
28.5 MBYour homepage downloads 28.5 MB in 144 requests on a phone: media 23.5 MB (17), images 3.3 MB (63) and scripts 1.1 MB (30). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (1.6 MB) 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 below the first screen load straight away
3 images further down the page (100 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 8.1 g of CO₂ per visit
8.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.08 g of CO₂e: 970.0 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (7 elements)
Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
42 images without alt text
42 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (37 elements)
All page content should be contained by landmarks: 37 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
17 H1 headlines
There are 17 <h1> headlines (“The USDA Organic® & ToxicFree® Superstore”, “category” and “goal”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.essanteorganics.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at essanteorganics.com/robots.txt, the first file search crawlers ask for.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
280 internal links, 33 external
The homepage links to 280 pages on essanteorganics.com and 33 external pages.
2 checks passed
Title: 30 characters
Your title is a healthy 30 characters: “Essanté Organics Shopping Cart”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.essanteorganics.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
Text is in the HTML
Your server sends the page's text in the HTML (2,880 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/startpublicshopping.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/CancelOrderv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/MainCartv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/ViewShoppingCartv4.aspx, https://www.essanteorganics.com/MemberToolsDotNet/ShoppingCartv4/MainCartv4.aspx and https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/ProductDetailv4.aspx all use the title “Essanté Organics Shopping Cart”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/CancelOrderv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/MainCartv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/ViewShoppingCartv4.aspx, https://www.essanteorganics.com/MemberToolsDotNet/ShoppingCartv4/MainCartv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/ProductDetailv4.aspx and https://www.essanteorganics.com/MemberToolsDotNet/EnrollmentV4/StartPublicEnrollment.aspx have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/ViewShoppingCartv4.aspx has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.essanteorganics.com/MemberToolsDotNet/EnrollmentV4/StartPublicEnrollment.aspx has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/CancelOrderv4.aspx, https://www.essanteorganics.com/membertoolsdotnet/shoppingcartv4/MainCartv4.aspx and https://www.essanteorganics.com/MemberToolsDotNet/ShoppingCartv4/MainCartv4.aspx took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
17 of 18 tappable elements near the top are at least 24 px.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 807 words of copy
The homepage carries about 807 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN & SAVE - GET 30% OFF” and “SHOP ALL”.
48 calls to action
The homepage has 48 calls to action, for example “View Order History”, “Cancel Current Order” and “Retail Shop”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 7 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 4 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Meta 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
20 other companies contacted
Loading the homepage contacts 20 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 essanteorganics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- Quality Technology Services, LLC
Company
- Founded
- 2009
- Headquarters
- Phoenix
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on essanteorganics.com, including 22 speed issues, 8 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.