Website review, no card needed
myessentia.com website review
Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 72 checks
This review found 44 issues worth fixing on myessentia.com, 14 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Essentia
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DNot ranked: the homepage didn't load normally in this review.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 107 ms |
| May 23, 2026 | 106 ms |
| May 30, 2026 | 108 ms |
| Jun 6, 2026 | 107 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 115 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 107 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 134 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 133 ms |
| Oct 31, 2026 | 141 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
Use efficient cache lifetimes
2.4 s · 433 KiB24 files are served with short cache lifetimes, so returning visitors download them again (433 KiB).
Reduce unused JavaScript
2.3 s · 504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Affirm and Clarity and others), adding 6.5 MB and 887 ms of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Legacy JavaScript
550 ms · 69 KiBPolyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
Shopify adds 50 ms
50 msShopify costs a phone 50 ms of main-thread work and 5.5 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.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 221 ms
221 msGoogle Tag Manager costs a phone 221 ms of main-thread work and 345 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.
2,313 HTML elements
The page has 2,313 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
190 ms · 16 KiB16 KiB could be saved by minifying JavaScript.
Minify CSS
160 ms · 12 KiB12 KiB could be saved by minifying CSS.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 152 ms. During a long task the page ignores taps.
Reduce unused CSS
60 ms · 42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.
Improve image delivery
34 KiB2 images could be 34 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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 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: 19.1 s
19.1 sYour largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 19.1 s
19.1 sThe page becomes fully interactive after 19.1 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 107 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 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.
Total Blocking Time: 370 ms
370 msScripts block taps and scrolling for 370 ms in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 495 ms
495 msReal visitors wait 495 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.5 MB in 308 requests
8.5 MBYour homepage downloads 8.5 MB in 308 requests on a phone: media 5.4 MB (1), scripts 1.6 MB (121) and other files 830 KiB (142). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (128 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 2.4 g of CO₂ per visit
2.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.41 g of CO₂e: 289.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
45 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: 45 passed and 5 failed. 4 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.
Title is short (28 characters)
Your title is only 28 characters: “Verifying your connection...”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://myessentia.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at myessentia.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1 checks passed
One H1 headline
Your main headline reads: “Your connection needs to be verified before you can proceed”.
Best practices
1 broken image
1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=6db0fa25-a7af-491b-8516-90a8e2dc4359&referrer=&landingpage=https%3A%2F%2Fmyessentia.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.
2 checks passed
Tap targets are thumb-sized
20 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Homepage answers HTTP 429
Your homepage answered with HTTP 429, so visitors and search engines may see an error page.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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.
About 1,863 words of copy
The homepage carries about 1,863 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “SHOP ORGANIC MATTRESSES”.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
27 cookies set on arrival
27Opening the homepage sets 27 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.
58 other companies contacted
Loading the homepage contacts 58 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 myessentia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Headquarters
- Boca Raton
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on myessentia.com, including 20 speed issues, 10 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.