Website review, no card needed
emmarelief.com website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 84 checks
This review found 42 issues worth fixing on emmarelief.com, 20 of them high impact, across 84 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
74C- #83,015 of 118,230 reviewed websitesbeats 26%
- #52,592 of 67,184 online storesbeats 18%
- #49,496 of 61,260 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 280 ms |
| May 23, 2026 | 289 ms |
| May 30, 2026 | 301 ms |
| Jun 6, 2026 | 304 ms |
| Jun 13, 2026 | 318 ms |
| Jun 20, 2026 | 321 ms |
| Jun 27, 2026 | 318 ms |
| Jul 4, 2026 | 321 ms |
| Jul 11, 2026 | 314 ms |
| Jul 18, 2026 | 307 ms |
| Jul 25, 2026 | 296 ms |
| Aug 1, 2026 | 288 ms |
| Aug 8, 2026 | 260 ms |
| Aug 15, 2026 | 255 ms |
| Aug 22, 2026 | 262 ms |
| Aug 29, 2026 | 265 ms |
| Sep 5, 2026 | 273 ms |
| Sep 12, 2026 | 273 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 250 ms |
| Oct 3, 2026 | 231 ms |
| Oct 10, 2026 | 230 ms |
| Oct 17, 2026 | 228 ms |
| Oct 24, 2026 | 220 ms |
| Oct 31, 2026 | 227 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
4.3 s · 1.1 MB49 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Reduce unused JavaScript
3.6 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
1.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
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.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.7 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 (Google Tag Manager, konsciousketo.com and Facebook and others), adding 2.3 MB and 2.0 s of main-thread time.
Improve image delivery
200 ms · 911 KiB12 images could be 911 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Google Tag Manager adds 872 ms
872 msGoogle Tag Manager costs a phone 872 ms of main-thread work and 1.1 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.
konsciousketo.com adds 289 ms
289 mskonsciousketo.com costs a phone 289 ms of main-thread work and 240 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 281 ms. During a long task the page ignores taps.
1,710 HTML elements
The page has 1,710 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
14 KiB14 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: 27 ms
27 msYour server sent the HTML in 27 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: 24.0 s
24.0 sYour largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Emma bottles”.
Time to Interactive: 33.0 s
33.0 sThe page becomes fully interactive after 33.0 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 945 ms
945 msScripts block taps and scrolling for 945 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 127 ms
127 msReal visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 675 ms
675 msReal visitors wait 675 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 280 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
20 images over 500 KB
20 images weigh 25.2 MB together. On a phone connection a single image that size takes seconds.
Page weight: 7.3 MB in 318 requests
7.3 MBYour homepage downloads 7.3 MB in 318 requests on a phone: images 2.7 MB (44), scripts 2.7 MB (83) and other files 868 KiB (165). Under 2 MB keeps phones on slow connections fast.
14 images far larger than shown
6.3 MB14 images are downloaded at several times the size a phone draws them, for example gut.webp at 1,413 px wide, shown at 327 px. Resized copies would save about 6.3 MB.
36 images in older formats
36 images (27.2 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.
22 images below the first screen load straight away
22 images further down the page (15.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.06 g of CO₂e: 247.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
37 images without alt text
37 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (110 elements)
All page content should be contained by landmarks: 110 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.
6 links without text
6 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.
1 checks passed
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to enclavebioactives.com, not emmarelief.com, so Google may credit that host instead.
23 internal links, 10 external
The homepage links to 23 pages on emmarelief.com and 10 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Emma relief supplement helps restore gut balance, ease bloating, and support healthy digestion - your natural solution …”.
One H1 headline
Your main headline reads: “Daily Support for Occasional Bloating, Gas & Constipation*”.
Title: 55 characters
Your title is a healthy 55 characters: “Emma Relief Supplement | Gut Health & Digestive Support”.
Structured data in place
Structured data found: 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://emmarelief.com/sitemap.xml.
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://emmarelief.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,767 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://emmarelief.com/pp_url, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages without a meta description
https://emmarelief.com/pages/our-approach and https://emmarelief.com/pages/accessibility-statement have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://emmarelief.com/pages/our-approach, https://emmarelief.com/blogs/emmas-world and https://emmarelief.com/pages/accessibility-statement have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://emmarelief.com/pages/reviews 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 8 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=283006905&Ver=2&mid=d0ce2e29-c0db-40d9-a29a-b1fe357d8602&bo=3&sid=4a60e0b0d84d11f180d02b7330113ab3&vid=4a612150d84d11f1ab7b8d7911a6d11e&vids=0&msclkid=N&pi=918639831&l.
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: the server responded with a status of 403 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 1,427 words of copy
The homepage carries about 1,427 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now →”.
2 calls to action
The homepage has 2 calls to action, for example “Shop Now →” and “Sign Up”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email 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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies, 1 of them by other companies (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.
57 other companies contacted
Loading the homepage contacts 57 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 emmarelief.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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on emmarelief.com, including 20 speed issues, 1 SEO issue 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.